Add `processed-by` entry to the producer
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 32/100
Research direction
Read the linked wasm-metadata Producers API documentation and ProducersSection.md convention first. Then locate the producer implementation and relevant tests in the repository; done means the producer emits the expected processed-by entry and the behavior is verified by tests.
Written by the indexing model from the issue text.
Description
- Dominant language
- Rust
- Stars
- 1.1k
- Forks
- 64
- PR merge metrics
- No merged PRs in 30d
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.
More from bytecodealliance/wizer
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
bytecodealliance/wizer#130 ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
bytecodealliance/wizer#153 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
bytecodealliance/wizer#126 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
bytecodealliance/wizer#125 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
bytecodealliance/wizer#98 · 8 comments ·
All issues in bytecodealliance/wizer
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
gitbutlerapp/gitbutler#15998 · 1 comment ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100