WebAssembly / WebAssembly/WASI
[v0.3] Specify what is meant by "not syntactically valid"
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 5.8k
- Forks
- 333
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 3
Description
A number of the interfaces that turn strings into typed values, e.g. fields.from-list, fields.set, request.set-method, and so on can return a failure result if the value being set is not "syntactically valid". However, the specification does not define what this means. Suggest adding wording such as, "Syntactically valid methods are defined in RFC 9110§9.1".
Also, is it an error if a WASI HTTP implementation does not impose syntactic constraints on header/method/etc values?
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
Review the interfaces named in the issue, including fields.from-list, fields.set, and request.set-method, alongside RFC 9110 §9.1. Clarify the meaning of “syntactically valid,” decide whether implementations may omit such constraints, and update the specification with the agreed wording.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- api, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100