Search Timeout Errors Shouldn't Take Over Full Page
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 9.9k
- Forks
- 471
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 117
Description
We tackled a variant of this in #1175 but now when search pages time out, we wipe out the search page table still. We should instead show an error at the end of the table that the next page failed to load, and allow the user to retry/keep searching, without wiping out intermediate results.
This is important for slower searches with lots of pages, where there's chances of later pages to time out even if earlier pages returned.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the search page timeout handling and read the related work in issue #1175. Reproduce a timeout on a later search page, then verify that earlier results remain visible, the failure appears at the end of the table, and retry or continued searching remains possible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend, search
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100