Aswin - Does the plugin Config of the signalK s...
Does the plugin Config of the signalK server support dependencies in plugin.schema? I want to optionally hide certain settings. Or is there another way?
8 Replies
you can make the schema dynamic (make it a function that returns the schema instead of a static object)
but that only helps if you schema depends on something the server already knows, like what paths are available
if want to enable/add something in the form based on another field you'll need to look into UISchema, i have not used it but it has some capabilities to this end
So, where can I find the syntax for UISchema? It seems it is notto be the syntax provided by JSON forms.
GitHub
react-jsonschema-form-bs4/docs/form-customization.md at master · pe...
A React component for building Web forms from JSON Schema. - peterkelly/react-jsonschema-form-bs4
Thanks for the link. I found what I was looking for in dependencies. But dependencies do not seem to work in SignalK server.
I give up.
@Scott Bender i've never looked into dependencies in anger, have you?
@naugehyde i suppose updating to mainline, up to date rsjf would solve this?
@Aswin there are two "espace hatches" here
1) write a custom React configuration UI for your plugin, embedded in server's plugin configuration - this is what calibration plugin does
2) extend your webapp to also cover plugin configuration, then you are free to do what you want, it just won't be part of the plugin config ui
No, I never looked into it
I tried this example as a plugin.schema: https://github.com/peterkelly/react-jsonschema-form-bs4/blob/master/docs/dependencies.md#dynamic
@Teppo Kurki Thanks for the hints. A custom React UI is way over my head but I will consider option 2.
@Teppo Kurki @Aswin I haven't tested schema dependencies except for oneOfs which work in current mainline (React 16) and are active in bt-sensors-plugin-sk.
I used https://rjsf-team.github.io/react-jsonschema-form/ as a testbed for future (React 18) capabilities.
One key improvement in React 18 was that oneOf enum default values appeared in the UI (but not in current mainline).