spinframework / spinframework/spin
Investigate WIT interface version upgrades
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 6.5k
- Forks
- 310
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 24
Description
How do we handle backward-compatible (i.e. adding a function) WIT interface upgrades?
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.
Research direction
No files or tests are named. Start by locating Spin's WIT interface definitions and version-handling entry points, then review existing upgrade behavior. Done means a decided strategy for backward-compatible function additions and a clear implementation and test scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, wasm
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100