fix(core): ensure default path is set for control flow migration#64298
Closed
aparzi wants to merge 1 commit intoangular:20.3.xfrom
Closed
fix(core): ensure default path is set for control flow migration#64298aparzi wants to merge 1 commit intoangular:20.3.xfrom
aparzi wants to merge 1 commit intoangular:20.3.xfrom
Conversation
When running the control flow migration via `ng update`, the path parameter could be undefined. This change ensures a default value of './' is used when no path is explicitly provided, making the migration work consistently between `ng update` and `ng generate` commands. Fixes angular#63294
14 tasks
crisbeto
reviewed
Oct 8, 2025
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When running the control flow migration via
ng update, the path parameter could be undefined. This change ensures a default value of './' is used when no path is explicitly provided, making the migration work consistently betweenng updateandng generatecommands.Fixes #63294
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue occurred because ng update doesn't apply schema defaults like ng generate does. This fix handles both cases by explicitly setting default values in the migration code.
Issue Number: #63294
What is the new behavior?
This change ensures a default value of './' is used when no path is explicitly provided, making the migration work consistently between ng update and ng generate commands.
Does this PR introduce a breaking change?