spinframework / spinframework/spin-rust-sdk
P3 Response bodies for the rest of us
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 35
- Forks
- 23
- Avg merge
- 37m
- Merged PRs (30d)
- 1
Description
In Spin 3.x, you could put a Vec<u8> in a Response body. Now, as far as I can tell, you have to do a FullBody::new(Bytes::from(...)) before it will let you.
This is non-obvious and is 28 extra characters, do you think I am made of keyboards.
(I know the young people are all about streaming bodies but sometimes it's useful, particularly for docs purposes, to just dump a blob in there, declare victory, and go home.)
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 tracing the Response body API and the existing FullBody::new(Bytes::from(...)) path described in the issue. Done means a Vec can be used directly as a response body, with the behavior covered by the relevant tests or documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100