@molecule/app-react-native 3.0.3 → 3.0.5

package/README.md

@@ -3,7 +3,7 @@ AUTO-GENERATED — DO NOT EDIT THIS FILE.
 Generated by `mlcl sync-docs` from the package's src/index.ts JSDoc + mlcl/registry.json.
 Edits here are overwritten on the next commit (molecule's pre-commit hook regenerates).
 To change this document, edit the module-level JSDoc in src/index.ts.
-Generated: 2026-11-04T14:20:07.525Z
+Generated: 2026-11-06T02:49:48.362Z
 -->
 
 # @molecule/app-react-native
@@ -3292,7 +3292,8 @@ const useAsyncState: <T>(initialState: T) => [T, AsyncSetState<T>, AsyncExtendSt
 
 A server-backed value — a favorite, follow, like or bookmark button, a rating, a quantity, a
 setting switch — that changes on the first render after a tap and is saved one change at a
-time, in order. A tap during a save is saved right after it; only a failure of the newest
+time, in order. Taps during a save update the desired value; the newest waiting value is
+saved after it (intermediate waiting values coalesce). Only a failure of the newest
 change puts the server value back. See `createOptimisticValue` in `@molecule/app-state`.
 
 `value` is the server's value from props or a query. A new `value` is taken only when it
@@ -3300,6 +3301,18 @@ differs (by `equals`) from the one the hook last received, and only while nothin
 saved, so a parent re-render or a refetch of older data never flips the button mid-save. The
 latest `commit` and `onError` are always used. Give the component a `key` per record, so one
 record's pending change never shows on another.
+Keep related fields, such as a favorite flag and its count, in the SAME value. Return both
+from the server response in `commit`, and publish that response to parent/query caches there
+if needed. Let commit reject on failure: a catch that returns old data hides the failure.
+Replace display-state setters and prop-copy effects with this hook's value and `update`.
+`pending` is for feedback, never a reason to disable the toggle or drop a tap.
+
+Render/enable the keyed control only once its initial record exists. Keep that control
+mounted through refetches of the same record. This hook does not fix a click handler that
+returns on a still-null profile, or a remount that throws its controller away. Refetches
+during a save cannot replace pending intent; changed server snapshots arriving AFTER saving
+finishes are accepted and need query-layer ordering if they can be stale. See the module
+quickstart for a complete favorite button with a server-confirmed count.
 
 ```typescript
 const useOptimisticValue: <T>(options: OptimisticValueOptions<T>) => UseOptimisticValueResult<T>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@molecule/app-react-native",
-  "version": "3.0.3",
+  "version": "3.0.5",
   "description": "React Native framework bindings for molecule.dev",
   "homepage": "https://www.molecule.dev/packages/app-react-native",
   "type": "module",
@@ -33,7 +33,7 @@
     "directory": "packages/app/frameworks/react-native"
   },
   "devDependencies": {
-    "@molecule/app-react": "3.3.1",
+    "@molecule/app-react": "3.4.1",
     "@types/node": "26.6.5",
     "react": "19.3.1",
     "typescript": "6.0.3",
@@ -48,18 +48,12 @@
     "react-native-safe-area-context": ">=4.0.0"
   },
   "peerDependenciesMeta": {
-    "@molecule/app-react": {
-      "optional": true
-    },
     "@molecule/app-lifecycle": {
       "optional": true
     },
     "@molecule/app-keyboard": {
       "optional": true
     },
-    "react": {
-      "optional": true
-    },
     "react-native": {
       "optional": true
     },