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(migrations): CF migration - ensure NgIfElse attributes are properly removed #53298

Closed
wants to merge 1 commit into from

Conversation

jessicajaniuk
Copy link
Contributor

the attribute in question was assumed to be at the start of the replaced content, but it could be later, too.

fixes: #53288

PR Checklist

Please check if your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

  • Bugfix

Does this PR introduce a breaking change?

  • Yes
  • No

…ly removed

the attribute in question was assumed to be at the start of the replaced content, but it could be later, too.

fixes: angular#53288
@jessicajaniuk jessicajaniuk added action: review The PR is still awaiting reviews from at least one requested reviewer target: patch This PR is targeted for the next patch release area: migrations Issues related to `ng update` migrations labels Nov 30, 2023
@ngbot ngbot bot modified the milestone: Backlog Nov 30, 2023
@jessicajaniuk jessicajaniuk added action: merge The PR is ready for merge by the caretaker and removed action: review The PR is still awaiting reviews from at least one requested reviewer labels Nov 30, 2023
@dylhunn
Copy link
Contributor

dylhunn commented Dec 1, 2023

This PR was merged into the repository by commit 1c1e8c4.

dylhunn pushed a commit that referenced this pull request Dec 1, 2023
…ly removed (#53298)

the attribute in question was assumed to be at the start of the replaced content, but it could be later, too.

fixes: #53288

PR Close #53298
@dylhunn dylhunn closed this in 1c1e8c4 Dec 1, 2023
tbondwilkinson pushed a commit to tbondwilkinson/angular that referenced this pull request Dec 6, 2023
…ly removed (angular#53298)

the attribute in question was assumed to be at the start of the replaced content, but it could be later, too.

fixes: angular#53288

PR Close angular#53298
@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 Jan 1, 2024
ChellappanRajan pushed a commit to ChellappanRajan/angular that referenced this pull request Jan 23, 2024
…ly removed (angular#53298)

the attribute in question was assumed to be at the start of the replaced content, but it could be later, too.

fixes: angular#53288

PR Close angular#53298
rlmestre pushed a commit to rlmestre/angular that referenced this pull request Jan 26, 2024
…ly removed (angular#53298)

the attribute in question was assumed to be at the start of the replaced content, but it could be later, too.

fixes: angular#53288

PR Close angular#53298
amilamen pushed a commit to amilamen/angular that referenced this pull request Jan 26, 2024
…ly removed (angular#53298)

the attribute in question was assumed to be at the start of the replaced content, but it could be later, too.

fixes: angular#53288

PR Close angular#53298
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker area: migrations Issues related to `ng update` migrations target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Control flow schematic: [ngIf] + [ngIfElse] + [ngTemplateOutlet] is not migrated properly
3 participants