[BUG] React Hook dependency warnings
- Dominant language
- TypeScript
- Stars
- 716
- Forks
- 1.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 35
Description
### Describe the bug.
Running `npm run lint` produces 8 warnings across 7 files related to `react-hooks/exhaustive-deps`.
These warnings indicate stale closure bugs where useEffect/useMemo hooks may not re-run when their dependencies change, causing unexpected behavior.
### Expected behavior
`npm run lint` should produce zero React Hook dependency warnings.
### Screenshots
### How to Reproduce
Run `npm run lint`
### 🖥️ Device Information [optional]
_No response_
### 👀 Have you checked for similar open issues?
- [x] I checked and didn't find similar issue
### 🏢 Have you read the Contributing Guidelines?
- [x] I have read the [Contributing Guidelines](https://github.com/asyncapi/.github/blob/master/CONTRIBUTING.md)
### Are you willing to work on this issue ?
Yes I am willing to submit a PR!
Contributor guide
Research direction
Run `npm run lint` and inspect the seven files reported with `react-hooks/exhaustive-deps` warnings. Trace each affected useEffect or useMemo dependency list, then rerun the lint command; done means it reports zero React Hook dependency warnings without introducing stale-closure behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100