Dominik J. Otto

Thank you for the clarification, that makes perfect sense! I find SpatialData has a fundamentally different structure that just contains AnnData objects: ``` SpatialData object, with associated Zarr store: /Users/macbook/embl/projects/basel/spatialdata-sandbox/mouse_liver/data.zarr...

Following up on the SpatialData discussion, I explored an alternative to `ObjectFormatter`: exporting building blocks so SpatialData can own its `_repr_html_` while reusing anndata's styling. **[settylab/anndata#3](https://github.com/settylab/anndata/pull/3)** exports building blocks (`get_css`,...

The CI failures appear unrelated to this PR. They're in dask distributed tests on `hatch-test.pre` which pulls pandas 3.0.0rc0. Pandas 3.0 defaults to `ArrowStringArray` for strings, but anndata's IO registry...

While experimenting with this PR, I noticed that anndata now has several extension mechanisms scattered across different locations (accessors in `ad.register_anndata_namespace`, HTML formatters in `anndata._repr`, I/O handlers in `anndata._io.specs._REGISTRY`). Following...

Following up on [settylab/anndata#3](https://github.com/settylab/anndata/pull/3) in addition to exporting building blocks for SpatialData integration, I've added a few more features: **New functionality:** - **Regex search**: Case-sensitive and regex toggles for filtering...