-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Allow a different Blueprint directory to be specified for Init and New commands #462
Conversation
@@ -10,7 +12,8 @@ module.exports = new Command({ | |||
|
|||
availableOptions: [ | |||
{ name: 'dry-run', type: Boolean, default: false }, | |||
{ name: 'verbose', type: Boolean, default: false } | |||
{ name: 'verbose', type: Boolean, default: false }, | |||
{ name: 'blueprint-path', type: path, default: Blueprint.main } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just "blueprint" is fine.
tests please |
1. change available option 'blueprint-path' to 'blueprint' 2. add acceptance test for 'blueprint' option
Do you want me to add this to the Changelog? |
Yup changelog would be great |
Updated the Changelog. Also, I'm gong to close #451 since it now can be taken care of as a plugin/external dependency. |
Sounds good. Eventually we plan to bundle a good component/addon blueprint |
Allow a different Blueprint directory to be specified for Init and New commands
This would allow a user to have a different project scaffold. It also works towards allowing #451.