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

Explicitly set non-reactive context when entering user-written code outside of the template update function #49906

Conversation

pkozlowski-opensource
Copy link
Member

@pkozlowski-opensource pkozlowski-opensource commented Apr 18, 2023

Explicitly set non-reactive context when entering user-written code outside of the template update function:

  • @Input setters
  • query result setters

@pkozlowski-opensource pkozlowski-opensource force-pushed the reactivity_non_reactive_ctx_user_code branch 4 times, most recently from 3bb7534 to 6400c34 Compare April 19, 2023 13:02
@pkozlowski-opensource pkozlowski-opensource changed the title Reactivity non reactive ctx user code Explicitly set non-reactive context when entering user-written code outside of the template update function Apr 19, 2023
This change explicitly resets a reactive consumer before setting inputs
on directive instances. This is to assure that any potential input setters
do _not_ run in the reactive context.
@pkozlowski-opensource pkozlowski-opensource force-pushed the reactivity_non_reactive_ctx_user_code branch from 6400c34 to e93014d Compare April 19, 2023 13:14
@pkozlowski-opensource pkozlowski-opensource marked this pull request as ready for review April 19, 2023 13:16
@pkozlowski-opensource pkozlowski-opensource added action: review The PR is still awaiting reviews from at least one requested reviewer area: core Issues related to the framework runtime labels Apr 19, 2023
@ngbot ngbot bot added this to the Backlog milestone Apr 19, 2023
@pkozlowski-opensource pkozlowski-opensource added cross-cutting: signals target: rc This PR is targeted for the next release-candidate labels Apr 19, 2023
This commit assures that query results setters run when there is no active
reactive consumer set.
@pkozlowski-opensource pkozlowski-opensource force-pushed the reactivity_non_reactive_ctx_user_code branch from e93014d to c4c25c6 Compare April 19, 2023 14:04
@atscott atscott 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 Apr 19, 2023
@angular-robot
Copy link
Contributor

angular-robot bot commented Apr 19, 2023

This PR was merged into the repository by commit 1dc919a.

angular-robot bot pushed a commit that referenced this pull request Apr 19, 2023
This change explicitly resets a reactive consumer before setting inputs
on directive instances. This is to assure that any potential input setters
do _not_ run in the reactive context.

PR Close #49906
angular-robot bot pushed a commit that referenced this pull request Apr 19, 2023
This commit assures that query results setters run when there is no active
reactive consumer set.

PR Close #49906
@angular-robot angular-robot bot closed this in 4031802 Apr 19, 2023
angular-robot bot pushed a commit that referenced this pull request Apr 19, 2023
This commit assures that query results setters run when there is no active
reactive consumer set.

PR Close #49906
@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 May 20, 2023
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: core Issues related to the framework runtime cross-cutting: signals target: rc This PR is targeted for the next release-candidate
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants