@lotics/app-sdk 0.123.9 → 0.123.10
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/docs/data_fetching.md +3 -1
- package/package.json +1 -1
package/docs/data_fetching.md
CHANGED
|
@@ -159,7 +159,9 @@ write it as `{ node_type: "condition", type: "record_id", operator, value }`.
|
|
|
159
159
|
§ A write shows from the press.
|
|
160
160
|
- **Realtime push keeps an already-open screen current.** When a table one of your queries reads
|
|
161
161
|
changes — another member, a workflow, the chat agent, or an external agent writing over the CLI or
|
|
162
|
-
MCP — that query refetches within about a second
|
|
162
|
+
MCP — that query refetches within about a second; a screen out of sight (a hidden tab, or an app
|
|
163
|
+
the host keeps while another is shown) refetches once, when shown, for every query that moved
|
|
164
|
+
meanwhile. Nothing to wire: it follows from the query's own
|
|
163
165
|
declaration, and only the aliases whose tables actually moved refetch. The queries one push names
|
|
164
166
|
re-render together — each answer held until all have landed, never past a second — so a screen never
|
|
165
167
|
shows one change in pieces and a slow query never holds the rest. It carries RECORD
|
package/package.json
CHANGED