Skip to content

fix(migrations): cf migration - ensure full check runs for all imports#53637

Closed
jessicajaniuk wants to merge 1 commit intoangular:mainfrom
jessicajaniuk:imports-fix
Closed

fix(migrations): cf migration - ensure full check runs for all imports#53637
jessicajaniuk wants to merge 1 commit intoangular:mainfrom
jessicajaniuk:imports-fix

Conversation

@jessicajaniuk
Copy link
Copy Markdown
Contributor

In cases where CommonModule was unsafe to remove but other imports were present, the symbol check would be skipped. This should run for all the possibly removed symbols for safety.

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

In cases where CommonModule was unsafe to remove but other imports were present, the symbol check would be skipped. This should run for all the possibly removed symbols for safety.
@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 19, 2023
@ngbot ngbot bot added this to the Backlog milestone Dec 19, 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 19, 2023
@atscott
Copy link
Copy Markdown
Contributor

atscott commented Dec 19, 2023

This PR was merged into the repository by commit 8e21787.

@atscott atscott closed this in 8e21787 Dec 19, 2023
atscott pushed a commit that referenced this pull request Dec 19, 2023
#53637)

In cases where CommonModule was unsafe to remove but other imports were present, the symbol check would be skipped. This should run for all the possibly removed symbols for safety.

PR Close #53637
@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 19, 2024
ChellappanRajan pushed a commit to ChellappanRajan/angular that referenced this pull request Jan 23, 2024
angular#53637)

In cases where CommonModule was unsafe to remove but other imports were present, the symbol check would be skipped. This should run for all the possibly removed symbols for safety.

PR Close angular#53637
rlmestre pushed a commit to rlmestre/angular that referenced this pull request Jan 26, 2024
angular#53637)

In cases where CommonModule was unsafe to remove but other imports were present, the symbol check would be skipped. This should run for all the possibly removed symbols for safety.

PR Close angular#53637
amilamen pushed a commit to amilamen/angular that referenced this pull request Jan 26, 2024
angular#53637)

In cases where CommonModule was unsafe to remove but other imports were present, the symbol check would be skipped. This should run for all the possibly removed symbols for safety.

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

4 participants