-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Handle nested classes in migrations #52309
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Fixes that the block entities migration was only processing top-level classes. Nested classes could come up during unit tests.
Fixes that the control flow migration was only processing top-level classes. Nested classes could come up during unit tests.
744d4fa
to
2b82d34
Compare
Caretaker note: this one passed the presubmit earlier, but I had to push again to resolve merge conflicts. |
This PR was merged into the repository by commit c993e9a. |
) Fixes that the control flow migration was only processing top-level classes. Nested classes could come up during unit tests. PR Close #52309
) Fixes that the control flow migration was only processing top-level classes. Nested classes could come up during unit tests. PR Close #52309
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. |
…ngular#52309) Fixes that the block entities migration was only processing top-level classes. Nested classes could come up during unit tests. PR Close angular#52309
…ular#52309) Fixes that the control flow migration was only processing top-level classes. Nested classes could come up during unit tests. PR Close angular#52309
…ngular#52309) Fixes that the block entities migration was only processing top-level classes. Nested classes could come up during unit tests. PR Close angular#52309
…ular#52309) Fixes that the control flow migration was only processing top-level classes. Nested classes could come up during unit tests. PR Close angular#52309
Updates a couple of migrations that were only looking at classes defined at the top level of the file.