Define policy for which header name constants to include

Open
#573 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust
Domain
networking

Research direction

Start by reviewing the existing standard header name constants in http::header and any project guidance on public API additions. Define and document a policy that weighs the benefits and maintenance costs of adding each name, with enough criteria for future contributors to apply it consistently.

Written by the indexing model from the issue text.

Description

A-headers B-rfc

We include many standard header names as constants in http::header. The exact criteria has not been defined, and it would be wise to do so. This stops it from being an unwritten rule in a few people's heads. The policy likely should consider the pros of adding any name versus the costs of adding a name.

Dominant language
Rust
Stars
1.4k
Forks
378
Avg merge
1d 21h
Merged PRs (30d)
5

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from hyperium/http

All issues in hyperium/http

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.