But actually, this is very similar to the input specs of napari workflows, just with slightly different limits: we can only use "image" as type and only have up to 2 images, where order matters
=> let's see whether we can use a variant of what we build for napari workflows input & output arguments here as well!
The review of input arguments & the discussions on pydantic models for napari workflows (e.g. https://github.com/fractal-analytics-platform/fractal-tasks-core/issues/404) and channel (https://github.com/fractal-analytics-platform/fractal-tasks-core/issues/386#issuecomment-1582511309) made me think:
We should also refactor the way we handle the channel inputs in Cellpose.
Currently, we do:
But actually, this is very similar to the input specs of napari workflows, just with slightly different limits: we can only use "image" as type and only have up to 2 images, where order matters
=> let's see whether we can use a variant of what we build for napari workflows input & output arguments here as well!