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(list-atom): make pristine (!dirty) after new initialValue is set #107

Merged
merged 1 commit into from
Feb 14, 2024

Conversation

MiroslavPetrik
Copy link
Member

Fixes #105
This requires the user to control the referential equality of the initialValue for the same values in order to prevent unnecessary updates.

Fixes #105
This requires the user to control the referential equality of the initialValue for the same values in order to prevent unnecessary updates.
@MiroslavPetrik MiroslavPetrik merged commit 170312d into next Feb 14, 2024
1 check passed
github-actions bot pushed a commit that referenced this pull request Feb 14, 2024
## [4.0.13-next.1](v4.0.12...v4.0.13-next.1) (2024-02-14)

### Bug Fixes

* **list-atom:** make pristine (!dirty) after new initialValue is set ([#107](#107)) ([170312d](170312d)), closes [#105](#105)
Copy link

🎉 This PR is included in version 4.0.13-next.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

MiroslavPetrik added a commit that referenced this pull request Feb 14, 2024
* fix(list-atom): make pristine (!dirty) after new initialValue is set (#107)

Fixes #105
This requires the user to control the referential equality of the initialValue for the same values in order to prevent unnecessary updates.

* chore(release): 4.0.13-next.1

## [4.0.13-next.1](v4.0.12...v4.0.13-next.1) (2024-02-14)

### Bug Fixes

* **list-atom:** make pristine (!dirty) after new initialValue is set ([#107](#107)) ([170312d](170312d)), closes [#105](#105)

---------

Co-authored-by: semantic-release-bot <[email protected]>
@MiroslavPetrik MiroslavPetrik deleted the fix-105 branch February 14, 2024 14:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant