Navigation Menu

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 Blueprint to determine if entity name is required. #1631

Conversation

rwjblue
Copy link
Member

@rwjblue rwjblue commented Aug 10, 2014

Prior to this change an entity name was always required (which makes sense for all of our bundled blueprints). In some cases you just want to run a generator that does not need a name (for example you are just initializing some required files for an addon).

This change still requires an entity name by default, but allows the blueprint to override the normalizeEntityName and prevent the error.

Prior to this change an entity name was always required (which makes
sense for all of our bundled blueprints). In some cases you just want to
run a generator that does not need a name (for example you are just
initializing some required files for an addon).

This change still requires an entity name by default, but allows the
blueprint to override the `normalizeEntityName` and prevent the error.
rwjblue added a commit that referenced this pull request Aug 10, 2014
…-entityname-is-required

Allow Blueprint to determine if entity name is required.
@rwjblue rwjblue merged commit 9a192e9 into ember-cli:master Aug 10, 2014
@rwjblue rwjblue deleted the allow-blueprint-to-determine-if-entityname-is-required branch August 10, 2014 14:42
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.

None yet

2 participants