[FEATURE ember-contextual-components] Enable by default. #12517
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
As discussed in Ember core team meeting on 2015-10-23. Prior to 2.3 branching into beta we need to evaluate the local lookup feature to ensure that contextual components land within one version of local lookup. If it looks like local lookup will not land by 2.4 (before branching 2.3.0-beta.1) this feature will be delayed. This timing should not be an issue.
rwjblue
added a commit
that referenced
this pull request
Oct 24, 2015
[FEATURE ember-contextual-components] Enable by default.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As discussed in Ember core team meeting on 2015-10-23.
Prior to 2.3 branching into beta we need to evaluate the local lookup feature to ensure that contextual components land within one version of local lookup. If it looks like local lookup will not land by 2.4 (before branching 2.3.0-beta.1) this feature will be delayed. This timing should not be an issue.