Thanks to visit codestin.com
Credit goes to github.com

Skip to content

fix(core): run root effects in creation order #60534

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

Closed
wants to merge 1 commit into from

Conversation

alxhub
Copy link
Member

@alxhub alxhub commented Mar 24, 2025

Previously, the order in which root effects were executed was non-deterministic and relied on the order in which signal graph dirty notifications were propagated. With this commit, root effects are always run in creation order.

Previously, the order in which root effects were executed was
non-deterministic and relied on the order in which signal graph dirty
notifications were propagated. With this commit, root effects are always run
in creation order.
@angular-robot angular-robot bot added the area: core Issues related to the framework runtime label Mar 24, 2025
@ngbot ngbot bot added this to the Backlog milestone Mar 24, 2025
@alxhub alxhub added target: major This PR is targeted for the next major release action: merge The PR is ready for merge by the caretaker labels Apr 1, 2025
@thePunderWoman
Copy link
Contributor

This PR was merged into the repository by commit a611b23.

The changes were merged into the following branches: main

@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 3, 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: core Issues related to the framework runtime target: major This PR is targeted for the next major release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants