wasmCloud / wasmCloud/wasmcloud.com
Doc go/httpserver: make uncomfortable warning obsolete
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 23
- Forks
- 70
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 17
Description
on https://wasmcloud.com/docs/examples/go/component/http-server/
there is written:
[!WARNING] Due to incompatibilities introduced in wasm-tools v1.226.0, a version of wasm-tools <= 1.225.0 is required for running this example.
would be good to give more details on this and
even better make this warning obsolete
-> especially for beginners / to build trust that wasmcloud is a longterm project and there is no risk to fall into compatibility traps in the field of tooling
- is/was this a permanent issue or will it be fixed in upcoming versions? see https://github.com/bytecodealliance/wasm-tools/releases
- how could one work with an uptodate versions of wasmtools?
- what’s the alternative?
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 with the Go HTTP server example at wasmcloud.com/docs/examples/go/component/http-server/ and compare its wasm-tools warning with the wasm-tools v1.226.0 and later release notes. Determine whether the incompatibility is resolved and update or remove the warning so the example works with a current wasm-tools version, documenting an alternative if it does not.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100