fix(migrations): remove error for no matching files in control flow migration#64253
Closed
crisbeto wants to merge 1 commit intoangular:mainfrom
Closed
fix(migrations): remove error for no matching files in control flow migration#64253crisbeto wants to merge 1 commit intoangular:mainfrom
crisbeto wants to merge 1 commit intoangular:mainfrom
Conversation
…igration Now that the control flow migration is running as a part of `ng update`, we need to be a bit forgiving about there not being any matching files since it can break the entire update process. These changes switch the error to a warning and it counts the files for the entire workspace, not the individual projects.
JeanMeche
approved these changes
Oct 6, 2025
Contributor
|
This PR was merged into the repository. The changes were merged into the following branches:
|
This was referenced Oct 8, 2025
crisbeto
added a commit
to crisbeto/angular
that referenced
this pull request
Oct 9, 2025
…igration (angular#64253) Now that the control flow migration is running as a part of `ng update`, we need to be a bit forgiving about there not being any matching files since it can break the entire update process. These changes switch the error to a warning and it counts the files for the entire workspace, not the individual projects. PR Close angular#64253
crisbeto
added a commit
to crisbeto/angular
that referenced
this pull request
Oct 9, 2025
…igration (angular#64253) Now that the control flow migration is running as a part of `ng update`, we need to be a bit forgiving about there not being any matching files since it can break the entire update process. These changes switch the error to a warning and it counts the files for the entire workspace, not the individual projects. PR Close angular#64253
crisbeto
added a commit
to crisbeto/angular
that referenced
this pull request
Oct 9, 2025
…igration (angular#64253) Now that the control flow migration is running as a part of `ng update`, we need to be a bit forgiving about there not being any matching files since it can break the entire update process. These changes switch the error to a warning and it counts the files for the entire workspace, not the individual projects. PR Close angular#64253
crisbeto
added a commit
to crisbeto/angular
that referenced
this pull request
Oct 9, 2025
…igration (angular#64253) Now that the control flow migration is running as a part of `ng update`, we need to be a bit forgiving about there not being any matching files since it can break the entire update process. These changes switch the error to a warning and it counts the files for the entire workspace, not the individual projects. PR Close angular#64253
AndrewKushnir
pushed a commit
that referenced
this pull request
Oct 9, 2025
…igration (#64253) (#64314) Now that the control flow migration is running as a part of `ng update`, we need to be a bit forgiving about there not being any matching files since it can break the entire update process. These changes switch the error to a warning and it counts the files for the entire workspace, not the individual projects. PR Close #64253 PR Close #64314
napulitanfrontend
pushed a commit
to napulitanfrontend/angular
that referenced
this pull request
Oct 10, 2025
…igration (angular#64253) Now that the control flow migration is running as a part of `ng update`, we need to be a bit forgiving about there not being any matching files since it can break the entire update process. These changes switch the error to a warning and it counts the files for the entire workspace, not the individual projects. PR Close angular#64253
|
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.
Now that the control flow migration is running as a part of
ng update, we need to be a bit forgiving about there not being any matching files since it can break the entire update process.These changes switch the error to a warning and it counts the files for the entire workspace, not the individual projects.