-
-
Notifications
You must be signed in to change notification settings - Fork 6
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
decouple from ember-cli #6
Comments
Regarding references to |
I believe the concept of structures, may enable this. |
The only thing gives me pause is that they kind of need to know about the resolver, but we don't want to couple that with the implementation. |
@trabus maybe we can do a minimal thing, that sufficiently decouples this case. We can see how it feels, then grow it to something more fully fledged? Call the effort "structures", and aim for that to be the guiding light? You have likely thought about this more then me, so you likely have much more context. |
https://github.com/ember-cli/blueprint/blob/master/lib/blueprint.js#L660
https://github.com/ember-cli/blueprint/blob/master/lib/blueprint.js#L783-L802
provide boundary for abstract tasks
taskFor('npm-install
)maybe rename to
node_module:install` and external consumer can provide the functionalityprovide standalone UI abstraction that can be provided, otherwise have ember-cli provide that UI.
load blueprints based on provided lookup strategy:
https://github.com/ember-cli/blueprint/blob/master/lib/blueprint.js#L1479-L1480
in-report addon stuff: https://github.com/ember-cli/blueprint/blob/master/lib/blueprint.js#L435
references to
pod
references to ember-cli
The text was updated successfully, but these errors were encountered: