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

Reactive cycle improvements #17

Merged
merged 9 commits into from
Nov 26, 2024
Merged

Reactive cycle improvements #17

merged 9 commits into from
Nov 26, 2024

Conversation

cesarParra
Copy link
Owner

Introduces improvements to the reactive cycles of signals and resources.

  • Previously, signals holding objects were not correct evaluated for changes, causing unnecessary notifications to observers. Now, even if the signal holds an object, the object is checked for deep equality of its properties and values (as opposed to checking for object identity).
  • Resource reactive cycles have also been improved to avoid unnecessary notifications.
    • A resource's source function is never evaluated unless fetchWhen is true
    • The deepCheck evaluation done for signals is also now done for resource source functions, avoiding unnecessary re-evaluation when these return an object

@cesarParra cesarParra merged commit 2fa354a into main Nov 26, 2024
1 check passed
@cesarParra cesarParra deleted the resource-improvements branch November 26, 2024 12:32
Copy link

🎉 This PR is included in version 1.0.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant