Allowed primary module location to be configured #94
+136
−44
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
This change allows the primary module (JS & LESS) to have a configured location. This is possible my adding an entry to the `modules` array in the yeoman config file for the primary module and also having a `primaryModule` key with the name of the primary module. Also, modules no longer have to be in subdirectories of their parent modules. When adding a new module, the parent directories will be searched for a module defining file, however, if no modules are found, the primary module will be attempted (regardless if the primary module is in a parent directory of the new module).
This was referenced Jan 22, 2015
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.
This change allows the primary module (JS & LESS) to have a configured location. This is possible my adding an entry to the
modulesarray in the yeoman config file for the primary module and also having aprimaryModulekey with the name of the primary module.Also, modules no longer have to be in subdirectories of their parent modules. When adding a new module, the parent directories will be searched for a module defining file, however, if no modules are found, the primary module will be attempted (regardless if the primary module is in a parent directory of the new module).