You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 5a4f169
Browse filesBrowse the repository at this point in the historyBrowse files
Address review on #4494: deprecate instead of reject
- parse_attributes checks Mapping rather than dict and emits
ZarrDeprecationWarning for out-of-contract input instead of raising;
dict(data) still runs so accepted values behave exactly as before
- parse_shapelike loses the reject_bool kwarg; bools now warn
(ZarrDeprecationWarning) wherever they parse, ahead of rejection once
the deprecation window elapses
- dimension_names string/bytes exclusion and storage_transformers
mapping exclusion unchanged
- tests updated: bools and non-mapping attributes are covered by
pytest.warns cases; repair fixtures reading stored true chunks keep
their assertions
Tighten array metadata field validation: ``shape`` rejects booleans, ``attributes`` requires a dict with string keys, ``dimension_names`` rejects a bare string, and ``storage_transformers`` rejects a mapping.
1
+
Tighten array metadata field validation: `dimension_names` rejects a bare string and `storage_transformers` rejects a mapping. `shape` fields that contain booleans and `attributes` fields that are not mappings with string keys still parse as before, but emit a `ZarrDeprecationWarning` ahead of rejection in a future release.
0 commit comments