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 0401a7f
Browse filesBrowse the repository at this point in the historyBrowse files
feat(zarr-metadata)!: the model reads each extension point through its definition (#4436)
* feat(zarr-metadata): the model reads each extension point through its definition
`validate_array_metadata_v3` judged an array document's structure and
left every configuration unread: a gzip `level` of 99, or a key a codec
does not declare, passed. It now reads each extension point -- the data
type, the chunk grid, the chunk key encoding, each codec and each
storage transformer -- with `resolve`, in a scope,
`CORE_AND_EXTENSIONS` unless a `context` is passed: the envelope judged,
`must_understand: false` refused at each, and the configuration read
against the definition that claims its name. A name nothing in scope
claims is left unjudged, which keeps the format open.
So do the `is_*` and `parse_*` beside it and the v3 group validators,
with each array an inline `consolidated_metadata` holds, and the v3
model classes' `from_json` and `from_key_value` take the same
`context`, so a reader that substitutes its own reading of a codec
builds the model from a document its scope accepts. The pydantic types
read in `CORE_AND_EXTENSIONS`, since a field type holds no scope; the
docstrings and the definition guide say so, and say that no rule here
reads one field against another.
Assisted-by: ClaudeCode:claude-opus-5-5
Co-Authored-By: Claude Opus 5.5 <[email protected]>
* docs(zarr-metadata): the validation boundary says what the validators read
The README and the docs index said the model validators do not
interpret extension names or configurations. In a v3 document they now
read each extension point through its definition in a scope, refuse
what the definition refuses and report an undeclared key as
`unknown_key`; they leave names nothing claims unjudged, and do not
judge fields against each other.
Assisted-by: ClaudeCode:claude-opus-5-5
Co-Authored-By: Claude Opus 5.5 <[email protected]>
* docs(zarr-metadata): the fragment for the model reading extension points through definitions
Assisted-by: ClaudeCode:claude-opus-5-5
Co-Authored-By: Claude Opus 5.5 <[email protected]>
* feat(zarr-metadata): a v3 model writes in the scope it reads in
`to_key_value` validates what it writes with its reader's `parse_*`,
and at this layer the reader reads each extension point in a scope. The
v3 array and group `to_key_value` take the same `context` as `from_json`
and `from_key_value`, so a model read with a reader's own definitions is
written with them, and the default scope still refuses to write what it
would refuse to read.
Assisted-by: ClaudeCode:claude-opus-5-5
* docs(zarr-metadata): the fragment takes this PR's number and says what breaks
Assisted-by: ClaudeCode:claude-opus-5-5
* docs(zarr-metadata): the must_understand fragment names the PR that merged it
The change merged with #4434, which carried #4433's commits; towncrier links a fragment to the pull request its name gives.
Assisted-by: ClaudeCode:claude-opus-5-5
---------
Co-authored-by: Claude Opus 5.5 <[email protected]>
Copy file name to clipboardExpand all lines: packages/zarr-metadata/README.md
+12-6Lines changed: 12 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ Two layers and an optional integration:
14
14
specifications, plus types for [`zarr-extensions`](https://github.com/zarr-developers/zarr-extensions/)
15
15
and a few widely-used-but-unspecified entities (e.g. consolidated metadata).
0 commit comments