Skip to content
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

Merged
merged 3 commits into from
Apr 27, 2014

Conversation

CapyTheBeara
Copy link
Contributor

This would allow a user to have a different project scaffold. It also works towards allowing #451.

@@ -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 }
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just "blueprint" is fine.

@stefanpenner
Copy link
Contributor

tests please

1. change available option 'blueprint-path' to 'blueprint'
2. add acceptance test for 'blueprint' option
@CapyTheBeara
Copy link
Contributor Author

Do you want me to add this to the Changelog?

@stefanpenner
Copy link
Contributor

Yup changelog would be great

@CapyTheBeara
Copy link
Contributor Author

Updated the Changelog. Also, I'm gong to close #451 since it now can be taken care of as a plugin/external dependency.

@stefanpenner
Copy link
Contributor

Sounds good. Eventually we plan to bundle a good component/addon blueprint

stefanpenner added a commit that referenced this pull request Apr 27, 2014
Allow a different Blueprint directory to be specified for Init and New commands
@stefanpenner stefanpenner merged commit 588beef into ember-cli:master Apr 27, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants