scribe-org / scribe-org/Scribe-Server
Add handler tests for GET /api/v1/translations
Open
Beginner friendly
Nobody has claimed this yet.
-priority-
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
Tests for the nested word -> wordType -> wordOrder -> {description, translation} response shape and all four error paths.
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
Start at the handler entry point for GET /api/v1/translations and inspect how its nested word, wordType, wordOrder, description, and translation response is produced. Add coverage for that response shape and each of the four error paths, then run the relevant Go handler tests to confirm all cases pass.
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
- 70/100