Fix Zarr Segmentation Layer json parsing #6363
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When parsing the datasource-properties.json, wk previously failed to recognize zarr segmentation layers. They were instead parsed as ZarrDataLayers (discarding segmentation-specific fields like largestSegmentId). The
category
field was still "segmentation" (creating an invalid state, and leading the frontend to in turn correctly show the layer as a segmentation). The symptom was that you could not create an annotation with this layer as fallback segmentation.URL of deployed dev instance (used for testing):
Steps to test:
Issues: