stacklok / stacklok/toolhive-studio
Test coverage: Global error boundary
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 167
- Forks
- 24
- Avg merge
- 11h 32m
- Merged PRs (30d)
- 91
Description
What to do
Stub 500 on the root loader → error screen appears; clicking Retry recovers.
Files to cover
- src/common/components/error/base-error-screen.tsx
- src/common/components/error/connection-refused-error.tsx
- src/common/components/error/keyring-error.tsx
- src/common/components/error/utils.ts
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 with the root loader and the listed error components: base-error-screen.tsx, connection-refused-error.tsx, keyring-error.tsx, and utils.ts. Stub a 500 response from the root loader, then verify that the error screen appears and that clicking Retry recovers. Done means the global error boundary behavior and the listed error components have test coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100