You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I should be able to hook into the Ember build process without needing an addon. Something like this:
newEmberApp({treeFor(){}})
Not totally sure how this would work or the semantics, but I would like a lightweight way to affect the broccoli tree. I suspect that somewhere in the process of calling the hooks for all addons, these hooks from the EmberApp definition could also be called pretty easily.
There was some discussion in Discord #ember-cli about in-repo addons being used for this case, but IMO in-repo addons do more harm than good:
They give developers the illusion that lib code is not owned by the project / shouldn't be touched.
It's not entirely clear how to configure tests of lib code to run in the normal test suite
They make it easy to go half-way to creating good abstractions that can actually be shared
Secondly, providing these hooks would allow developers to gradually build good build time abstractions: (1) inline in build file (2) in-repo addon (3) external addon.
The text was updated successfully, but these errors were encountered:
I should be able to hook into the Ember build process without needing an addon. Something like this:
Not totally sure how this would work or the semantics, but I would like a lightweight way to affect the broccoli tree. I suspect that somewhere in the process of calling the hooks for all addons, these hooks from the
EmberApp
definition could also be called pretty easily.There was some discussion in Discord
#ember-cli
about in-repo addons being used for this case, but IMO in-repo addons do more harm than good:lib
code is not owned by the project / shouldn't be touched.lib
code to run in the normal test suiteSecondly, providing these hooks would allow developers to gradually build good build time abstractions: (1) inline in build file (2) in-repo addon (3) external addon.
The text was updated successfully, but these errors were encountered: