Separated status codes for different levels
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.4k
- Forks
- 378
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 5
Description
This is a wished feature, not a bug.
It would be nice to have status codes separated by level. For example status::Success::OK or status::Client::NotFound.
The "everything in one place" is fine for normal codes, but as you read some code and you stumble upon something like "Not exteded" or "Upgrade required" or "Precondition failed" it's really hard to remember if they are 4xx (Client errors) or 5xx (Server errors).
I tried to take a look at the code to prepare a PR, but they are macro-generated and that's beyond me, for now...
Contributor guide
No contributing guide indexed for this repository
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 by locating the macro-generated HTTP status-code definitions and reading how the existing single-level names are organized. Determine how success, client-error, and server-error groupings should map to the proposed names, then add coverage showing representative codes such as OK and NotFound resolve through the new organization.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100