Stringly-typed HeaderValue?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.4k
- Forks
- 378
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 5
Description
Hi!
Hyper made the design decision to having properly-typed header values, and cites good reasons for it: https://docs.rs/hyper/0.11.6/hyper/header/index.html
I was wondering if it was an explicit design decision in http to not do this, and if so, could someone go into the reasons?
I'm genuinely curious if this could be a nice addition to http, especially since it seems hyper is planning to move to http-provided types in a future version, or whether there are strong reasons against it.
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 reading the issue and the linked Hyper header documentation to understand the contrast with http's design. Determine whether typed header values are intended as a concrete addition or require a broader design decision; the issue is complete only when that direction and its scope are resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100