Version 1.0

Version 1.0 should drop some legacy code (i.e., leftover stuff from #69) , and align with ember-2.0 standards and best practices. Ultimately, we should have no deprecation warnings when running with the “latest” ember.

This is also an opportunity to change some API surfaces, and to bring greater consistency to the ember-cli-materialize library, without needing to maintain backwards compatibility.

I suggest we consider potential changes from the following perspectives

• Consistency - Making sure there is conceptual alignment across all components (i.e., action names, binding names, etc…)
• Completeness of Components - Looking at some use-cases that may be missed by some existing components, and considering what can be changed/added in order to more completely offer a “materialize” equivalent to plain old HTML
• Ease of Use - Is installation/setup as easy as we’d like? Are there some ergonomic improvements that could be made?
• Completeness of Library - We’re still missing quite a few things that the materialize library offers (toasts, table, etc…).

Tasks

• Remove old {{materialize-*}} helpers
• Address all deprecation warnings
• Establish a CI/Testing solution that allows us to maintain quality for both the 0.x and 1.x releases. New components may be back-ported to the Ember 1.x compatible branch?
• Establish some guidelines regarding “versions” and documentation (i.e., how do we make it clear what to do for ember 1.x vs. 2.x apps)

(more tasks will be added)

[mike-north]

I’m going for 1.0! Minimum required version of ember will be 2.3, so that we can take advantage of the new contextual component feature set. “glimmer components” seems quite a ways off, so I don’t want to wait for that

[mike-north]

Last I checked, Brocfile customizations didn’t work in blueprints. I’ll try to move sassOptions to ember-cli-build

On Mon, Aug 24, 2015 at 07:57 Ryan Tablada [e-mail] wrote:

@mike-north https://github.com/mike-north what is the plan in terms of sassOptions deprecations?

Maybe change from including the sassOptions in the blueprint and instead print a suggestion to update sassOptions in the ember-cli-build.js file.

— Reply to this email directly or view it on GitHub https://github.com/mike-north/ember-cli-materialize/issues/130#issuecomment-134233914 .