ConfigHubPub / ConfigHubPub/ConfigHubPlatform
Error response codes should give a reason for the error state.
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 80
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
Can error responses have an explanation of what went wrong. Like say 'USA;NJ' is a valid context, but 'NJ' is supplied, can we get something like 'Improper context: two levels required, one given.' or the like? It would make debugging systems that use confighub a lot easier.
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
The issue names no files, tests, or entry points. Start by locating the error-response handling for invalid context values and inspect existing API error tests. Done means invalid contexts return a clear explanation, such as the expected and supplied context levels, with coverage for the reported USA;NJ versus NJ case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100