Publicly reexport the http crate
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 65/100
Research direction
Locate Hyper's pub use http; declaration and inspect its current documentation attribute. Remove the #[doc(hidden)] marker, then run the relevant Hyper test or documentation checks to confirm the http crate is publicly visible and its items remain accessible.
Written by the indexing model from the issue text.
Description
The http crate is already a public dependency of Hyper, and some items from it are already exported from Hyper. Let's remove the #[doc(hidden)] on pub use http;.
Projects out there sometimes need to use http::uri::Authority and other http items and that means depending on both http and hyper, which can be a papercut when either requires a breaking bump.
- Dominant language
- Rust
- Stars
- 16.3k
- Forks
- 1.8k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 14
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.
More from hyperium/hyper
-
C-feature
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
C-bug S-waiting-on-author
-
A-http2 C-bug
-
C-bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
A-client C-bug E-pr-welcome K-hyper-util
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
bug team:backend track:services-maintenance
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
cowprotocol/services#4950 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
gitbutlerapp/gitbutler#15998 · 1 comment ·