scribe-org / scribe-org/Scribe-Server
Add handler tests for GET /api/v1/data-version/{lang}
Nobody has claimed this yet.
- 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 endpoint clients should use to decide whether to re-download a language pack.
Covers the <datatype>_last_modified map shape, the 400/404/500 paths, an empty map for a language with zero data types, and the 1970-01-01 fallback when a table has no lastModified column.
A wrong or stale date here makes clients either miss updates or re-download everything, and neither failure is visible server-side.
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
Find the GET /api/v1/data-version/{lang} handler and nearby handler tests, then run the existing API test suite to understand its conventions. Add coverage for the map shape, 400/404/500 responses, empty language data, and the 1970-01-01 fallback; done means each listed path is asserted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend, testing
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100