Describe the bug
The documentation don't mark opposites as optional:
|
- `opposites` (object) — Maps opposing directions to target names: |
But it can be optional. For example, in this JSON object:
|
{ |
|
"has_left_and_right": false, |
|
"label": "head-triangular", |
|
"name": "head-triangular", |
|
"targets": [ |
|
"head-triangular" |
|
] |
|
}, |
Same issue with unsorted. Looks like it's always either always empty or missing.
Describe the bug
The documentation don't mark
oppositesas optional:mpfb2/docs/fileformats/target_metadata.md
Line 34 in 13530a3
But it can be optional. For example, in this JSON object:
mpfb2/src/mpfb/data/targets/target.json
Lines 1844 to 1851 in 13530a3
Same issue with
unsorted. Looks like it's always either always empty or missing.