Skip to content

ng update --next should show commands with --next #10247

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.

Sign up for GitHub

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

Jump to bottom
Closed
StephenFluin opened this issue Apr 9, 2018 · 1 comment
Closed

ng update --next should show commands with --next #10247

StephenFluin opened this issue Apr 9, 2018 · 1 comment
Labels
P5 The team acknowledges the request but does not plan to address it, it remains open for discussion
Milestone
v6.0.0

Comments

@StephenFluin
Copy link
Contributor

Versions

Angular CLI: 6.0.0-rc.2
Node: 9.2.0
OS: linux x64
Angular: 6.0.0-rc.3
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

@angular/cli: 6.0.0-rc.2
@angular-devkit/architect: 0.5.4
@ngtools/json-schema: 1.2.0
@schematics/update: 0.5.4
typescript: 2.7.2
webpack: error

Repro steps

ng update --next

Observed behavior

Recommendations look like:
@angular/animations 5.2.9 -> 6.0.0-rc.3 ng update @angular/animations

Desired behavior

Show the command that will install the indicated version, aka @angular/animations 5.2.9 -> 6.0.0-rc.3 ng update @angular/animations --next
@hansl hansl added this to the v6.0.0 milestone Apr 12, 2018
@hansl hansl added severity3: broken P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent P5 The team acknowledges the request but does not plan to address it, it remains open for discussion and removed 6.0.0-rc severity3: broken P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent labels Apr 12, 2018
@hansl hansl mentioned this issue Apr 14, 2018
Merged
hansl added a commit to hansl/devkit that referenced this issue Apr 14, 2018
@hansl
fix(@schematics/update): group packages together
57c9adc 
Packages will be reduced to their package name. Added the spec for the new
packageGroupName argument (default to the first item of the packageGroup).

Fixes angular/angular-cli#10248
Fixes angular/angular-cli#10247
filipesilva pushed a commit to angular/devkit that referenced this issue Apr 14, 2018
@hansl @filipesilva
fix(@schematics/update): group packages together
6a9bd36 
Packages will be reduced to their package name. Added the spec for the new
packageGroupName argument (default to the first item of the packageGroup).

Fixes angular/angular-cli#10248
Fixes angular/angular-cli#10247
hansl added a commit that referenced this issue Jun 6, 2018
@hansl
fix(@schematics/update): group packages together
53f9d96 
Packages will be reduced to their package name. Added the spec for the new
packageGroupName argument (default to the first item of the packageGroup).

Fixes #10248
Fixes #10247
@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 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
P5 The team acknowledges the request but does not plan to address it, it remains open for discussion
Projects
None yet
Milestone
v6.0.0
Development

No branches or pull requests
3 participants
@StephenFluin @hansl @filipesilva