@plitzi/sdk-style 0.35.9 → 0.36.0

package/CHANGELOG.md

@@ -1,5 +1,75 @@
 # @plitzi/sdk-style
 
+## 0.36.0
+
+### Minor Changes
+
+- - **An `apiContainer` can keep its browser requests in a query cache, the way react-query does.** Moving between
+    sections or pages used to ask the API again every time a provider was shown: a provider in a hidden section is
+    mounted but disabled, so showing it fired a fresh request, and a page navigation remounted it and did the same.
+    With the new `cache: true` an answer is kept for `staleTime` seconds (30 by default) and shared by every cached
+    provider asking the same thing — same method, URL, credentials and headers, the token included, so two visitors
+    never share one. Past its time the answer is still drawn at once and a fresh one is fetched behind it; an answer
+    nobody shows is forgotten after `gcTime` seconds (300 by default). A refused request (`4xx`/`5xx`) is shown but
+    never kept. **The cache is off unless an element asks for it**: an uncached provider behaves as before, asking on
+    every mount and sharing nothing.
+
+    The cache is `@plitzi/sdk-shared/queries` (`queryCache`, `useQuery`, `invalidateQueries`,
+    `invalidateQueriesForWrite`), a nexus store written with the per-path `ttl` of `@plitzi/nexus` 1.2.0, which every
+    consumer now requires. It reacts to the store's own freshness events, so anything that expires a query's path
+    makes the providers on screen ask again.
+
+    An answer stops counting as current before its time when the element's `performQuery` runs (it always asks
+    again), when a flow runs the new global `invalidateQueries` step (source `queries`: `elements`, api container ids
+    — a container's requests are tagged with its own id — and/or a `url` prefix), and after a write. Both write steps
+    gained `invalidateQueries` / `invalidateElements`: a `webHook` sent with anything but `GET`/`HEAD` refreshes the
+    requests to its own site by default, a completed `runServerAction` refreshes all of them by default, and either
+    can name containers instead or refresh nothing. A `writeRecord` refreshes all. Providers on screen ask again at
+    once; the rest when they are next shown. A sign-in, sign-out or change of account drops everything held. Server-driven
+    providers and RSC are untouched.
+
+  - **A `webHook` that reads can be cached** (`cache`, `staleTime`), in the same cache and under the same key as an api
+    container asking the same thing. Its declaration now lives beside it (`utility/webHookSpec`) and the authoring
+    catalog gathers it instead of keeping a copy. A `HEAD` is no longer sent with a body, which `fetch` refused.
+
+  - **Step params can pick several elements.** A new param type, `elementIds` (with an `elementType` filter), is drawn
+    in the flow editor as a picker: the matching elements of the space to add, and the picked ones as chips to remove —
+    an id no element answers to any more is kept and flagged. The value is a list of ids, so nobody types a
+    comma-separated list; `invalidateQueries.elements` and the write steps' `invalidateElements` use it, and the MCP
+    catalog says which element type each such param takes.
+
+  - The dev-tools' Store tab lists the paths a store holds with a TTL — how long ago each was written, what is left
+    of it, and a button to expire one or all of them. The query cache appears there as "Queries".
+
+  - `useApi` no longer takes `params`: nothing passed them, and a GET cannot carry a body anyway. A mock now answers
+    synchronously, without a loading frame, and a provider whose URL has not resolved asks for nothing.
+
+### Patch Changes
+
+- Updated dependencies
+  - @plitzi/sdk-plugins@0.36.0
+  - @plitzi/sdk-shared@0.36.0
+  - @plitzi/sdk-variables@0.36.0
+
+## 0.35.10
+
+### Patch Changes
+
+- **Breaking:** the space setting that lets a published site open the dev tools is now `settings.debugMode`, and
+  `settings.devTools` is gone.
+
+  It was always the same decision the SDK and the page server call `debugMode` — whether the dev-tools panel is
+  authorized — and having a third name for it invited confusing it with `devMode`, which is a different thing: it turns a
+  deployment into a development server (the unminified bundles, request timings, and the full action trace with every
+  step's results). A space can authorize debugging for its own site; it can never make its server a development one.
+
+  A space that stored `settings.devTools` needs it moved to `settings.debugMode`; nothing reads the old key.
+
+- Updated dependencies
+  - @plitzi/sdk-plugins@0.35.10
+  - @plitzi/sdk-shared@0.35.10
+  - @plitzi/sdk-variables@0.35.10
+
 ## 0.35.9
 
 ### Patch Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@plitzi/sdk-style",
-  "version": "0.35.9",
+  "version": "0.36.0",
   "license": "AGPL-3.0",
   "files": [
     "dist"
@@ -909,9 +909,9 @@
   },
   "dependencies": {
     "@plitzi/plitzi-ui": "^1.6.21",
-    "@plitzi/sdk-plugins": "0.35.9",
-    "@plitzi/sdk-shared": "0.35.9",
-    "@plitzi/sdk-variables": "0.35.9",
+    "@plitzi/sdk-plugins": "0.36.0",
+    "@plitzi/sdk-shared": "0.36.0",
+    "@plitzi/sdk-variables": "0.36.0",
     "clsx": "^2.1.1",
     "immer": "^11.1.18",
     "prop-types": "^15.8.1",