Schedules for different conditions only differ in minor but important details, for example the set of used items is different but the general structure stays the same.
This, combined with #28 and the idea of item templates, can be implemented by adding a prepocessing step. We define a JSON-specification, that can be understood and displayed by the app. Then, we compile our higher-level JSON-file to the lower level specification. Sounds unnecesarily complex to me when I write it like this 🤔, the idea is actually very simple.
Schedules for different conditions only differ in minor but important details, for example the set of used items is different but the general structure stays the same.
This, combined with #28 and the idea of item templates, can be implemented by adding a prepocessing step. We define a JSON-specification, that can be understood and displayed by the app. Then, we compile our higher-level JSON-file to the lower level specification. Sounds unnecesarily complex to me when I write it like this 🤔, the idea is actually very simple.