(fix): object dtypes + v2 tests

zarrs · ilan-gold · Feb 11, 2025 · Jan 3, 2025 · Jan 3, 2025 · Jan 28, 2025
commit a51e810618de5e794787d21aa4cf5cfda19941b2
diff --git a/README.md b/README.md
@@ -21,7 +21,7 @@ You can then use your `zarr` as normal (with some caveats)!
 
 ## API
 
-We export a `ZarrsCodecPipeline` class so that `zarr-python` can use the class but it is not meant to be instantiated and we do not guarantee the stability of its API beyond what is required so that `zarr-python` can use it.  Therefore, it is not documented here.  We also export two errors, `DiscontiguousArrayError` and `CollapsedDimensionError` that can be thrown in the process of converting to indexers that `zarrs` can understand (see below for more details).
+We export a `ZarrsCodecPipeline` class so that `zarr-python` can use the class but it is not meant to be instantiated and we do not guarantee the stability of its API beyond what is required so that `zarr-python` can use it.  Therefore, it is not documented here.
 
 At the moment, we only support a subset of the `zarr-python` stores:
 

diff --git a/docs/api.md b/docs/api.md
diff --git a/docs/index.md b/docs/index.md
@@ -5,6 +5,5 @@
 :hidden: true
 :maxdepth: 1
 
-api
 contributing
 ```
diff --git a/pyproject.toml b/pyproject.toml
@@ -122,3 +122,6 @@ ignore = [
 "**/*.pyi" = ["ICN001"]
 [tool.ruff.lint.isort]
 known-first-party = ["zarrs"]
+
+[tool.hatch.metadata]
+allow-direct-references = true
-Original file line number
+Diff line change
@@ Expand Up / @@ -21,7 +21,7 @@ You can then use your `zarr` as normal (with some caveats)! @@
     ## API
-    We export a `ZarrsCodecPipeline` class so that `zarr-python` can use the class but it is not meant to be instantiated and we do not guarantee the stability of its API beyond what is required so that `zarr-python` can use it.  Therefore, it is not documented here.  We also export two errors, `DiscontiguousArrayError` and `CollapsedDimensionError` that can be thrown in the process of converting to indexers that `zarrs` can understand (see below for more details).
+    We export a `ZarrsCodecPipeline` class so that `zarr-python` can use the class but it is not meant to be instantiated and we do not guarantee the stability of its API beyond what is required so that `zarr-python` can use it.  Therefore, it is not documented here.
     At the moment, we only support a subset of the `zarr-python` stores:
@@ Expand Down @@