Skip to content
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

fix(core): ComponentFixture autoDetect respects OnPush flag of … #54824

Closed
wants to merge 1 commit into from

Conversation

atscott
Copy link
Contributor

@atscott atscott commented Mar 11, 2024

…host view

This is a follow-up to #53718 that applies the same logic to the autoDetect feature of the fixture's host view. This now unifies the logic between ApplicationRef and ComponentFixture autodetect.

BREAKING CHANGE: The ComponentFixture autoDetect feature will no longer refresh the component's host view when the component is OnPush and not marked dirty. This exposes existing issues in components which claim to be OnPush but do not correctly call markForCheck when they need to be refreshed. If this change causes test failures, the easiest fix is to change the component to ChangeDetectionStrategy.Default.

…host view

This is a follow-up to angular#53718 that applies the same logic to the
`autoDetect` feature of the fixture's host view. This now unifies the
logic between `ApplicationRef` and `ComponentFixture` autodetect.

BREAKING CHANGE: The `ComponentFixture` `autoDetect` feature will no
longer refresh the component's host view when the component is `OnPush`
and not marked dirty. This exposes existing issues in components which
claim to be `OnPush` but do not correctly call `markForCheck` when they
need to be refreshed. If this change causes test failures, the easiest
fix is to change the component to `ChangeDetectionStrategy.Default`.
@atscott atscott added area: testing Issues related to Angular testing features, such as TestBed breaking changes area: core Issues related to the framework runtime target: major This PR is targeted for the next major release labels Mar 11, 2024
@ngbot ngbot bot added this to the Backlog milestone Mar 11, 2024
@angular-robot angular-robot bot added the detected: breaking change PR contains a commit with a breaking change label Mar 11, 2024
@atscott atscott added the action: global presubmit The PR is in need of a google3 global presubmit label Mar 12, 2024
@atscott
Copy link
Contributor Author

atscott commented Mar 13, 2024

@atscott atscott added the action: merge The PR is ready for merge by the caretaker label Mar 13, 2024
@atscott
Copy link
Contributor Author

atscott commented Mar 13, 2024

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

@atscott atscott closed this in 8cad4e8 Mar 13, 2024
@angular-automatic-lock-bot
Copy link

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 Apr 13, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: global presubmit The PR is in need of a google3 global presubmit action: merge The PR is ready for merge by the caretaker area: core Issues related to the framework runtime area: testing Issues related to Angular testing features, such as TestBed breaking changes detected: breaking change PR contains a commit with a breaking change target: major This PR is targeted for the next major release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants