rename ArrayV3Metadata and ArrayV2Metadata #3843

Activity

1. maxrjones commented on Mar 30, 2026

   

   maxrjones

   on Mar 30, 2026

   Member

   More actions

   why?
2. d-v-b commented on Mar 30, 2026

   

   d-v-b

   on Mar 30, 2026

   ContributorAuthor

   More actions

   logically, it's array metadata first, and then the version qualifies it. and for consistency: we are already using the X_V2 / X_V3 pattern elsewhere in the codebase to distinguish v2 and v3 metadata representations of comparable things.
3. maxrjones commented on Apr 7, 2026

   

   maxrjones

   on Apr 7, 2026

   Member

   More actions

   I prefer ArrayMetadataV2 + ArrayMetadataV3; I find the _ is a mixing of naming styles.

   https://github.com/zarr-developers/zarr-python/actions/runs/24095500618/job/70292885214?pr=3882 shows other inconsistencies.
4. d-v-b commented on Apr 7, 2026

   

   d-v-b

   on Apr 7, 2026

   ContributorAuthor

   More actions

   i think we are allowed to mix styles when it favors readability: compare ArrayMetadataJSON_V3 and ArrayMetadataJSONV3
5. maxrjones commented on Apr 7, 2026

   

   maxrjones

   on Apr 7, 2026

   Member

   More actions

   i think we are allowed to mix styles when it favors readability: compare ArrayMetadataJSON_V3 and ArrayMetadataJSONV3

   Yeah, underscores between distinct sets of capital letters help readability. For the non-JSON class, I prefer ArrayMetadataV3.

   We might want to jot down these preferred code styles in the contributors guide or CLAUDE.md

   👍React with 👍1Reacted by Davis Bennett
6. d-v-b

   added

   design discussionDiscussion about the design of the libraryDiscussion about the design of the library

   on Apr 23, 2026