[BUGFIX beta] Implement cacheKeyForTree
hook.
#5110
Merged
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 hook was added in ember-cli/rfcs#90, and essentially guarantees that a given tree returned by an addon is considered stable (or not).
In the case of Ember Data, we do not have different tree output based on our parent (project or addon).
Specifically, this implementation allows both an app and a lazy engine to depend on
ember-data
without duplicating theember-data
assets in both theassets/vendor.js
andengine-dist/<engine-name>/assets/engine-vendor.js
.Fixes ember-engines/ember-engines#438.