Skip to content

Commit fecce55

Browse files
committed
docs(changeset): name the round-4 readers, rewrap the 9673 entry, and past-tense PageView's remount in the react-page entry
- 10519-pageview-refresh-in-place: the block list adds what the round-4 census measured green through a real page action: a dashboard's optionsFrom filter options (its selected value kept) and an object-view drawn as a kanban, calendar, gallery or timeline. A kind:'react' page is named apart: its own read re-runs in place when its effect names the injected useDataInvalidation nonce, and a read keyed on useAdapter alone is not re-run by a page action. - 9673-pageview-drop-context-spread: the replaced sentence is rewrapped to the file's width; the words are unchanged. - 10887-react-page-data-invalidation (pending): "as PageView does after a page action" becomes "did"; this branch stops that remount in the same release. Frontmatter unchanged in all three. Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DuWo5bdP9SdVebamn99GGk
1 parent beac974 commit fecce55

3 files changed

Lines changed: 16 additions & 9 deletions

File tree

‎.changeset/10519-pageview-refresh-in-place.md‎

Lines changed: 11 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -19,8 +19,14 @@ the bus refetch in place, once each: the object grid, chart, detail view, list
1919
view, kanban, metric, calendar, gallery, timeline, gantt, map, tree, pivot and
2020
data table, every `object-form` layout, `object-master-detail-form` (edit-mode
2121
lines), `report` / `spec-report` over a dataset, a `dashboard`'s dataset table
22-
widget, `record:line_items` with an authored parent, and the `element:number` /
23-
`element:repeater` / `element:record_picker` readers. An `object-form` holding
24-
unsaved input keeps it and takes the re-read when it is saved or reverted
25-
(objectui#10572). The page node's `context` is `{ params }` alone: nothing read
26-
the `refreshKey` it also carried. No prop, export or schema key changes.
22+
widget and its `optionsFrom` filter options, an `object-view` drawn as a kanban,
23+
calendar, gallery or timeline, `record:line_items` with an authored parent, and
24+
the `element:number` / `element:repeater` / `element:record_picker` readers. An
25+
`object-form` holding unsaved input keeps it and takes the re-read when it is
26+
saved or reverted (objectui#10572), and a dashboard filter keeps its selected
27+
value. A `kind: 'react'` page is no longer remounted either: its own read
28+
re-runs in place when its effect names the `useDataInvalidation` nonce the page
29+
scope injects (objectui#10887), and a read keyed on `useAdapter` alone is not
30+
re-run by a page action. The page node's `context` is `{ params }` alone:
31+
nothing read the `refreshKey` it also carried. No prop, export or schema key
32+
changes.

‎.changeset/10887-react-page-data-invalidation.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ feat(components): a `kind: 'react'` page's author scope injects `useDataInvalida
77
A react page reads data through the injected `useAdapter`, in an effect it
88
writes itself. The scope gave that effect no data-invalidation reader to name,
99
so the read the react-pages guide taught, keyed on `[adapter]`, re-ran only
10-
when the page was remounted (as `PageView` does after a page action) or its
10+
when the page was remounted (as `PageView` did after a page action) or its
1111
adapter changed.
1212

1313
The scope now injects `useDataInvalidation` from `@object-ui/react` beside

‎.changeset/9673-pageview-drop-context-spread.md‎

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,7 @@ fix(app-shell): `PageView` builds the page node's `context`, it no longer reads
77
`PageView` spread `(page as any).context` into the `context` it hands `SchemaRenderer`.
88
`PageSchema` refuses a page-level `context` key, so on every page that parses the
99
spread added nothing, and the code read as an author channel that no author could use.
10-
The node's `context` is now built from the route alone, and the `as any` cast at that spot is gone. A stored document
11-
that carries `context` without passing `PageSchema` no longer passes it through.
12-
`context` stays undeclared on `PageSchema` (objectui#9673).
10+
The node's `context` is now built from the route alone, and the `as any` cast at that
11+
spot is gone. A stored document that carries `context` without passing `PageSchema`
12+
no longer passes it through. `context` stays undeclared on `PageSchema`
13+
(objectui#9673).

0 commit comments

Comments
 (0)