@forumone/throughline-design-system 2.2.0-pr-311-6957fbf → 2.2.0
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/CHANGELOG.md +2 -2
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,10 +1,10 @@
|
|
|
1
1
|
# @forumone/throughline-design-system
|
|
2
2
|
|
|
3
|
-
## 2.2.0
|
|
3
|
+
## 2.2.0
|
|
4
4
|
|
|
5
5
|
### Minor Changes
|
|
6
6
|
|
|
7
|
-
-
|
|
7
|
+
- 623d42c: Messages an editor can read now make sense to an editor: they say what happened in the editor's terms, what to do next, and to "tell a site administrator" when only somebody else can fix it. (forumone-2026#805)
|
|
8
8
|
|
|
9
9
|
- **The publish-blocked notification lists issues where the editor finds them.** It no longer starts "Blocked at: composition", lists `layout[2]: …` or `(root): …`, or prefixes "Suggestion:". Every pipeline issue gains `where`, its `field` as the collection's labels say it — `Block 3 (Image Hero) › Image`, `SEO › Title` — computed from the field config for built-in and custom checks alike, and the admin prints it before the message. An issue marked on an ancestor field (three blocks' problems on `layout`) says which block it is about.
|
|
10
10
|
- **Components are named by their block's label,** not their contract name. The composition validator takes a `label` function; the publish step passes each block's `labels.singular`, and the `validate_composition` MCP tool keeps contract names. `componentDisplayName` (`ImageHero` → `Image Hero`) is exported from `@forumone/throughline-design-system/contract`.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@forumone/throughline-design-system",
|
|
3
|
-
"version": "2.2.0
|
|
3
|
+
"version": "2.2.0",
|
|
4
4
|
"description": "The design-system side of Throughline: the component contract and manifest a design system publishes, its linter, and the Payload blocks, rendering and admin components generated from it.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"exports": {
|