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

getRegistryForCurrentRoute should take route from enabled package only #1697

Merged

Conversation

lcampanis
Copy link
Collaborator

@lcampanis lcampanis commented Jan 9, 2017

Make sure current route is taken from enabled packages only, so that other modules can override package templates by using the same package name, without breaking existing package functionality when inheriting events and helpers.

@lcampanis lcampanis changed the title Get registry for current route enabled package only getRegistryForCurrentRoute should take route from enabled package only Jan 10, 2017
@brent-hoover brent-hoover merged commit d1ab807 into release-0.19.0 Jan 11, 2017
@brent-hoover brent-hoover deleted the getRegistryForCurrentRoute-enabled-package-only branch January 11, 2017 23:52
@spencern spencern mentioned this pull request Oct 11, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants