@loadbare/app 0.7.3 → 0.8.0

package/docs/tutorials/080-widget-requests.md

@@ -37,7 +37,7 @@ class NoteInput extends HTMLElement {
       this.dispatchEvent(
         new CustomEvent(LB_EVENT_NAME, {
           bubbles: true,
-          detail: { action: "lb-cell-change", value: input.value },
+          detail: { action: "lb-row-update", value: input.value },
         }),
       );
     });
@@ -49,9 +49,9 @@ customElements.define("note-input", NoteInput);
 
 A widget with both a `.html` and a `.browser.ts` file shares one tag name; the
 build finds each half independently. On change, it dispatches a
-`lb-cell-change` carrying the input's value. The hub adds the list, the key
-of the row it is in and its own `lb-cell`, the same way it does for a
-`lb-row-update` form.
+`lb-row-update` carrying the input's value. The hub adds the list and the key
+of the row it is in, and turns the value into a `values` map holding only
+the widget's own `lb-cell`.
 
 ## Using it
 
@@ -72,30 +72,11 @@ every change, so there's nothing left to batch.
 
 ## Answering it server-side
 
-```ts
-// src/pages/about.requests.ts
-import { patch } from "@loadbare/app/server";
-
-export const requests = {
-  // ...onPageEnter and actions unchanged...
-  crud: {
-    notes: {
-      // ...rowInsert, rowDelete, rowUpdate unchanged...
-      cellChange: {
-        run: async (ctx, { key, value }) => {
-          const note = await ctx.db.updateNote(key, value);
-          return { notes: patch({ rows: [note] }) };
-        },
-        refresh: [],
-      },
-    },
-  },
-};
-```
-
-`cellChange` reuses `updateNote` from [Updating a List Item](./076-updating-a-list-item.md)
-— the database doesn't care whether the edit came from a form's values
-map or one widget's value.
+There is nothing to add. The request is the same `lb-row-update` the form
+sent in [Updating a List Item](./076-updating-a-list-item.md), with `values`
+holding only `text`, so the `rowUpdate` written there answers it unchanged.
+A `rowUpdate` sets the columns `values` names and leaves the rest alone, as
+an SQL `UPDATE` does, so one handler serves a form and a widget alike.
 
 ## Run it
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@loadbare/app",
   "description": "High performance web app framework for server-bound applications",
-  "version": "0.7.3",
+  "version": "0.8.0",
   "type": "module",
   "files": [
     "dist",