feat(spec): sync design-data-spec, SDK validators, registry, and tooling from beta#837
Merged
Conversation
…yzer from beta to main Brings the most up-to-date spec, schemas, conformance fixtures, SDK validators, registry vocabulary, and supporting tooling onto main, without touching packages/tokens/. Includes Proposal 010 (composite tokens), Proposal 012 (string-name escape hatch), proposals 001–010 + 012 documents, registry vocabulary expansion (anatomy-terms, sizes, variants), SPEC-014/015/016/017 rules and fixtures, scaleIndex field, and the token-mapping-analyzer tooling.
Rename camelCase project IDs to hyphenated equivalents: componentSchemas → component-schemas designDataSpec → design-data-spec csvGenerator → token-csv-generator componentDiff → component-diff-generator spectrumDiffCore → spectrum-diff-core diff → token-diff-generator Also update the dependent reference in markdown-generator/moon.yml and the command example in design-data-spec/README.md.
🦋 Changeset detectedLatest commit: 25bcf64 The changes in this PR will be included in the next version bump. This PR includes changesets to release 3 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Member
Author
Run report for 25bcf64eTotal time: 2m 29s | Comparison time: 7m 28s | Estimated savings: 4m 58s (66.7% faster)
Expanded report
Touched files |
When syncing spec content from beta, the RFC reconciliation work landed in main via #824 was accidentally regressed because beta forked before that commit. Restore the non-lastModified portions: - taxonomy.md: 'Structure vs. component — when does the line move?' section with the worked card example and Nate Baldwin attribution, plus the RFC #806 reference in the categories note. - manifest.md: query-language deferral clarification pointing at query.md as the normative reference. The lastModified-related portions of #824 (token-format.md lifecycle table, evolution.md mapping) are intentionally not restored, since the SPEC-014 ID is now occupied by composite-inline-alias-exists.
Closes the 010→012 numbering gap by renumbering the string-name escape hatch (originally landed on beta as Proposal 012) to 011. This PR is the proposal's first appearance on main, so the rename does not affect any published references on main. - Rename docs/proposals/012-string-name-escape-hatch.md -> 011-... - Rename .changeset/proposal-012-... -> proposal-011-... - Update file titles and changeset body to 'Proposal 011' - Update example UUID in spec/token-format.md from 0012 to 0011 to match the proposal-number convention used in the example.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Brings the most up-to-date design-data-spec content from
origin/betaand PR #814 ontomainin a single unified PR — without touchingpackages/tokens/.Changes grouped by area:
packages/design-data-spec/$valueTypefield, value-type schemas (typography,drop-shadow,typography-scale), rules SPEC-014/015/016, conformance fixturesnameallowed as tech-debt escape, rule SPEC-017, conformance fixturesscaleIndexfield declarationtoken-format.md,taxonomy.md,evolution.md,manifest.mdpackages/design-system-registry/anatomy-terms,sizes, andvariantsto close gaps surfaced by token-to-spec gap analysissdk/core/spec017.rs) — string-name tech-debt rulelegacy.rs/migrate.rsregistry_data.rslib.rscleanup,Cargo.tomldep cleanupdocs/proposals/tools/token-mapping-analyzer/.gitignore.moon/workspace.yml.changeset/@adobe/design-data-specand@adobe/design-system-registryonly — no@adobe/spectrum-tokensentriesRelated Issue
Related to #814 (token-to-spec gap analysis) and the beta release branch work in #817, #819, #820.
Motivation and Context
The
betabranch and PR #814 both advanced the spec significantly but on separate tracks. This PR merges that work ontomainso the normative spec, SDK validators, and registry vocabulary are available without waiting for a full tokens release.Key constraint:
packages/tokens/is intentionally unchanged — the typography-scale and token-rename work from #814/#819 will land in a follow-up PR.How Has This Been Tested?
git diff main..HEAD -- packages/tokens/— empty (hard guard passes)moon run sdk:test— 164 tests pass (incl. SPEC-017 string-name validator)moon run design-data-spec:check— layout guard passesmoon run design-system-registry:test— 65 tests passmoon run component-schemas:test— 27 tests pass (no regression)moon run tokens:test— 20 tests pass (no regression)moon run sdk:codegen-check— registry_data.rs and manifest.schema.json up to datepnpm avaintools/token-mapping-analyzer— 10 tests pass### Value-type declarationand### String-name escape hatchsections present inspec/token-format.md.changeset/files list only@adobe/design-data-specand@adobe/design-system-registryTypes of changes
Checklist: