Is your feature request related to a problem? Please describe.
Currently, the GUI generation in cuiman is quite simple and mainly relies on standard properties defined in OGC API Processes descriptions and the inputs'/outputs' JSON Schemas, if any.
Describe the solution you'd like
A clean OGC API Processes UI client pipeline would look like this
Process description
↓
Parameter model
↓
JSON Schema merge
↓
UI metadata merge
↓
Field model
↓
Panels
which cleanly keeps architectural layers separated:
- Semantics, Validation <--> JSON Schema
- Metadata <--> OGC input/output descriptions
- Presentation <--> Extensions fields `"x-ui"` / `"ui"` in the above
Checklist:
Related
Is your feature request related to a problem? Please describe.
Currently, the GUI generation in
cuimanis quite simple and mainly relies on standard properties defined in OGC API Processes descriptions and the inputs'/outputs' JSON Schemas, if any.array(Add GUI for process inputs of type "array" #37) andobject(Add GUI for process inputs of type "object" #38)oneOf,anyOf,allOf,discriminator,$ref`Describe the solution you'd like
A clean OGC API Processes UI client pipeline would look like this
which cleanly keeps architectural layers separated:
Checklist:
ClientConfig.is_advanced_input()should then be replaced by the new solution.cuiman.Related