This repository has been archived by the owner on Sep 21, 2020. It is now read-only.
Fix legacy each with item controller #11
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
rwjblue
suggested changes
May 12, 2020
There was a problem hiding this comment.
Need to add a treeFor (or treeForApp) that avoids putting the app/controllers/* files into the host app if it isn't opting in to legacy controllers.
I'm thinking something like (and you can remove the similar guard from treeForVendor):
treeFor() {
if (this.hasLegacyViewSupport) {
return this._super.treeFor.apply(this, arguments);
}
},
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 part of the original code in the ember.js repo didn't make it into this addon originally:
https://github.com/emberjs/ember.js/blob/v1.13.13/packages/ember-views/lib/views/legacy_each_view.js#L40-L46