Skip to content

fix(@schematics/angular): the ng-new schematic should not prompt for style nor for routing #15207

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

Merged
merged 2 commits into from
Aug 2, 2019

Conversation

ahasall
Copy link
Contributor

@ahasall ahasall commented Jul 30, 2019

closes #13383

@ahasall ahasall force-pushed the fix-#13383 branch 2 times, most recently from 8e98683 to aed10da Compare July 30, 2019 22:10
@ahasall ahasall changed the title fix(schematics/angular): the ng-new schematic should not prompt for style nor routing fix(@schematics/angular): the ng-new schematic should not prompt for style nor routing Jul 30, 2019
@ahasall ahasall changed the title fix(@schematics/angular): the ng-new schematic should not prompt for style nor routing fix(@schematics/angular): the ng-new schematic should not prompt for style nor for routing Jul 30, 2019
@clydin clydin added the target: major This PR is targeted for the next major release label Jul 31, 2019
@ahasall ahasall force-pushed the fix-#13383 branch 2 times, most recently from d2ffe0e to f9c389e Compare July 31, 2019 20:23
Copy link
Contributor

@Splaktar Splaktar left a comment

Choose a reason for hiding this comment

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

LGTM otherwise.

@@ -307,6 +307,10 @@ export default function (options: ApplicationOptions): Rule {
}
validateProjectName(options.name);
options.prefix = options.prefix || 'app';
// This line and the one above shouldn't be needed, but at the moment they are.
// This is because the default value defined in the schema.json file is not
// correctly set when this schematic is run from another schematic.
Copy link
Contributor

Choose a reason for hiding this comment

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

We should probably open an issue and add a link to it here w/ a TODO to remove this when that issue is resolved.

@kyliau kyliau merged commit c4a3262 into angular:master Aug 2, 2019
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 13, 2019
@ahasall ahasall deleted the fix-#13383 branch November 10, 2019 02:00
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
target: major This PR is targeted for the next major release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Unnecessary prompts for ng new when using create application false (i.e. Conditional Prompts)
6 participants