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

fix(@angular/cli): ng-update migrations not running with --migrate-only #14567

Merged
merged 1 commit into from
May 30, 2019

Conversation

devversion
Copy link
Member

With Angular CLI version 8, migrations cannot be re-run with the
--migrate-only flag as there was a recent regression introduced
in e406f00#diff-0d0a748fb9a38a7ccde08d9b42e70bce as it now passes
a normalized platform path to the engine.createCollection call.

This breaks as there is incorrect logic within
node-modules-engine-host that causes the schematic collection to be
searched within the package.json#schematics entry. This is incorrect
as migration schematics specify their migration schematics in a separate
schematic collection file which is part of package.json#ng-update.

Fixes #14565

With Angular CLI version 8, migrations cannot be re-run with the
`--migrate-only` flag as there was a recent regression introduced
in e406f00#diff-0d0a748fb9a38a7ccde08d9b42e70bce as it now passes
a normalized platform path to the `engine.createCollection` call.

This breaks as there is incorrect logic within
`node-modules-engine-host` that causes the schematic collection to be
searched within the `package.json#schematics` entry. This is incorrect
as migration schematics specify their migration schematics in a separate
schematic collection file which is part of `package.json#ng-update`.

Fixes #14565
@clydin clydin added the target: patch This PR is targeted for the next patch release label May 29, 2019
@devversion devversion added the P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful label May 29, 2019
@alexeagle alexeagle merged commit a57f053 into master May 30, 2019
@clydin clydin deleted the fix/windows-schematic-resolve-collection branch May 30, 2019 19:06
@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
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area: @angular-devkit/schematics P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Running ng update @angular/core --from 7 --to 8 --migrate-only on 8.0.0 does not migrate
4 participants