[FEATURE ember-container-inject-owner] Expose proxy mixins.#12578
Merged
rwjblue merged 1 commit intoemberjs:masterfrom Nov 10, 2015
Merged
[FEATURE ember-container-inject-owner] Expose proxy mixins.#12578rwjblue merged 1 commit intoemberjs:masterfrom
rwjblue merged 1 commit intoemberjs:masterfrom
Conversation
This is needed for tooling to avoid creating fake/mock owner objects. These mixins are underscored since they generally should not be used by end users, however the methods that they expose are public (as part of container-registry-reform feature that was enabled in Ember 2.1).
rwjblue
added a commit
that referenced
this pull request
Nov 10, 2015
[FEATURE ember-container-inject-owner] Expose proxy mixins.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This is needed for tooling to avoid creating fake/mock owner objects. These mixins are underscored since they generally should not be used by end users, however the methods that they expose are public (as part of container-registry-reform feature that was enabled in Ember 2.1).