Skip to content
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

Deprecate component eventManager #194

Merged
merged 1 commit into from
Mar 26, 2017
Merged

Deprecate component eventManager #194

merged 1 commit into from
Mar 26, 2017

Conversation

GavinJoyce
Copy link
Member

@GavinJoyce GavinJoyce commented Dec 26, 2016

@GavinJoyce GavinJoyce changed the title Deprecate custom component eventManager Deprecate component eventManager Dec 26, 2016
@rwjblue
Copy link
Member

rwjblue commented Dec 26, 2016

Awesome, thank you for putting this together!

We should also have this deprecation cover the canDispatchToEventManager property of EventDispatcher (mostly because the option does nothing at that point and is misleading) so that when this lands defining an eventManager on any component or specifying canDispatchToEventManager trigger a deprecation.

@kellyselden
Copy link
Member

I haven't used this feature before, but if I did, what would be the alternative to using it? (how do I un-deprecate my code)

@GavinJoyce
Copy link
Member Author

GavinJoyce commented Jan 17, 2017

@kellyselden you could extend EventDispatcher and implement the soon to be removed _findNearestEventManager in event handlers. I'm happy to create an addon for this if anyone requires it so that it's a simple opt-in.

true on `EventDispatcher`. The warning will have a target version of `3.0`.

If required, we can create an addon which extends the `EventDispatcher` allowing
for opt-in custom `eventManager`s in Ember apps.
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if anyone has a need for this, let me know and I'll create the addon

@kellyselden
Copy link
Member

@GavinJoyce Addon route seems like a good idea to me.

@rwjblue
Copy link
Member

rwjblue commented Jan 27, 2017

Sorry for the delay here. We discussed in the core team meeting on 2017-01-20, and are 👍 on moving this to final comment period.

@mixonic
Copy link
Member

mixonic commented Mar 26, 2017

I'm merging this, as we are certainly past the one-week window and I see no new comments 😗

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants