Document the config API
Description
The config endpoints lack a single reference for their request/response shapes and error codes, slowing integrators. This issue documents them.
Requirements and context
- Repository scope: StableRoute-Org/Stableroute-backend only.
- Add
docs/config.md covering each config route, its params, response shape, and error codes.
- Cross-reference the handler; keep it accurate to the code.
- Include a request/response example per route.
Suggested execution
- Fork the repo and create a branch
git checkout -b docs/config-01-api
- Implement changes
- Write code in: the relevant module.
- Write comprehensive tests in: cover the new behaviour and edge cases.
- Test and commit
Test and commit
- Run
npm run lint, npm test, and npm run build.
- Cover edge cases: n/a — verify each documented route against source.
- Include the full test output in the PR description.
Example commit message
docs(config): document the API contract
Guidelines
- Minimum 95 percent test coverage for impacted modules.
- Clear, reviewer-focused documentation.
- Timeframe: 96 hours.
Community & contribution rewards
- 💬 Join the StableRoute community on Discord: https://discord.gg/37aCpusvx
- ⭐ This is a GrantFox OSS / Official Campaign task and may be rewarded. When your PR is merged you'll be prompted to rate the project — a 5-star rating is much appreciated.
Document the config API
Description
The config endpoints lack a single reference for their request/response shapes and error codes, slowing integrators. This issue documents them.
Requirements and context
docs/config.mdcovering each config route, its params, response shape, and error codes.Suggested execution
git checkout -b docs/config-01-apiTest and commit
npm run lint,npm test, andnpm run build.Example commit message
docs(config): document the API contractGuidelines
Community & contribution rewards