fix(migrations): flip the default standalone flag in route-lazy-loadi…#58474
fix(migrations): flip the default standalone flag in route-lazy-loadi…#58474eneajaho wants to merge 1 commit intoangular:mainfrom
Conversation
There was a problem hiding this comment.
Thanks for the change, the code looks good 👍 I'd like to propose a followup refactoring (as a separate PR) to move this function into a common migration utils (and potentially add some tests for it), so that we can reuse it in existing (including this one) and new migrations.
…ng migration Before v19, the default value of the standalone flag was false, this code change flips the logic in the migration to make it true by default.
9923a3e to
732df24
Compare
|
Needed to force push to fix the lint error. |
|
Caretaker note: presubmit looks good, this PR is ready for merge. |
|
This PR was merged into the repository by commit 6819d6a. The changes were merged into the following branches: main, 19.0.x |
|
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. |
…ng migration
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 Number: #58473
What is the new behavior?
Now the migration will work fine even when the standalone flag is not there at all (v19 defaults to true)
Does this PR introduce a breaking change?