Review useQueryInconsistencyInvalidator usage in hardwareDetails/treeDetails
Open
bug
Frontend
- Dominant language
- Python
- Stars
- 9
- Forks
- 31
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 16
Description
Current implementation uses useEffect to compare router state with query data, invalidating all queries made and causing duplicated requests at some scenarios, we should evaluate its usage and check if its possible to fix the inconsistencies without relying into re-fetching all the data
Related to #1710
Contributor guide
Research direction
Start by tracing useQueryInconsistencyInvalidator usage in hardwareDetails and treeDetails, comparing router state with query data and observing the duplicated requests. The work is done when the inconsistencies are resolved without invalidating all queries and the duplicated requests no longer occur.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100