@adobe/design-data-spec 3.4.0 → 3.4.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/package.json +1 -1
- package/spec/manifest.md +15 -0
package/package.json
CHANGED
package/spec/manifest.md
CHANGED
|
@@ -61,6 +61,16 @@ Each override object **MUST** include enough information to identify a target to
|
|
|
61
61
|
|
|
62
62
|
**NORMATIVE:** Overrides **MUST NOT** change the resolved type of the token (aligns with [Cascade — type safety](cascade.md)).
|
|
63
63
|
|
|
64
|
+
An override is applied as a new **platform-layer** record, not an in-place edit of the
|
|
65
|
+
foundation record it targets — the original foundation record is left untouched.
|
|
66
|
+
[Query](query.md) reports records across all cascade layers, so a query over an overridden
|
|
67
|
+
token's selector returns both the untouched foundation record and the new platform-layer
|
|
68
|
+
record (e.g. an override on a `state=disabled` token increases the matching count by one,
|
|
69
|
+
rather than replacing an existing match). Only [`resolve` / `resolve_property`](cascade.md)
|
|
70
|
+
apply `Foundation < Platform < Product` precedence to select a single winner. Tooling that
|
|
71
|
+
counts "tokens a platform ships" from `query` output should resolve first, or it will
|
|
72
|
+
double-count overridden tokens.
|
|
73
|
+
|
|
64
74
|
### `extensions`
|
|
65
75
|
|
|
66
76
|
**RECOMMENDED:** `extensions` follows the same structural conventions as foundation token files (tokens, mode sets) and **SHOULD** be validated with the same Layer 1 and Layer 2 rules.
|
|
@@ -132,6 +142,11 @@ A platform **MAY** declare formatting rules that control how structured name obj
|
|
|
132
142
|
|
|
133
143
|
**RECOMMENDED:** Validators resolve `foundationVersion` against a registry or lockfile and report mismatches as errors or warnings per product policy.
|
|
134
144
|
|
|
145
|
+
**RECOMMENDED:** Validators confirm the resolved `foundationVersion` provides a cascade-format
|
|
146
|
+
dataset (`packages/design-data/*`), not a pre-cascade legacy release predating the structured
|
|
147
|
+
`name` object, mode sets, and UUIDs — a manifest cascaded against a pre-cascade pin is not
|
|
148
|
+
meaningful. Report a pre-cascade pin as an error per product policy.
|
|
149
|
+
|
|
135
150
|
## Automated upgrades
|
|
136
151
|
|
|
137
152
|
**OPTIONAL:** Workflows **MAY** open upgrade PRs when `foundationVersion` lags the latest release; details are out of scope for this document (see [#715](https://github.com/adobe/spectrum-design-data/discussions/715)).
|