Update to pod structure. #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
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.
This is to serve as an example of how the currently pending PR to the ember-jj-abrams-resolver will allow an application to be structured.
The only possibly odd part was that I actually created a subdirectory for the itemController manually. This might need to be addressed in Ember itself, but in the end the solution that I went with was to simply specify
itemController='todos/item-controller'which doesn't seem TOO bad. A possible solution to this upstream would be to make itemControllers their own type, and therefor the actual path for this item controller would have beenapp/todos/item-controller.js.Please note, this should not be merged until the resolver PR is merged and we can update
bower.jsonin this PR to point to main fork again.ember-cli/ember-resolver#16