meteor / meteor/react-packages
Concurrency issue with useFind
- Dominant language
- JavaScript
- Stars
- 575
- Forks
- 168
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 1
Description
I have found a problem with the current implementation of useFindClient.
A `fetchData` is run synchronously at first render, then useEffect run `cursor.observe({` which watch for changes on cursor.
On my component there is a concurrency issue with changes happening between the first render and the useEffect (so between the first fetchData and the observer creation)
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue identifies useFindClient, fetchData, and cursor.observe as the relevant entry points; start by tracing the first render and the useEffect observer setup. Done means changes occurring between those steps are not missed, with the timing window covered by a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100