LukeMathWalker / LukeMathWalker/biscotti
Elaborate on non-design goal of parsing set-cookie
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Biscotti looks great and I love the direction you took way this crate from the 'cookie' crate.
I wonder however why parsing Set-Cookie headers is such a non goal? Feels like you already have everything in place for response headers, only the parsing is missing.
In case it is due to time constraints, I could offer to contribute this for you. Otherwise I might need to fork it for my own purposes if you don't mind as I do really need that support.
Either way, thanks for your blog and crate, it's a nice refreshing take on cookies.
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 Biscotti's existing response-header handling and the stated non-goal around parsing Set-Cookie. Clarify the intended parsing scope and validation behavior before implementation; done means the agreed Set-Cookie response headers parse correctly without changing existing cookie-management behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100