Add Spin-version-specific worlds to `src/spin_sdk/wit/spin.wit`

Open
#123 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python, wasm
Domain
build-system, developer-experience

Research direction

Start with src/spin_sdk/wit/spin.wit and inspect the existing worlds and version-related definitions. Check how the --world option to componentize-py is specified in the build directive of spin.toml. Done means version-specific worlds cover the supported older Spin versions while the latest supported version remains the default.

Written by the indexing model from the issue text.

Description

Currently, there's no obvious way to use the latest SDK to target older (e.g. pre-3.4) versions of Spin; the only option is to use an earlier SDK version. One easy way to address that would be to add version-specific worlds to spin.wit, e.g. one for Spin 3.2.x, one for Spin 3.3.x, etc. This will allow the user to specify which Spin version they wish to target using the --world option to componentize-py in the build directive of their spin.toml file. The default would remain the latest version of Spin supported by the SDK.

Dominant language
Python
Stars
48
Forks
15
Avg merge
2d 23h
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from spinframework/spin-python-sdk

All issues in spinframework/spin-python-sdk

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.