Remove pods support #693
Merged
Remove pods support #693
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
|
😢 Mainly because there is no good alternative to pods yet. |
|
@knownasilya apologies, but since pods have been recommended against for years, I felt the overhead of supporting them was not worth it and was more confusing for users getting started. I personally like component colocation and keeping everything else classic, but I know a lot of folks do like pods still, so sorry for this 😕 |
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.
Instead of supporting pods, which have been recommended against almost since they came into existence, we should support just the documented and supported formats Ember provides. This will give us less to maintain, and hopefully the more we scope down, the easier it will be to support the latest and greatest things.