Backport `Either` to 0.4
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 173
- Forks
- 69
- Avg merge
- 6d 15h
- Merged PRs (30d)
- 4
Description
With the latest changes, moving types to http-body-util, I think this will require a breaking change release for a lot of crates.
I have a use-case where I require the recently introduced Either type from #64, currently I basically just copied the file. Would it be possible to backport #64 to a 0.4 branch and make a release?
Happy to make the PR of course.
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 reviewing issue #64 and the repository's current branch and release history to understand the introduced Either type and the 0.4 baseline. Backport the requested change to a 0.4 branch and verify that the resulting release makes Either available to crates still using that line.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend-api-design, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100