Allow per-field renaming of elements/attributes
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
Start by reviewing the naming conventions discussed in issue #5 and the current serialization behavior for fields. Define how an explicit per-field name should override conventions for both element and attribute serialization, then add coverage confirming both forms use the requested names.
Written by the indexing model from the issue text.
Description
Even with a set of standard naming conventions (https://github.com/thunderbird/xml-struct-rs/issues/5), there will be times that fields don't match an existing convention or violate the conventions used by an API. Allow consumers to explicitly set the name used for a field when serializing as an element or attribute.
- Dominant language
- Rust
- Stars
- 18
- Forks
- 2
- 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 thunderbird/xml-struct-rs
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
thunderbird/xml-struct-rs#9 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
All issues in thunderbird/xml-struct-rs
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