Skip to content

#250 child: Define Atlas layout-versioning and compatibility rules #264

Description

@Joncallim

Parent: #250. Determinism/maintenance review finding.

Deterministic output is only meaningful if layout/projection rule changes are explicit. Define version ownership and compatibility for Atlas projection/layout/visual grammar.

Requirements: named projection/layout versions or equivalent constants; fixture golden output tied to version; intentional rule changes require explicit golden migration and changelog/record; no accidental coordinate churn from dependency upgrades; third-party layout dependency versions pinned if selected; persisted/shareable state stores semantic subject/lens identity, not coordinates; old browser state degrades safely after version change.

Do not expose internal layout version as a public API compatibility promise unless separately justified. It is primarily a regression/change-control authority.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions