Skip to content

fix(migrations): Fix NgStyle migration#67714

Open
aparzi wants to merge 1 commit intoangular:mainfrom
aparzi:fix-comma-ngstyle-migration
Open

fix(migrations): Fix NgStyle migration#67714
aparzi wants to merge 1 commit intoangular:mainfrom
aparzi:fix-comma-ngstyle-migration

Conversation

@aparzi
Copy link
Contributor

@aparzi aparzi commented Mar 16, 2026

This fixes an issue where when removing NgStyle from the imports array of a component, an extra trailing comma would be left behind if it was the last element in that component`.

PR Checklist

Please check if your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • angular.dev application / infrastructure changes
  • Other... Please describe:

Does this PR introduce a breaking change?

  • Yes
  • No

@pullapprove pullapprove bot requested a review from atscott March 16, 2026 20:46
@angular-robot angular-robot bot added the area: migrations Issues related to `ng update`/`ng generate` migrations label Mar 16, 2026
@ngbot ngbot bot added this to the Backlog milestone Mar 16, 2026
Copy link
Contributor

@atscott atscott left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

AGENT: I have left a few inline suggestions for your consideration.

This fixes an issue where when removing NgStyle from the imports array of a component, an extra trailing comma would be left behind if it was the last element in that component`.
@aparzi aparzi force-pushed the fix-comma-ngstyle-migration branch from 7f4022d to 54dff79 Compare March 17, 2026 10:26
@aparzi aparzi requested a review from atscott March 17, 2026 10:26
@aparzi
Copy link
Contributor Author

aparzi commented Mar 17, 2026

AGENT: I have left a few inline suggestions for your consideration.

Fixed and updated the commit

@aparzi
Copy link
Contributor Author

aparzi commented Mar 17, 2026

@atscott @JeanMeche

Is this a legitimate error? I don't understand why it would affect my fix.

@JeanMeche
Copy link
Member

It's a pre-exisiting error. See #67719.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: migrations Issues related to `ng update`/`ng generate` migrations

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants