scribe-org / scribe-org/Scribe-Server
Add handler tests for GET /api/v1/data/{lang}
Open
Beginner friendly
Nobody has claimed this yet.
-priority-
blocked
testing
- Dominant language
- Go
- Stars
- 12
- Forks
- 14
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 4
Description
Terms
- I have searched open and closed feature requests
- I agree to follow Scribe-Server's Code of Conduct
Description
Covers 200, 400 on an invalid code, 404 on unsupported, two distinct 500s, and the partial-failure path where a data type whose table fetch fails is skipped while the rest are returned.
Contribution
No response
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
Locate the handler for GET /api/v1/data/{lang} and inspect the repository's existing handler-test conventions. Add coverage for 200, invalid-code 400, unsupported 404, both 500 cases, and partial failure where one data type is skipped; done means all listed response paths are tested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend, testing
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 74/100