Closed tcompa closed 3 months ago
For the moment this was fixed in fractal-server 1.3.6, where we stopped pre-populating the defaults from the backend. Refs
Right now, the behavior in the webclient when a task is added for the first time is the same as in the sandbox.
We can still review the web-client behavior in the future, based on more specific example use cases or edge cases.
This stems from the report in https://github.com/fractal-analytics-platform/fractal-web/issues/537, also reviewed in https://github.com/fractal-analytics-platform/fractal-web/issues/538.
It's clear that it should be somehow possible to display default values for nested arguments even when some JSON data are set, see e.g. this https://rjsf-team.github.io/react-jsonschema-form/ example:
One likely complexity is that we generally strip null or empty values (ref https://github.com/fractal-analytics-platform/fractal-web/issues/209), and we will likely need to review this approach as well when we start handling nested arguments.