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 bound ngIfElse cases ignore line breaks #53435

Closed
wants to merge 1 commit into from

Conversation

jessicajaniuk
Copy link
Contributor

When using ternaries or other expressions in bound if / else cases, it is possible that line breaks could end up affecting template replacement.

fixes: #53428

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

…ne breaks

When using ternaries or other expressions in bound if / else cases, it is possible that line breaks could end up affecting template replacement.

fixes: angular#53428
@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 Dec 7, 2023
@ngbot ngbot bot added this to the Backlog milestone Dec 7, 2023
@pkozlowski-opensource pkozlowski-opensource 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 Dec 8, 2023
@ngbot
Copy link

ngbot bot commented Dec 8, 2023

I see that you just added the action: merge label, but the following checks are still failing:
    failure status "google-internal-tests" is failing
    pending status "mergeability" is pending

If you want your PR to be merged, it has to pass all the CI checks.

If you can't get the PR to a green state due to flakes or broken main, please try rebasing to main and/or restarting the CI job. If that fails and you believe that the issue is not due to your change, please contact the caretaker and ask for help.

@pkozlowski-opensource pkozlowski-opensource added the merge: caretaker note Alert the caretaker performing the merge to check the PR for an out of normal action needed or note label Dec 8, 2023
@pkozlowski-opensource
Copy link
Member

caretaker note: G3 failures are unrelated

@jessicajaniuk jessicajaniuk removed the merge: caretaker note Alert the caretaker performing the merge to check the PR for an out of normal action needed or note label Dec 8, 2023
@alxhub
Copy link
Member

alxhub commented Dec 8, 2023

This PR was merged into the repository by commit a027679.

@alxhub alxhub closed this in a027679 Dec 8, 2023
alxhub pushed a commit that referenced this pull request Dec 8, 2023
…ne breaks (#53435)

When using ternaries or other expressions in bound if / else cases, it is possible that line breaks could end up affecting template replacement.

fixes: #53428

PR Close #53435
josephperrott pushed a commit to josephperrott/angular that referenced this pull request Dec 11, 2023
…ne breaks (angular#53435)

When using ternaries or other expressions in bound if / else cases, it is possible that line breaks could end up affecting template replacement.

fixes: angular#53428

PR Close angular#53435
@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 8, 2024
ChellappanRajan pushed a commit to ChellappanRajan/angular that referenced this pull request Jan 23, 2024
…ne breaks (angular#53435)

When using ternaries or other expressions in bound if / else cases, it is possible that line breaks could end up affecting template replacement.

fixes: angular#53428

PR Close angular#53435
rlmestre pushed a commit to rlmestre/angular that referenced this pull request Jan 26, 2024
…ne breaks (angular#53435)

When using ternaries or other expressions in bound if / else cases, it is possible that line breaks could end up affecting template replacement.

fixes: angular#53428

PR Close angular#53435
danieljancar pushed a commit to danieljancar/angular that referenced this pull request Jan 26, 2024
…ne breaks (angular#53435)

When using ternaries or other expressions in bound if / else cases, it is possible that line breaks could end up affecting template replacement.

fixes: angular#53428

PR Close angular#53435
amilamen pushed a commit to amilamen/angular that referenced this pull request Jan 26, 2024
…ne breaks (angular#53435)

When using ternaries or other expressions in bound if / else cases, it is possible that line breaks could end up affecting template replacement.

fixes: angular#53428

PR Close angular#53435
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 migration: whitespace + new lines in condition produces invalid code
4 participants