This reworks the question catalog JSON structure as well as the internal models and some working principles.
The reason behind this is to simplify the JSON structure where possible while increasing its flexibility and power so future inputs like MultipleChoice can be implemented.
The previous uniform input structure is split in a
uniform part (the constructor) - so final OSM tag creation is still identical/centralized
heterogeneous part: (the input) - so input properties can be defined independently from other inputs
TODOs:
[ ] Requires testing (especially upload)
[x] The JSON testing currently fails due to a bug in the JSON validation tool. Easiest solution would be to rename the constructor parameter. > Resolved by using a different json validator
This reworks the question catalog JSON structure as well as the internal models and some working principles. The reason behind this is to simplify the JSON structure where possible while increasing its flexibility and power so future inputs like MultipleChoice can be implemented.
The previous uniform input structure is split in a
TODOs:
constructorparameter. > Resolved by using a different json validator