-
-
Notifications
You must be signed in to change notification settings - Fork 501
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adds ember engines in "Application Concerns" #763
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added some suggested wording changes. Thanks for your work on this!
Co-Authored-By: villander <nousvillander@gmail.com>
Co-Authored-By: villander <nousvillander@gmail.com>
I applied all suggested changes, thanks so much @jenweber |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is ready to go now!
I raised the question of file naming and TOC placement with the learning team a couple days ago. It seems that ember-engines makes sense as the file name/url because there is not really a more general concept to use here. It's about the name of the library, the same as how we renamed "Models" to "Ember Data."
There were no objections to the merge in general, since there was already good cautionary info in this PR.
It's solves the big problem around ember ecosystem #701 - this will increase our visibility and the actual proposal of ember engines in ember ecosystem and de-emphasize code-splitting/lazy-loading a bit.
cc: @MelSumner @locks @jenweber @acorncom