@stonecrop/desktop 0.35.0 → 0.36.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.
Files changed (2) hide show
  1. package/README.md +1 -1
  2. package/package.json +5 -5
package/README.md CHANGED
@@ -160,7 +160,7 @@ Three things are adjustable, for the cases that genuinely differ between applica
160
160
 
161
161
  `args` is an opaque JSON array: nothing validates it, so both ends of your own stack have to agree. A backend taking positional `[recordId, data]` supplies `buildArgs` to say so.
162
162
 
163
- Resolving a record's identity and keying it into HST are deliberately **not** adjustable. That rule is declared on the doctype and re-derived server-side by the adapter, and every host that re-derived it client-side got it wrong. If you dispatch through `Stonecrop.dispatchAction` directly instead of using this composable, that method still files the returned record under the settled identity, so you cannot store it under the wrong key by accident. What you lose is the stale-key cleanup and the route-follow, which need the id you dispatched.
163
+ Resolving a record's identity and keying it into HST are deliberately **not** adjustable. That rule is declared on the doctype and re-derived server-side by the adapter, and every host that re-derived it client-side got it wrong. If you dispatch through `Stonecrop.dispatchAction` directly instead of using this composable, that method still files the result's `record` (the server's read of the record after the action) under the settled identity, so you cannot store it under the wrong key by accident. What you lose is the stale-key cleanup and the route-follow, which need the id you dispatched.
164
164
 
165
165
  Do not copy form data into HST before dispatching. Desktop already hands you the current form snapshot in `payload.data`, and an unsaved record has no HST node to write to.
166
166
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@stonecrop/desktop",
3
- "version": "0.35.0",
3
+ "version": "0.36.0",
4
4
  "description": "Desktop-specific components for Stonecrop UI",
5
5
  "keywords": [
6
6
  "components",
@@ -44,10 +44,10 @@
44
44
  "access": "public"
45
45
  },
46
46
  "dependencies": {
47
- "@stonecrop/aform": "0.35.0",
48
- "@stonecrop/schema": "0.35.0",
49
- "@stonecrop/stonecrop": "0.35.0",
50
- "@stonecrop/themes": "0.35.0"
47
+ "@stonecrop/schema": "0.36.0",
48
+ "@stonecrop/stonecrop": "0.36.0",
49
+ "@stonecrop/aform": "0.36.0",
50
+ "@stonecrop/themes": "0.36.0"
51
51
  },
52
52
  "devDependencies": {
53
53
  "@microsoft/api-extractor": "^7.58.7",