This repository has been archived by the owner on Dec 20, 2018. It is now read-only.
Regenerate manifest.json when config/manifest.js is changed #55
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.
Closes #48
@san650 Finally found some time to work on this. This is fully functional!
However I had to skip the broccoli test (
node-tests/broccoli/generate-manifest-json-test.js
) because I am not sure how to make this testable again. Or if this is actually needed...This is because the Broccoli plugin now does much more, as it has to generate the manifest by itself, rather than getting the data from
index.js
. Because it has to regenerate it upon change, while the hooks inindex.js
are only invoked once. So currently it has access to the ember-cliproject
model, and with that dependency testing becomes harder. Would probably have to mock all relevantproject
methods to make this testable.Not sure if that is really worth the needed effort, as the acceptance tests still cover the overall functionality. Your thoughts?