bioio-devs
Feature Request/ manage writers differently
Description
We added sophisticated functionality for reader plugins so that we could manage dependencies separately and it was easy for external users to contribute.
Why not do the same for writers?
some of the writer dependencies cause conflicts that don't allow updated readers to be used in bioio, (ome-zarr) This seems like the same issue that we had with readers so why not make the writers plugins too?
This is a pretty reasonable idea, but here's a couple thoughts: Writers aren't special in the sense that they don't conform to a particular API. (There's no base writer class). So there's nothing stopping anyone from making their own writer in a separate repo. The goal of bioio is to support writing only to open file formats that can have high adoption. So tiff and zarr are the best choices right now. Maybe new zarrV3 writer development needs to happen in a separate repo? bioio-devs/zarrv3-writer ?
@toloudis Some additional context here. bioio is currently restricted to zarr <3.0.0 due to the writers, additionally bioio-ome-tiff and bioio-tiff-glob are also restricted to zarr <3.0.0. This means we cannot have a reader that plugin that supports zarr v3 while the writers still dictate the dependencies. While having a separate repo for v3 writer allows isolation of writer dependencies it doesn't fix the blocked new reader. We would have to move the other writers as well into seperate repos.