Skip to content

Commit 80d6679

Browse files
committed
public API for getting the zarr v3 name
1 parent ba2ad18 commit 80d6679

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

changes/2874.feature.rst

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,8 @@ fields on the ``ArrayV2Metadata`` and ``ArrayV3Metadata`` classes. Previously, `
1313
was a NumPy ``dtype`` object, and ``ArrayV3Metadata.data_type`` was an internally-defined ``enum``.
1414
After this change, both ``ArrayV2Metadata.dtype`` and ``ArrayV3Metadata.data_type`` are instances of
1515
``ZDType``. A NumPy data type can be generated from a ``ZDType`` via the ``ZDType.to_native_dtype()``
16-
method. The internally-defined Zarr V3 ``enum`` class is gone entirely, but the ``ZDType._zarr_v3_name``
17-
attribute contains the string value previously associated with that ``enum``.
16+
method. The internally-defined Zarr V3 ``enum`` class is gone entirely, but the ``ZDType.to_json(zarr_format=3)``
17+
method can be used to generate a dictionary that has a ``name`` field that contains the string value
18+
previously associated with that ``enum``.
1819

1920
For more on this new feature, see the `documentation </user-guide/data_types.html>`_

0 commit comments

Comments
 (0)