fortedigital / fortedigital/Optimizely.ContentUsage

Search input changes race condition

Open
#87 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
C#
Stars
2
Forks
2
PR merge metrics
No merged PRs in 30d

Description

When we enter some value to search input on first view (with Content types list) and after that we change it again but previous triggered request doesn't complete the latest value'll be changed to the first (to that value which started the first GET request).

Propositions to solve this issue:
- add spinner + disable inputs (search and dropdowns) when loading (you can try to use useNavigation hook from react-router)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start at the first view containing the Content types list and trace the search input through the GET request, reproducing the issue by changing the value before the first request completes. Review the suggested useNavigation hook from react-router; done means an earlier request can no longer replace the latest search value, with loading behavior matching the issue's proposal.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, react
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.