-
Notifications
You must be signed in to change notification settings - Fork 64
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
Yo commands could group generated content into 'components' using a folder structure. #130
Comments
I think this harkens to a discussion we've had internally at WDS on dev calls. At the moment one of the issues with the plugin-gen on larger projects is conflicts in the primary plugin file as we multiple devs scaffold different includes (see #135 ). The issue at hand is does the use case you suggest indicate that perhaps multiple plugins would be better? |
@aubreypwd What are your thoughts on namespacing in addition to using something like
This would add some structure and allow us to still separate into a looser component structure. Your thoughts? |
Right now when you use a command such as
yo plugin-wp:include <include-name>
you end up with aclass-<prefix>-<thing).php
file in theincludes/class...php
folder. It would be nicer to create a folder when this happens:This would allow us to create other sub-classes under a 'component' folder w/out having to do some funky changes to make that possible. This way I can easily create another
includes
folder in the 'component' folder, which can contain other classes, files, etc that I can include separately.Would also like to get some feedback before I attempt this.
The text was updated successfully, but these errors were encountered: