@adobe/design-data-spec 4.11.0 → 4.11.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
CHANGED
|
@@ -32,7 +32,7 @@ A record's own `rationale` is copied into the entry when present. History comes
|
|
|
32
32
|
| `documentation` | Descriptions, document blocks, rationale, relationship context text |
|
|
33
33
|
| `metadata` | Legacy keys, ids, ordering, implementations, spec bookkeeping (summarized, not listed) |
|
|
34
34
|
|
|
35
|
-
**Metadata-class changes are not entries.** Each commit records them as `metadata: {count, fields}`: how many changes, and which field paths changed (a record added or removed is named `<kind> <change>`, e.g. `implementation added`). They count as a patch.
|
|
35
|
+
**Metadata-class changes are not entries.** Each commit records them as `metadata: {count, fields}`: how many changes, and which field paths changed (a record added or removed is named `<kind> <change>`, e.g. `implementation added`). They count as a patch. Removing a relationship whose exact twin survives (same scope, context and `$ref` or value) is metadata: nothing changes for consumers. Re-scoping a record (`scope.options` added or changed, same component, property, context and target) is an update, not a removal and an addition.
|
|
36
36
|
|
|
37
37
|
In the committed file every entry, source and metadata summary is written on one line.
|
|
38
38
|
|