@lotics/ui 47.13.0 → 47.13.1
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_entry.md +4 -1
- package/package.json +1 -1
package/docs/data_entry.md
CHANGED
|
@@ -284,7 +284,10 @@ field they would be both a false claim and dead buttons. The **popover** editors
|
|
|
284
284
|
(the resting box, wired as the popover trigger) with their OWN `useState` for open/draft/saving/
|
|
285
285
|
error — a pick, not a keystroke, is the edit, so `useInlineEdit` doesn't fit. `onSave` is async
|
|
286
286
|
either way: the saving spinner sits INSIDE the control at its right edge (never a sibling — that
|
|
287
|
-
reflows); an error shows inline without losing the edit.
|
|
287
|
+
reflows); an error shows inline without losing the edit. Saves overlap — the operator blurs one
|
|
288
|
+
field and edits the next while the first round trip is out — so land each result with the
|
|
289
|
+
updater form (`setForm((f) => ({ ...f, [key]: value }))`), never the form the save started from:
|
|
290
|
+
a snapshot lands the other field back at its pre-edit value while the server holds both.
|
|
288
291
|
|
|
289
292
|
To let a value be UNSET (a diff-write CLEAR — unassign, remove a due date, drop a select), pass
|
|
290
293
|
**`onClear`** to `InlineSelect` / `InlineMemberSelect` / `InlineDatePicker`. It surfaces through
|