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 e6658d2
Browse filesBrowse the repository at this point in the historyBrowse files
* fix(metadata): read Zarr V3.1 short-hand extension names
Zarr V3.1 lets an extension definition that needs no configuration be
written as a bare name: `"crc32c"` is equivalent to `{"name": "crc32c"}`.
Reading such a document raised `TypeError: Expected dict, got <class 'str'>`.
`expand_short_hand_name` expands a bare name at the parser of each array
extension point that took only the object form: codecs (including codecs
nested in a sharding codec), chunk_grid, chunk_key_encoding and
storage_transformers. data_type already accepted a bare name. A bare name
for an extension that requires a configuration (`"regular"`, `"gzip"`) is
still rejected, with the missing-configuration error.
Metadata is still written in the object form, which Zarr V3.0 readers
require.
Refs zarr-developers#3188
Assisted-by: ClaudeCode:claude-opus-5-5
* docs(changes): add changelog fragment for short-hand extension names
Assisted-by: ClaudeCode:claude-opus-5-5
* docs(changes): renumber short-hand names fragment to the upstream PR
Assisted-by: ClaudeCode:claude-opus-5-5
* fix(chunk-key-encoding): accept a bare encoding name in ChunkKeyEncodingLike
parse_chunk_key_encoding now expands short-hand names, so array creation
functions accept `chunk_key_encoding="v2"`. Declare `str` in the type,
drop the type ignore it made unnecessary, and test the chunk keys each
short-hand name produces. Correct the fragment: a short-hand storage
transformer was kept as a bare string on main, not rejected.
Assisted-by: ClaudeCode:claude-opus-5-5
Co-Authored-By: Claude Opus 5.5 <[email protected]>
---------
Co-authored-by: Claude Opus 5.5 <[email protected]>
0 commit comments