@forumone/throughline 2.2.0-pr-312-ad011d0 → 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 +3 -3
- package/package.json +3 -3
package/CHANGELOG.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# @forumone/throughline
|
|
2
2
|
|
|
3
|
-
## 2.2.0
|
|
3
|
+
## 2.2.0
|
|
4
4
|
|
|
5
5
|
### Minor Changes
|
|
6
6
|
|
|
@@ -35,7 +35,7 @@
|
|
|
35
35
|
|
|
36
36
|
A link is either an internal link in Lexical rich text, or a relationship field marked with `custom: { throughlineLinkTarget: true }`. The design-system generator's `linkField` now marks its `reference`, so every generated link is covered without changes. To cover a hand-written link field, wrap it in `markLinkTarget` from `@forumone/throughline/publishing`. A marked reference whose sibling `mode` isn't `internal` is ignored, and `markLinkTarget(field, { when })` takes a different rule. The structural walk behind `referencesIn` is now `walkDocument`, exported from `/media` along with `linkTargetsIn`.
|
|
37
37
|
|
|
38
|
-
-
|
|
38
|
+
- a9d4873: The `link-targets` publish step now checks links inside composed sections (forumone-2026#756). A composed section stores its content as JSON, one value per field its recipe declares, so before this change a landing page whose composed-section link went to a draft, trashed or deleted page published without a warning. With `publishing.recipes` configured, the step reads every recipe the document uses in one query. It then walks each block's content by the recipe's `contract.content.fields`: a `link` (`{ mode, reference: { relationTo, value } }`, with the same `mode` rule as a generated link), internal links in a `richtext` field, and both of those inside a `group` or `array`. The verdicts and messages are the same as for any other link. The issue's `field` is the content field's path (`layout[2].content`), and its `where` is the block (`Block 3 (Composed section)`). `composedRecipeIds` and the `composed` option of `linkTargetsIn` are exported from `/media`.
|
|
39
39
|
|
|
40
40
|
A new subpath, `@forumone/throughline/links`, exports `markLinkTarget`, `LINK_TARGET_KEY` and `linkTargetMarker`. It imports nothing at run time, so a link-field helper that a `'use client'` module also imports can mark its reference. `/publishing` still exports `markLinkTarget` and `LINK_TARGET_KEY`.
|
|
41
41
|
|
|
@@ -45,7 +45,7 @@
|
|
|
45
45
|
|
|
46
46
|
- Updated dependencies [623d42c]
|
|
47
47
|
- Updated dependencies [332baf9]
|
|
48
|
-
- @forumone/throughline-design-system@2.2.0
|
|
48
|
+
- @forumone/throughline-design-system@2.2.0
|
|
49
49
|
|
|
50
50
|
## 2.1.0
|
|
51
51
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@forumone/throughline",
|
|
3
|
-
"version": "2.2.0
|
|
3
|
+
"version": "2.2.0",
|
|
4
4
|
"description": "Throughline: an editorial platform for Payload CMS. Publishing, approvals, audit, integrations, email and jobs, with every feature reachable over MCP.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"main": "./dist/index.js",
|
|
@@ -170,7 +170,7 @@
|
|
|
170
170
|
"dependencies": {
|
|
171
171
|
"zod": "^3.23.0",
|
|
172
172
|
"zod-to-json-schema": "^3.25.2",
|
|
173
|
-
"@forumone/throughline-design-system": "2.2.0
|
|
173
|
+
"@forumone/throughline-design-system": "2.2.0"
|
|
174
174
|
},
|
|
175
175
|
"devDependencies": {
|
|
176
176
|
"@payloadcms/db-sqlite": "^3.83.0",
|
|
@@ -194,7 +194,7 @@
|
|
|
194
194
|
"typescript": "^5.6.0",
|
|
195
195
|
"vitest": "^4.1.10",
|
|
196
196
|
"@forumone/throughline-eslint-config": "0.0.1",
|
|
197
|
-
"@forumone/throughline-reference-ds": "0.3.22
|
|
197
|
+
"@forumone/throughline-reference-ds": "0.3.22",
|
|
198
198
|
"@forumone/throughline-tsconfig": "0.0.1"
|
|
199
199
|
},
|
|
200
200
|
"scripts": {
|