Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Fix rapid updating of useAsyncIterState's state yields the first update instead the last one in the series #44

Merged
merged 1 commit into from
Jan 8, 2025

Conversation

shtaif
Copy link
Owner

@shtaif shtaif commented Jan 8, 2025

No description provided.

@shtaif shtaif self-assigned this Jan 8, 2025
@shtaif shtaif marked this pull request as ready for review January 8, 2025 17:09
@shtaif shtaif merged commit b11b5a5 into master Jan 8, 2025
6 checks passed
@shtaif shtaif deleted the fix-use-async-iter-state-rapid-updates branch January 8, 2025 17:12
shtaif pushed a commit that referenced this pull request Jan 8, 2025
## [0.5.1](v0.5.0...v0.5.1) (2025-01-08)

### Bug Fixes

* **useAsyncIterState:** disallow user manipulation of the state iterable's current value property ([#43](#43)) ([6dd5ac5](6dd5ac5))
* **useAsyncIterState:** rapidly updating state yields the first update instead of the last update's value ([#44](#44)) ([b11b5a5](b11b5a5))

### Documentation

* **useAsyncIterState:** missing documentations for the state iterable's added current value property ([#42](#42)) ([675331f](675331f))
Copy link

github-actions bot commented Jan 8, 2025

🎉 This PR is included in version 0.5.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

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

Successfully merging this pull request may close these issues.

1 participant