serde-rs / serde-rs/serde-rs.github.io
Implementing custom Deserialize
Open
Nobody has claimed this yet.
content
- Dominant language
- HTML
- Stars
- 23
- Forks
- 109
- PR merge metrics
- No merged PRs in 30d
Description
- for primitives
- for a seq
- for a map
- for different types of structs
- normal struct
- tuple struct
- newtype struct
- unit struct
- for an enum
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
Start by locating the custom Deserialize documentation or examples in the repository and reviewing how the completed primitive, map, normal-struct, and newtype-struct cases are organized. Determine the expected treatment for sequences, tuple structs, unit structs, and enums, then consider the work complete when each unchecked case is documented consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100