Sub-types naming conflicts
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
Research direction
Start with the conflicting JSON Schema example in the issue and trace how names are assigned to the referenced subtype and enum. Define a naming approach that prevents the generated Enum and Struct from sharing a name, then verify it against this schema and related naming cases.
Written by the indexing model from the issue text.
Description
The following definitions will result in both an Enum and a Struct named AaBb:
"Aa": {
"properties": {
"bb": {
"anyOf": [
{
"$ref": "#/definitions/AaBb"
},
{
"type": "string"
}
]
}
}
},
"AaBb": {
"enum": [
"A",
"B"
],
"type": "string"
}
We might need an alternative way to name types in types. Maybe AaSubBb or AaBbProp, idk.
- Dominant language
- Rust
- Stars
- 898
- Forks
- 114
- Avg merge
- 4h 18m
- Merged PRs (30d)
- 14
Contributor guide
No contributing guide indexed for this repository
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 oxidecomputer/typify
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
oxidecomputer/typify#1077 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
oxidecomputer/typify#1075 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 50/100
oxidecomputer/typify#1060 ·
-
Difficulty 5/5 Over a week Newbie friendliness 48/100
oxidecomputer/typify#1059 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
oxidecomputer/typify#1022 · 1 comment ·
All issues in oxidecomputer/typify
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
BurntSushi/jiff#653 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ZcashFoundation/zeeder#106 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
oxidize-rb/rb-sys#807 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
todo:ticket
Difficulty 2/5 1-2 days Newbie friendliness 74/100