nodejs / nodejs/orchestrion-js
User `serde::Deserialize` rather than a specific serialization format
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 24
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
It should be possible to derive serde::Deserialize for InstrumentationConfig and that way consumers of this library will be able to use whichever serialization format they prefer.
It will also mean that if this library is exposed via wasm-bindgen, it will automatically support passing these as JavaScript objects and it will output TypeScript definitions to match.
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
Locate InstrumentationConfig and inspect its existing serialization support. Then trace how the configuration is exposed through wasm-bindgen and how TypeScript definitions are generated; the work is done when consumers can derive serde::Deserialize and use their preferred format, including JavaScript object input with matching definitions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, rust, typescript, wasm
- Domain
- api, web-dev
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100