Skip to content

test(migrations): add test for earlier fix#59497

Closed
crisbeto wants to merge 1 commit intoangular:mainfrom
crisbeto:unused-migrations-fix-test
Closed

test(migrations): add test for earlier fix#59497
crisbeto wants to merge 1 commit intoangular:mainfrom
crisbeto:unused-migrations-fix-test

Conversation

@crisbeto
Copy link
Copy Markdown
Member

Adds a test for the fix from #59452 now that we know what caused the issue.

Adds a test for the fix from angular#59452 now that we know what caused the issue.
@crisbeto crisbeto added action: review The PR is still awaiting reviews from at least one requested reviewer target: rc This PR is targeted for the next release-candidate labels Jan 13, 2025
@crisbeto crisbeto requested a review from devversion January 13, 2025 12:40
@angular-robot angular-robot bot added the area: migrations Issues related to `ng update`/`ng generate` migrations label Jan 13, 2025
@ngbot ngbot bot added this to the Backlog milestone Jan 13, 2025
expect(tree.readContent('comp.ts')).toBe(initialContent);
});

it('should handle a file that is present in multiple projects', async () => {
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

I was considering whether to update groupReplacementsByFile to de-duplicate identical text updates as well. Might be worth waiting to see if this comes up again.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LIkely, synchronouslyCombineUnitData needs to be fixed instead of groupReplacementsByFile. As pretty much everything is duplicate.

@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 Jan 13, 2025
@kirjs
Copy link
Copy Markdown
Contributor

kirjs commented Jan 13, 2025

This PR was merged into the repository by commit 9931030.

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

@kirjs kirjs closed this in 9931030 Jan 13, 2025
kirjs pushed a commit that referenced this pull request Jan 13, 2025
Adds a test for the fix from #59452 now that we know what caused the issue.

PR Close #59497
PrajaktaB27 pushed a commit to PrajaktaB27/angular that referenced this pull request Feb 7, 2025
Adds a test for the fix from angular#59452 now that we know what caused the issue.

PR Close angular#59497
@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 Feb 13, 2025
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: rc This PR is targeted for the next release-candidate

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants