Thanks to visit codestin.com
Credit goes to github.com

Skip to content

fix(migrations): preserve comments when removing unused imports #61674

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

Closed
wants to merge 1 commit into from

Conversation

crisbeto
Copy link
Member

Updates the unused imports schematic to preserve comments inside the array. THis is necessary for some internal use cases.

Updates the unused imports schematic to preserve comments inside the array. THis is necessary for some internal use cases.
@crisbeto crisbeto requested a review from devversion May 26, 2025 07:21
@crisbeto crisbeto 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 labels May 26, 2025
@angular-robot angular-robot bot added the area: migrations Issues related to `ng update` migrations label May 26, 2025
@ngbot ngbot bot added this to the Backlog milestone May 26, 2025
@crisbeto crisbeto 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 May 26, 2025
thePunderWoman pushed a commit that referenced this pull request May 26, 2025
Updates the unused imports schematic to preserve comments inside the array. THis is necessary for some internal use cases.

PR Close #61674
thePunderWoman pushed a commit that referenced this pull request May 26, 2025
Updates the unused imports schematic to preserve comments inside the array. THis is necessary for some internal use cases.

PR Close #61674
@thePunderWoman
Copy link
Contributor

This PR was merged into the repository by commit 04656d0.

The changes were merged into the following branches: main, 19.2.x, 20.0.x

crisbeto added a commit to crisbeto/angular that referenced this pull request May 27, 2025
Follow-up to angular#61674 where we were leaving behind some whitespace, e.g. `[One, Two, Three]` would turn into `[One ]`. These changes only preserve the whitespace if the node is preceded by a newline.

This wasn't caught by tests, because they were stripping away whitespaces before asserting. I've also reworked the tests to be sensitive to formatting changes.
kirjs pushed a commit that referenced this pull request May 30, 2025
…on (#61698)

Follow-up to #61674 where we were leaving behind some whitespace, e.g. `[One, Two, Three]` would turn into `[One ]`. These changes only preserve the whitespace if the node is preceded by a newline.

This wasn't caught by tests, because they were stripping away whitespaces before asserting. I've also reworked the tests to be sensitive to formatting changes.

PR Close #61698
kirjs pushed a commit that referenced this pull request May 30, 2025
…on (#61698)

Follow-up to #61674 where we were leaving behind some whitespace, e.g. `[One, Two, Three]` would turn into `[One ]`. These changes only preserve the whitespace if the node is preceded by a newline.

This wasn't caught by tests, because they were stripping away whitespaces before asserting. I've also reworked the tests to be sensitive to formatting changes.

PR Close #61698
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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.

3 participants