Skip to content

fix(migrations): CF Migration - ensure bound ngIfElse cases ignore line breaks#53435

Closed
jessicajaniuk wants to merge 1 commit intoangular:mainfrom
jessicajaniuk:whitespace
Closed

fix(migrations): CF Migration - ensure bound ngIfElse cases ignore line breaks#53435
jessicajaniuk wants to merge 1 commit intoangular:mainfrom
jessicajaniuk:whitespace

Conversation

@jessicajaniuk
Copy link
Copy Markdown
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`/`ng generate` 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
Copy Markdown

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
Copy Markdown
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
Copy Markdown
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
@angular-automatic-lock-bot
Copy link
Copy Markdown

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
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`/`ng generate` 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

5 participants