Skip to content

docs(zarr-metadata): document every public object - #4590

Merged
d-v-b merged 3 commits into
zarr-developers:mainfrom
d-v-b:claude/zarr-metadata-api-docs-13ef0c
Nov 2, 2026
Merged

d-v-b merged 3 commits into
zarr-developers:mainfrom
d-v-b:claude/zarr-metadata-api-docs-13ef0c

Conversation

@d-v-b

@d-v-b d-v-b commented Nov 2, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Adds docstrings for all public objects and gets them wired up to the API docs.

Author attestation

  • I am a human, these are my changes, and I have reviewed and understood every change and can explain why each is correct.

TODO

  • Add unit tests and/or doctests in docstrings
  • Add docstrings and API docs for any new/modified user-facing classes and functions
  • New/modified features documented in docs/user-guide/*.md
  • Changes documented as a new file in changes/
  • GitHub Actions have all passed
  • Test coverage is 100% (Codecov passes)

@github-actions github-actions Bot added needs release notes Automatically applied to PRs which haven't added release notes zarr-metadata Specific to the zarr-metadata sub-package labels Nov 2, 2026
@read-the-docs-community

read-the-docs-community Bot commented Nov 2, 2026 •

Copy link
Copy Markdown

d-v-b added 2 commits November 2, 2026 08:54
Add a docstring to every public object, and a test that fails on an
undocumented public object, a public module with no reference page, or a
v2 on-disk field docstring that drifts from its in-memory counterpart.

Assisted-by: ClaudeCode:claude-opus-5-5
…t pass

Cover the vlen codecs, the fixed-width string data types and the strategy
records, and render zarr_metadata.testing, which has no __all__.

Assisted-by: ClaudeCode:claude-opus-5-5
@d-v-b
d-v-b force-pushed the claude/zarr-metadata-api-docs-13ef0c branch from c30fcee to 1d602b2 Compare November 2, 2026 08:00
Drop the struct sentence, since main already renders that page.

Assisted-by: ClaudeCode:claude-opus-5-5
@d-v-b d-v-b changed the title docs(zarr-metadata): document every public object and give struct its reference page docs(zarr-metadata): document every public object Nov 2, 2026
@d-v-b
d-v-b marked this pull request as ready for review November 2, 2026 08:09
@codecov

codecov Bot commented Nov 2, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.84%. Comparing base (51a6b77) to head (74671ac).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #4590   +/-   ##
=======================================
  Coverage   94.84%   94.84%           
=======================================
  Files          96       96           
  Lines       13998    13998           
=======================================
  Hits        13276    13276           
  Misses        722      722           
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@d-v-b

d-v-b commented Nov 2, 2026

Copy link
Copy Markdown
Contributor Author

this is internal to zarr-metadata so i am self-merging

@d-v-b
d-v-b merged commit 9e44021 into zarr-developers:main Nov 2, 2026
45 checks passed
d-v-b added a commit to d-v-b/zarr-python that referenced this pull request Nov 2, 2026
Resolve the rename against the four zarr-metadata changes main gained:
the ZARR_PYTHON_CONTEXT scope and the *_CONTEXT constant names (zarr-developers#4583),
the v3 submodule re-exports (zarr-developers#4588), the Hypothesis strategies (zarr-developers#4575)
and the docstrings for every public object (zarr-developers#4590).

Every conflict was the rename on one side and new upstream text on the
other, so each is resolved as the upstream text with the rename applied.
The rename is carried into upstream's additions: the new docstrings say
"field" for a JSON key and "declaration" for an extension-point value,
and the strategies module's `fields` strategy is `declarations`, with
`FieldForm` now `DeclarationForm` in its tests. The zarr-developers#4575 changelog
fragment uses the new name, since neither name has been released.

Assisted-by: ClaudeCode:claude-fable-5-1
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
d-v-b added a commit to d-v-b/zarr-python that referenced this pull request Nov 2, 2026
This branch was squash-merged upstream as zarr-developers#4575 (4a72dd4), whose tree
matches this branch's head. Each conflict is main's later change to the
same files (zarr-developers#4583, zarr-developers#4588, zarr-developers#4590, zarr-developers#4592), so every file takes main's
side, and the branch now matches main.

Assisted-by: ClaudeCode:claude-opus-5-5
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs release notes Automatically applied to PRs which haven't added release notes zarr-metadata Specific to the zarr-metadata sub-package

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant