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
Currently Environment provides the function findGeneratorsIn, which searches a list of paths and returns a list of generators within those paths. From what I can tell, the user still has to loop through each found module, registering any generators found within. If I am mistaken by all means correct me.
I would like to propose the addition of a registerGeneratorsIn method which receives a list of paths, uses the findGeneratorsIn function to find all the modules within these paths, and then registers all of the generators/sub-generators in the found modules. Namespaces could be generated using the namespace method.
If this addition makes sense I would be happy to start working on a PR.
The text was updated successfully, but these errors were encountered:
I am building a web app that uses yeoman generators. The generators available will all be located under a common directory on the server. Currently, I am using findGeneratorsIn to list all of the modules in this directory, and then looping through each module, registering any generators and sub generators.
jseed
changed the title
registerGeneratorsIn method
registerGeneratorsIn function
Feb 26, 2016
Currently Environment provides the function findGeneratorsIn, which searches a list of paths and returns a list of generators within those paths. From what I can tell, the user still has to loop through each found module, registering any generators found within. If I am mistaken by all means correct me.
I would like to propose the addition of a registerGeneratorsIn method which receives a list of paths, uses the findGeneratorsIn function to find all the modules within these paths, and then registers all of the generators/sub-generators in the found modules. Namespaces could be generated using the namespace method.
If this addition makes sense I would be happy to start working on a PR.
The text was updated successfully, but these errors were encountered: