-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixing Enumerable#contains deprecation #84
Conversation
As documented in [the deprecation guide](http://emberjs.com/deprecations/v2.x/#toc_enumerable-contains), addons can use [this polyfill](https://github.com/rwjblue/ember-runtime-enumerable-includes-polyfill) to avoid the deprecation while still supporting older versions of Ember.
And nuke all observers.
Fixed deprecation in that commit ( thx for the polyfill hint) - 7cc865a Also, I like your switch to didRender from observers, I'd like to incorporate that, but I remember there were some issues with this approach before. I'll check again. |
If you need that to maintain some backward compatibility that makes sense. But, going forward I would recommend against using methods on components as API between components. If open and close are things that can be done by an ancestor component of this one, it should be expressed as data coming down (like If open and close are things that can be done by a descendant component of this one, they should be yielded downward as actions that can come back up. |
I agree with you. My problem with that initially was that you can't just send However, I see how that could be improved and this should be refactored, but carefully. |
@asennikov can you release a new version with this fix. |
@xomaczar yep, done |
Thx Andrey S. Khomenko
|
As documented in the deprecation guide, addons can use this polyfill to avoid the deprecation while still supporting older versions of Ember.
Closes #82
(The test suite was already failing on beta and canary.)