Skip to content

fix(migrations): CF migration only remove newlines of changed template content#53508

Closed
jessicajaniuk wants to merge 1 commit intoangular:mainfrom
jessicajaniuk:format-newlines
Closed

fix(migrations): CF migration only remove newlines of changed template content#53508
jessicajaniuk wants to merge 1 commit intoangular:mainfrom
jessicajaniuk:format-newlines

Conversation

@jessicajaniuk
Copy link
Copy Markdown
Contributor

The formatting logic would eliminate all newlines in updated template code. This adds start and end markers for tracking when the formatter is in a block of template code that changed or not. It should leave behind any newlines that are outside of a migrated section.

fixes: #53494

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

…e content

The formatting logic would eliminate all newlines in updated template code. This adds start and end markers for tracking when the formatter is in a block of template code that changed or not. It should leave behind any newlines that are outside of a migrated section.

fixes: angular#53494
@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 11, 2023
@ngbot ngbot bot modified the milestone: Backlog Dec 11, 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 Dec 12, 2023
@alxhub
Copy link
Copy Markdown
Member

alxhub commented Dec 12, 2023

This PR was merged into the repository by commit cc02852.

@alxhub alxhub closed this in cc02852 Dec 12, 2023
alxhub pushed a commit that referenced this pull request Dec 12, 2023
…e content (#53508)

The formatting logic would eliminate all newlines in updated template code. This adds start and end markers for tracking when the formatter is in a block of template code that changed or not. It should leave behind any newlines that are outside of a migrated section.

fixes: #53494

PR Close #53508
@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 12, 2024
ChellappanRajan pushed a commit to ChellappanRajan/angular that referenced this pull request Jan 23, 2024
…e content (angular#53508)

The formatting logic would eliminate all newlines in updated template code. This adds start and end markers for tracking when the formatter is in a block of template code that changed or not. It should leave behind any newlines that are outside of a migrated section.

fixes: angular#53494

PR Close angular#53508
rlmestre pushed a commit to rlmestre/angular that referenced this pull request Jan 26, 2024
…e content (angular#53508)

The formatting logic would eliminate all newlines in updated template code. This adds start and end markers for tracking when the formatter is in a block of template code that changed or not. It should leave behind any newlines that are outside of a migrated section.

fixes: angular#53494

PR Close angular#53508
amilamen pushed a commit to amilamen/angular that referenced this pull request Jan 26, 2024
…e content (angular#53508)

The formatting logic would eliminate all newlines in updated template code. This adds start and end markers for tracking when the formatter is in a block of template code that changed or not. It should leave behind any newlines that are outside of a migrated section.

fixes: angular#53494

PR Close angular#53508
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.

Feature Request: Control flow schematic formatter option to preserve newlines

4 participants