Repository navigation
fix(frontend): bound API reads and expose retry actions (#70) - #189
Open
isaacsamual994-lang wants to merge 1 commit into
Open
isaacsamual994-lang wants to merge 1 commit into
isaacsamual994-lang wants to merge 1 commit into
Conversation
isaacsamual994-lang
marked this pull request as ready for review
October 25, 2026 08:06
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes the indefinitely-loading GET screens covered by #70 and adds manual retry feedback without silently re-submitting writes.
withRequestTimeoutfor bounded async API reads, including JSON parsing. Use a safe default of 15 seconds, configurable viaNEXT_PUBLIC_API_REQUEST_TIMEOUT_MS(1–120000 milliseconds) or a per-requesttimeoutMsoption. Document this in both.env.exampletemplates anddocs/frontend-api-timeouts.md.ApiRequestTimeoutErrorand abort the underlying fetch. On component unmount or filter/wallet changes, cancel with a distinctAbortError. A late response cannot settle the timeout wrapper even when the underlying transport ignores abort./api/tasks) and My Submissions (/api/my-submissions) screens. Add a visible loading status and user-triggered Retry loading bounties / Retry loading history options without losing filters, pagination or connected-wallet context.Verification (local macOS)
request-timeout.ts,request-timeout.test.ts,BountyList.tsx, andBountyList.test.tsxfiles: 22 timeout/configuration/cancellation/retry tests and 3 UI markup tests. The UI test setup used real React/ReactDOM with simple stand-ins for existing design-system primitives.tsc --noEmitfor the exact changed timeout utility, bounty hook, bounty list and corresponding tests, with lightweight UI stubs and the repository's actualtask-workflowtypes..ts/.tsxfiles, including both pages, withtranspileModulediagnostics (syntax check, not a substitute for full app typecheck).git diff --checkand clean committed working tree.Frontend CIandDependency Vulnerability Scanareaction_requiredfor this fork PR, awaiting the maintainers' approval to execute. No CI result is claimed.GrantFox / payment status
Applied under the GitHub login
isaacsamual994-langthrough GrantFox OSS before coding. The issue is still unassigned, the label is Maybe Rewarded, and neither reward eligibility nor payment has been confirmed. Assignment/eligibility clarification was requested in the issue application comment.Closes #70