@loadbare/app 0.5.5 → 0.6.0

package/dist/core/lb-constants.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"lb-constants.d.ts","sourceRoot":"","sources":["../../core/lb-constants.ts"],"names":[],"mappings":"AAKA,eAAO,MAAM,UAAU,aAAa,CAAC;AACrC,eAAO,MAAM,QAAQ,WAAW,CAAC;AACjC,eAAO,MAAM,SAAS,YAAY,CAAC;AACnC,eAAO,MAAM,UAAU,aAAa,CAAC;AAMrC,eAAO,MAAM,UAAU,aAAa,CAAC;AAKrC,eAAO,MAAM,SAAS,YAAY,CAAC;AAOnC,eAAO,MAAM,cAAc,cAAc,CAAC;AAK1C,eAAO,MAAM,aAAa,eAAe,CAAC;AAM1C,eAAO,MAAM,WAAW,cAAc,CAAC;AAMvC,eAAO,MAAM,WAAW,cAAc,CAAC;AAKvC,eAAO,MAAM,WAAW,cAAc,CAAC;AAOvC,eAAO,MAAM,WAAW,cAAc,CAAC;AAMvC,eAAO,MAAM,SAAS,YAAY,CAAC;AAYnC,eAAO,MAAM,aAAa,gBAAgB,CAAC;AAK3C,eAAO,MAAM,aAAa,gBAAgB,CAAC;AAG3C,eAAO,MAAM,oBAAoB,UAAU,CAAC;AAQ5C,eAAO,MAAM,iBAAiB,oBAAoB,CAAC;AAQnD,eAAO,MAAM,YAAY,WAAW,CAAC;AAQrC,eAAO,MAAM,YAAY,oBAAoB,CAAC;AAO9C,eAAO,MAAM,UAAU,kBAAkB,CAAC;AAG1C,eAAO,MAAM,gBAAgB,aAAa,CAAC;AAC3C,eAAO,MAAM,mBAAmB,QAAQ,CAAC;AAIzC,eAAO,MAAM,qBAAqB,QAAS,CAAC"}
+{"version":3,"file":"lb-constants.d.ts","sourceRoot":"","sources":["../../core/lb-constants.ts"],"names":[],"mappings":"AAUA,eAAO,MAAM,SAAS,YAAY,CAAC;AAQnC,eAAO,MAAM,QAAQ,WAAW,CAAC;AAMjC,eAAO,MAAM,QAAQ,WAAW,CAAC;AAMjC,eAAO,MAAM,cAAc,iBAAiB,CAAC;AAQ7C,eAAO,MAAM,SAAS,YAAY,CAAC;AAEnC,eAAO,MAAM,UAAU,aAAa,CAAC;AAOrC,eAAO,MAAM,cAAc,iBAAiB,CAAC;AAK7C,eAAO,MAAM,aAAa,eAAe,CAAC;AAS1C,eAAO,MAAM,WAAW,cAAc,CAAC;AAYvC,eAAO,MAAM,kBAAkB,QAAQ,CAAC;AAMxC,eAAO,MAAM,iBAAiB,kBAAkB,CAAC;AAKjD,eAAO,MAAM,iBAAiB,kBAAkB,CAAC;AAOjD,eAAO,MAAM,iBAAiB,kBAAkB,CAAC;AAMjD,eAAO,MAAM,kBAAkB,mBAAmB,CAAC;AAInD,eAAO,MAAM,UAAU,gFAKb,CAAC;AAMX,eAAO,MAAM,SAAS,YAAY,CAAC;AAYnC,eAAO,MAAM,aAAa,gBAAgB,CAAC;AAK3C,eAAO,MAAM,aAAa,gBAAgB,CAAC;AAM3C,eAAO,MAAM,SAAS,YAAY,CAAC;AAQnC,eAAO,MAAM,OAAO,kBAAkB,CAAC;AAKvC,eAAO,MAAM,cAAc,eAAe,CAAC;AAC3C,eAAO,MAAM,YAAY,aAAa,CAAC;AAUvC,eAAO,MAAM,iBAAiB,oBAAoB,CAAC;AAQnD,eAAO,MAAM,YAAY,WAAW,CAAC;AAQrC,eAAO,MAAM,YAAY,eAAe,CAAC;AAOzC,eAAO,MAAM,UAAU,aAAa,CAAC;AAMrC,eAAO,MAAM,WAAW,QAAQ,CAAC;AAIjC,eAAO,MAAM,qBAAqB,QAAS,CAAC"}

package/dist/core/lb-constants.js

@@ -2,49 +2,93 @@
 // literal — not a widget, not a page host, not a test. See
 // docs/reference/data-binding.md.
 // --- Binding (docs/reference/data-binding.md) ---------------------------
-export const ATTR_QUERY = "lb-query";
+// One containment ladder: a list holds rows, a row holds cells. Both scope
+// attributes take a name the server declares, and a nested one of either
+// kind begins a new scope.
+// Scopes DOM children to a named set of rows.
+export const ATTR_LIST = "lb-list";
+// Scopes DOM children to one named row.
+//
+// A single-row scope is read-only. Every write operation needs a key, and a
+// key exists only on a live row the hub stamped inside a list, so a declared
+// action is the only thing such a scope can send. An application that wants
+// a writable single row declares a list that answers with one row.
+export const ATTR_ROW = "lb-row";
+// Named on a row template by the developer: the column that identifies a row
+// of the list. A property of the list rather than of the template — a list
+// without a fixed key column is meaningless — but written where the rows
+// land, because that is the only place the page says anything about them.
 export const ATTR_KEY = "lb-key";
+// Stamped on a live row by the row machinery: that row's value of the column
+// ATTR_KEY names. Written by the hub, never by a developer, and read back by
+// whatever needs to know which row it is inside — a delete button, an update
+// form, a widget building its own request, or a stylesheet.
+export const ATTR_KEY_VALUE = "lb-key-value";
+// The column an element displays.
+//
+// Its value is a column name and never a cell name. A cell has no name of
+// its own: it is identified by its row and its column, and the row arrives
+// from scope, so the column is all that is left to say. ATTR_KEY holds a
+// column name for the same reason.
 export const ATTR_CELL = "lb-cell";
 export const ATTR_VALUE = "lb-value";
-// Named on a row template, and read by a list widget that groups its rows
-// rather than by the hub. Grouping is placement, and placement is the
-// widget's — but the name is shared, because a grouped <select> and a table
-// with section headings are asking the same thing of the same data.
-export const ATTR_GROUP = "lb-group";
-// Named on a row template beside lb-group, and read by the same kind of
-// widget for the same reason. Sorting and grouping are one question — where
-// does this row go? — and both answers are local.
-export const ATTR_SORT = "lb-sort";
-// Stamped on a list widget by the shared row machinery: how many rows it is
-// showing. It is HTML's namespace rather than Loadbare App's because nothing
-// binds to it — it is derived from rows the hub already knows, exactly as
-// the section heading in lb-table is. It exists so that "no members yet"
-// is a stylesheet rule rather than a conditional in every list widget.
-export const ATTR_ROW_COUNT = "data-rows";
+// Stamped on a list scope by the shared row machinery: how many rows it is
+// showing. Written by the hub and never bound to — it is derived from rows
+// the hub already knows, exactly as the section heading in lb-table is. A
+// list widget watches it, and it exists so that "no members yet" is a
+// stylesheet rule rather than a conditional in every list widget.
+export const ATTR_ROW_COUNT = "lb-row-count";
 // --- Requests (docs/reference/data-binding.md) --------------------------
 // One event name, used by a widget reaching the server and by a widget
 // reaching an ancestor widget.
 export const LB_EVENT_NAME = "lb-request";
-// Names a declared action. On a native element, the hub turns a click into
-// the request; on a widget, the widget builds it from whatever interaction
-// it owns. Either way the name must appear in the page's hooks or it is
-// refused.
+// Names what an interaction asks for.
+//
+// One attribute name, one wire field, one set of values: the request field
+// `action` carries this attribute's value verbatim, and nothing is
+// translated in between. On a native element the hub turns the element's own
+// event into the request — a form submits, anything else clicks; on a
+// widget, the widget builds it from whatever interaction it owns.
 export const ATTR_ACTION = "lb-action";
-// Marks a native element as deleting the tuple it is inside — the CRUD
-// counterpart to lb-action. It needs no declared name: tuple-delete takes
-// only the row's own lb-query/lb-key binding, which is all the server
+// --- Reserved names ----------------------------------------------------
+// Loadbare owns every value beginning with this prefix, in every lb-*
+// attribute: a name so prefixed is the hub's own (NAV_ROW), and an
+// lb-action so prefixed is an operation (below). The server refuses a page
+// that declares a query or an action beginning with it, so a new reserved
+// name can never collide with one an application already uses.
+//
+// It is also the whole of the wire discriminant. A request whose `action`
+// begins with it is one of the four operations; anything else is a name the
+// page declared under its requests. Nothing else tells them apart.
+export const LB_RESERVED_PREFIX = "lb-";
+// On a <form> in a list scope: builds a new row on submit. The hub gathers
+// every lb-cell inside the form into a values map — no key, because there is
+// no row yet — and the form's own lb-list says which list it is inserting
+// into.
+export const ACTION_ROW_INSERT = "lb-row-insert";
+// Deletes the row the element is inside. Needs no declared name: it takes
+// only the row's own lb-list/lb-key-value binding, which is all the server
 // needs to know which row and whether the operation is permitted on it.
-export const ATTR_DELETE = "lb-delete";
-// Marks a <form> as building a new tuple on submit. The hub gathers every
-// lb-cell inside it into a values map — no lb-key, because there is no row
-// yet — and the form's own lb-query says which query it is inserting into.
-export const ATTR_INSERT = "lb-insert";
-// Marks a <form> as committing several cells of one existing tuple at once
-// on submit — the batch counterpart to cell-change. The hub gathers the
-// same values map lb-insert does, plus the row's own lb-key: a form that is
-// a list's row template root, or sits inside one, has both from its
-// ancestors exactly as a delete button does.
-export const ATTR_UPDATE = "lb-update";
+export const ACTION_ROW_DELETE = "lb-row-delete";
+// On a <form> inside a live row: commits several cells of that row at once
+// on submit — the batch counterpart to a cell change. The hub gathers the
+// same values map, plus the row's own lb-key-value: a form that is a list's
+// row template root, or sits inside one, has both from its ancestors exactly
+// as a delete button does.
+export const ACTION_ROW_UPDATE = "lb-row-update";
+// On a widget wrapping one control: commits that one cell when the control
+// changes. The hub never sends this itself — a native element has no widget
+// to decide what a change is — so a widget that carries it builds the
+// operation from its own lb-list/lb-key-value/lb-cell binding.
+export const ACTION_CELL_CHANGE = "lb-cell-change";
+// Every reserved lb-action, in one place, so the builder can refuse an
+// unknown one and the hub can refuse to send one it does not implement.
+export const LB_ACTIONS = [
+    ACTION_ROW_INSERT,
+    ACTION_ROW_DELETE,
+    ACTION_ROW_UPDATE,
+    ACTION_CELL_CHANGE,
+];
 // --- Expansion (docs/reference/custom-elements.md) ---------------------
 // Marks the element in a definition whose children receive the authored
 // inner content. An attribute rather than an element because HTML content
@@ -65,14 +109,31 @@ export const ATTR_TEMPLATE = "lb-template";
 // Only anchors carrying this are intercepted, so external links are never
 // hijacked.
 export const ATTR_NAV_LINK = "lb-nav-link";
-// A page host ships as <template id="page-<name>">.
-export const PAGE_TEMPLATE_PREFIX = "page-";
+// A page host ships as <template lb-page="<name>">. An attribute rather than
+// an id: an id lives in the application's own namespace, where a page named
+// for something the chrome also ids would collide, and getElementById()
+// answers a collision by silently picking one.
+export const ATTR_PAGE = "lb-page";
+// The hub's own row. Landed on every navigation, on any subtree inside the
+// hub that names it, through the same applyData() a server answer goes
+// through — so a chrome displays where the page is the way it displays
+// anything else. One row rather than a list, so a subtree binds it with
+// lb-row. A reserved name (LB_RESERVED_PREFIX): the server refuses to
+// declare a query so named.
+export const NAV_ROW = "lb-navigation";
+// Its two columns. The label is the nav's: the text of the lb-nav-link
+// anchor whose href names the current page, and empty when no anchor does.
+// The URI is the path as the browser has it.
+export const NAV_CELL_LABEL = "page-label";
+export const NAV_CELL_URI = "page-uri";
 // Marks the chrome's own <dialog> for a page name that resolves to no
 // template — a routing miss discovered client-side, not an HTTP 404 (every
 // route gets the same 200 response; see docs/tutorials/010-pages-and-navigation.md).
-// Optional: an application that declares none gets today's console.error
-// and nothing more. The builder requires the element it's on to be a
-// <dialog> (build/assemble.ts), since the hub calls showModal() on it.
+// The hub only opens it; what it says comes from NAV_ROW, which the dialog
+// consumes like any other subtree, by naming it in lb-row. Optional: an
+// application that declares none gets today's console.error and nothing
+// more. The builder requires the element it's on to be a <dialog>
+// (build/assemble.ts), since the hub calls showModal() on it.
 export const ATTR_UNKNOWN_PAGE = "lb-unknown-page";
 // The hub's own tag. It is exempt from the rule every other LB-* tag
 // follows: expansion does not require it to have a definition (build/expand.ts),
@@ -87,16 +148,18 @@ export const HUB_TAG_NAME = "lb-hub";
 // meaning beyond "in flight": a stylesheet dims the element, or a custom
 // button widget watches it to disable itself, but the hub itself only sets
 // and clears it.
-export const ATTR_PENDING = "data-lb-pending";
+export const ATTR_PENDING = "lb-pending";
 // Stamped on the same element if that round trip failed — a non-2xx
 // response, a thrown application error, or a timeout, all alike. Cleared at
 // the start of that element's next request. What (if anything) an
 // application shows for it is undecided; this is only the fact that it
 // happened.
-export const ATTR_ERROR = "data-lb-error";
+export const ATTR_ERROR = "lb-error";
 // --- Wire --------------------------------------------------------------
-export const LB_DATA_ENDPOINT = "/lb/data";
-export const LB_REQUEST_ENDPOINT = "/lb";
+// One path, one method: everything the hub asks of the server is a POST to
+// this path. Navigation is therefore the only GET an application serves,
+// which is what leaves the page name space unrestricted.
+export const LB_ENDPOINT = "/lb";
 // A client-side deadline for one round trip. fetch() has no deadline of its
 // own; past this the request is aborted and treated as a failure.
 export const LB_REQUEST_TIMEOUT_MS = 10_000;

package/dist/core/lb-types.d.ts

@@ -1,88 +1,129 @@
-/** docs/reference/data-binding.md — the operation set is closed. */
-export type HubRequest = {
-    op: "cell-change";
-    query: string;
-    key: string;
-    cell: string;
-    value: string;
-} | {
-    op: "tuple-insert";
-    query: string;
+import { ACTION_CELL_CHANGE, ACTION_ROW_DELETE, ACTION_ROW_INSERT, ACTION_ROW_UPDATE } from "./lb-constants";
+/**
+ * One row: its columns, by name.
+ *
+ * A value is whatever the server serialized. The hub knows nothing about its
+ * type and enforces nothing: it hands each value to the browser untouched,
+ * and the browser renders it as it sees fit. What a number, a date or a null
+ * should look like is the application's decision, made in the query.
+ */
+export type Row = Record<string, unknown>;
+/**
+ * Part of a list — see docs/reference/server.md, "Queries".
+ *
+ * Rows named here arrive or are updated, keys in `drop` are gone, and
+ * anything unnamed is left alone: its contents, and its place in whatever
+ * order the widget is keeping. Add and remove are one result rather than two
+ * because the interesting cases are both at once — a row whose sort key
+ * changed has to move, a swap is one out and one in — and two messages would
+ * paint the intermediate state.
+ */
+export interface Patch {
+    rows?: Row[];
+    drop?: unknown[];
+}
+/**
+ * What a list answers with.
+ *
+ * An array is the entire set and therefore also the order: a row whose key
+ * is not in it is gone. A Patch disturbs only what it names.
+ *
+ * `Array.isArray` tells the two apart, which is why no column name has to be
+ * reserved to carry a discriminant. A list answering with an object is a
+ * patch, because the declaration already said this name answers with rows.
+ */
+export type ListResult = Row[] | Patch;
+export declare function isPatch(result: ListResult): result is Patch;
+/**
+ * What any one name answers with. Which of the two it is comes from the
+ * query's own declaration, never from inspecting the value.
+ */
+export type HubResult = Row | ListResult;
+/**
+ * Every response on the data channel is the same shape, whether it is a cold
+ * start or the narrowest refresh. The hub does not know which case it is in.
+ *
+ * A name rides as an object key and is labelled by nothing, which is why the
+ * response direction never needed a noun for the addressable thing.
+ */
+export type HubData = Record<string, HubResult>;
+/**
+ * The four operations — docs/reference/data-binding.md. The set is closed.
+ *
+ * `action` carries the value of `lb-action` verbatim, so the attribute, the
+ * wire field and the CRUD key are one vocabulary with no translation step.
+ * The scope field is `list` here because all four are list operations: each
+ * needs a key, and a key exists only on a live row inside a list.
+ */
+export type LbOperation = {
+    action: typeof ACTION_ROW_INSERT;
+    list: string;
     values: Record<string, string>;
 } | {
-    op: "tuple-update";
-    query: string;
+    action: typeof ACTION_ROW_DELETE;
+    list: string;
+    key: string;
+} | {
+    action: typeof ACTION_ROW_UPDATE;
+    list: string;
     key: string;
     values: Record<string, string>;
 } | {
-    op: "tuple-delete";
-    query: string;
+    action: typeof ACTION_CELL_CHANGE;
+    list: string;
     key: string;
-}
+    cell: string;
+    value: string;
+};
 /**
- * Everything that is not a CRUD operation.
+ * Everything that is not one of the four.
  *
  * The name is the application's and is looked up in the page's declared
  * actions. What keeps this from being an RPC endpoint is that the name must
- * already appear in the page's hooks: the browser cannot reach anything the
+ * already appear in the page's requests: the browser cannot reach anything the
  * page has not published, and there is no argument list — only where the
  * interaction happened and, where a control has one, its value.
  *
- * A button carries no value, so the server computes the whole of the new
+ * The scope field is `list` or `row`, whichever attribute scoped the element
+ * the interaction came from, so an action fired from a single-row scope says
+ * so. A button carries no value, so the server computes the whole of the new
  * state and the browser never displays a number it has not confirmed. A
  * `<select>` carries one, because the choice is the interaction.
  */
- | {
-    op: "action";
-    name: string;
-    query?: string;
+export interface DeclaredAction {
+    action: string;
+    list?: string;
+    row?: string;
     key?: string;
     cell?: string;
     value?: string;
-};
-/** One query's result: the cells of a single tuple. Every value is a string. */
-export type QueryResult = Record<string, string>;
-/**
- * A query that returns many tuples — see docs/reference/server.md, "Queries".
- *
- * Two results, because a list widget must be told the difference. `rows` is
- * the entire set and therefore also the order; `patch` names only what
- * changed and leaves everything it does not name alone. Add and remove are
- * one result rather than two because the interesting cases are both at once
- * — a row whose sort key changed has to move, a swap is one out and one in —
- * and two messages would paint the intermediate state.
- *
- * `op` is the same discriminant word the request union uses, so one
- * vocabulary runs in both directions. It is therefore a reserved cell name:
- * a tuple with a cell called `op` whose value is `rows` or `patch` would be
- * read as a projection.
- */
-export type Projection = {
-    op: "rows";
-    rows: QueryResult[];
-} | {
-    op: "patch";
-    rows?: QueryResult[];
-    drop?: string[];
-};
-/** A tuple is the sugar and the common case; a projection says so. */
-export type HubResult = QueryResult | Projection;
-export declare function isProjection(result: HubResult): result is Projection;
+}
+export type HubRequest = LbOperation | DeclaredAction;
 /**
- * Every response on the data channel is the same shape, whether it is a
- * cold start or the narrowest refresh. The hub does not know which case
- * it is in.
+ * The reserved prefix is the whole of the discriminant. Nothing else tells
+ * an operation from a declared action, on the wire or anywhere else.
  */
-export type HubData = Record<string, HubResult>;
+export declare function isOperation(request: HubRequest): request is LbOperation;
 /**
- * What a list widget implements. The hub delivers a projection by calling
- * this and stops; where a row goes is the widget's, because only the widget
- * knows whether it sorts, groups, or appends.
+ * The two hooks a list widget may implement, both optional.
+ *
+ * The hub reconciles every list scope itself, so a widget supplies placement
+ * and scaffolding and nothing else. A scope that implements neither is a
+ * plain element with a row template inside it, which is why there is no
+ * repeater widget.
  *
- * One protocol name, not a table of tag names — the hub tests for the method,
- * never for the element.
+ * They are methods on an element the hub does not own, so they carry the
+ * `lb` prefix that Loadbare reserves for exactly that — see
+ * docs/reference/custom-elements.md.
  */
-export interface HubRowHost {
-    acceptRows(result: Projection): void;
+export interface ListHost {
+    /**
+     * Where a row belongs, called with the row detached on its first
+     * appearance. Without it a row lands immediately before the template, so
+     * rows accumulate in the order they arrive.
+     */
+    lbPlaceRow?(el: Element, row: Row, template: HTMLTemplateElement): void;
+    /** Called once after a whole result has landed, for derived scaffolding. */
+    lbRowsLanded?(): void;
 }
 //# sourceMappingURL=lb-types.d.ts.map

package/dist/core/lb-types.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"lb-types.d.ts","sourceRoot":"","sources":["../../core/lb-types.ts"],"names":[],"mappings":"AAEA,oEAAoE;AACpE,MAAM,MAAM,UAAU,GAClB;IACE,EAAE,EAAE,aAAa,CAAC;IAClB,KAAK,EAAE,MAAM,CAAC;IACd,GAAG,EAAE,MAAM,CAAC;IACZ,IAAI,EAAE,MAAM,CAAC;IACb,KAAK,EAAE,MAAM,CAAC;CACf,GACD;IAAE,EAAE,EAAE,cAAc,CAAC;IAAC,KAAK,EAAE,MAAM,CAAC;IAAC,MAAM,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAA;CAAE,GACrE;IACE,EAAE,EAAE,cAAc,CAAC;IACnB,KAAK,EAAE,MAAM,CAAC;IACd,GAAG,EAAE,MAAM,CAAC;IACZ,MAAM,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;CAChC,GACD;IAAE,EAAE,EAAE,cAAc,CAAC;IAAC,KAAK,EAAE,MAAM,CAAC;IAAC,GAAG,EAAE,MAAM,CAAA;CAAE;AACpD;;;;;;;;;;;;GAYG;GACD;IACE,EAAE,EAAE,QAAQ,CAAC;IACb,IAAI,EAAE,MAAM,CAAC;IACb,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,GAAG,CAAC,EAAE,MAAM,CAAC;IACb,IAAI,CAAC,EAAE,MAAM,CAAC;IACd,KAAK,CAAC,EAAE,MAAM,CAAC;CAChB,CAAC;AAEN,gFAAgF;AAChF,MAAM,MAAM,WAAW,GAAG,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;AAEjD;;;;;;;;;;;;;;GAcG;AACH,MAAM,MAAM,UAAU,GAClB;IAAE,EAAE,EAAE,MAAM,CAAC;IAAC,IAAI,EAAE,WAAW,EAAE,CAAA;CAAE,GACnC;IAAE,EAAE,EAAE,OAAO,CAAC;IAAC,IAAI,CAAC,EAAE,WAAW,EAAE,CAAC;IAAC,IAAI,CAAC,EAAE,MAAM,EAAE,CAAA;CAAE,CAAC;AAE3D,sEAAsE;AACtE,MAAM,MAAM,SAAS,GAAG,WAAW,GAAG,UAAU,CAAC;AAEjD,wBAAgB,YAAY,CAAC,MAAM,EAAE,SAAS,GAAG,MAAM,IAAI,UAAU,CAGpE;AAED;;;;GAIG;AACH,MAAM,MAAM,OAAO,GAAG,MAAM,CAAC,MAAM,EAAE,SAAS,CAAC,CAAC;AAEhD;;;;;;;GAOG;AACH,MAAM,WAAW,UAAU;IACzB,UAAU,CAAC,MAAM,EAAE,UAAU,GAAG,IAAI,CAAC;CACtC"}
+{"version":3,"file":"lb-types.d.ts","sourceRoot":"","sources":["../../core/lb-types.ts"],"names":[],"mappings":"AAIA,OAAO,EACL,kBAAkB,EAClB,iBAAiB,EACjB,iBAAiB,EACjB,iBAAiB,EAElB,MAAM,gBAAgB,CAAC;AAExB;;;;;;;GAOG;AACH,MAAM,MAAM,GAAG,GAAG,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC;AAE1C;;;;;;;;;GASG;AACH,MAAM,WAAW,KAAK;IACpB,IAAI,CAAC,EAAE,GAAG,EAAE,CAAC;IACb,IAAI,CAAC,EAAE,OAAO,EAAE,CAAC;CAClB;AAED;;;;;;;;;GASG;AACH,MAAM,MAAM,UAAU,GAAG,GAAG,EAAE,GAAG,KAAK,CAAC;AAEvC,wBAAgB,OAAO,CAAC,MAAM,EAAE,UAAU,GAAG,MAAM,IAAI,KAAK,CAE3D;AAED;;;GAGG;AACH,MAAM,MAAM,SAAS,GAAG,GAAG,GAAG,UAAU,CAAC;AAEzC;;;;;;GAMG;AACH,MAAM,MAAM,OAAO,GAAG,MAAM,CAAC,MAAM,EAAE,SAAS,CAAC,CAAC;AAEhD;;;;;;;GAOG;AACH,MAAM,MAAM,WAAW,GACnB;IACE,MAAM,EAAE,OAAO,iBAAiB,CAAC;IACjC,IAAI,EAAE,MAAM,CAAC;IACb,MAAM,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;CAChC,GACD;IAAE,MAAM,EAAE,OAAO,iBAAiB,CAAC;IAAC,IAAI,EAAE,MAAM,CAAC;IAAC,GAAG,EAAE,MAAM,CAAA;CAAE,GAC/D;IACE,MAAM,EAAE,OAAO,iBAAiB,CAAC;IACjC,IAAI,EAAE,MAAM,CAAC;IACb,GAAG,EAAE,MAAM,CAAC;IACZ,MAAM,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;CAChC,GACD;IACE,MAAM,EAAE,OAAO,kBAAkB,CAAC;IAClC,IAAI,EAAE,MAAM,CAAC;IACb,GAAG,EAAE,MAAM,CAAC;IACZ,IAAI,EAAE,MAAM,CAAC;IACb,KAAK,EAAE,MAAM,CAAC;CACf,CAAC;AAEN;;;;;;;;;;;;;;GAcG;AACH,MAAM,WAAW,cAAc;IAC7B,MAAM,EAAE,MAAM,CAAC;IACf,IAAI,CAAC,EAAE,MAAM,CAAC;IACd,GAAG,CAAC,EAAE,MAAM,CAAC;IACb,GAAG,CAAC,EAAE,MAAM,CAAC;IACb,IAAI,CAAC,EAAE,MAAM,CAAC;IACd,KAAK,CAAC,EAAE,MAAM,CAAC;CAChB;AAED,MAAM,MAAM,UAAU,GAAG,WAAW,GAAG,cAAc,CAAC;AAEtD;;;GAGG;AACH,wBAAgB,WAAW,CAAC,OAAO,EAAE,UAAU,GAAG,OAAO,IAAI,WAAW,CAEvE;AAED;;;;;;;;;;;GAWG;AACH,MAAM,WAAW,QAAQ;IACvB;;;;OAIG;IACH,UAAU,CAAC,CAAC,EAAE,EAAE,OAAO,EAAE,GAAG,EAAE,GAAG,EAAE,QAAQ,EAAE,mBAAmB,GAAG,IAAI,CAAC;IAExE,4EAA4E;IAC5E,YAAY,CAAC,IAAI,IAAI,CAAC;CACvB"}

package/dist/core/lb-types.js

@@ -1,5 +1,13 @@
+/// <reference lib="dom" />
 // The wire vocabulary. Shared by browser and server.
-export function isProjection(result) {
-    const op = result.op;
-    return op === "rows" || op === "patch";
+import { LB_RESERVED_PREFIX, } from "./lb-constants";
+export function isPatch(result) {
+    return !Array.isArray(result);
+}
+/**
+ * The reserved prefix is the whole of the discriminant. Nothing else tells
+ * an operation from a declared action, on the wire or anywhere else.
+ */
+export function isOperation(request) {
+    return request.action.startsWith(LB_RESERVED_PREFIX);
 }

package/dist/hub/lb-apply.d.ts

@@ -1,13 +1,27 @@
-import { type QueryResult, type HubData } from "../core/lb-types";
+import { type HubData, type ListResult, type Row } from "../core/lb-types";
 /**
- * Fill one scope from one tuple.
+ * Fill one scope from one row.
  *
  * The root counts as a cell if it carries one. A `<tr>` holds its cells in
  * `<td>` children, but `<option>`'s content model is text, so an option row
  * has to be the cell it displays. Requiring a wrapper there would require an
  * element HTML does not allow.
  */
-export declare function applyTuple(root: Element, cells: QueryResult): void;
-/** Land a whole response. Every query result arrives through here. */
+export declare function applyRow(root: Element, row: Row): void;
+/**
+ * Land a list result in a list scope.
+ *
+ * An array is the whole set, so it decides membership and order: every row is
+ * placed in the order given, and a row whose key did not arrive is gone. A
+ * patch disturbs only what it names — a row it did not mention keeps its
+ * contents and its position.
+ *
+ * A widget that carries `lbPlaceRow` decides where a row goes, because only
+ * it knows whether it sorts or groups. Without it a row lands immediately
+ * before the template, so rows accumulate in the order they arrive and the
+ * template stays put as the insertion marker.
+ */
+export declare function applyList(scope: Element, result: ListResult): void;
+/** Land a whole response. Every result arrives through here. */
 export declare function applyData(root: ParentNode, data: HubData): void;
 //# sourceMappingURL=lb-apply.d.ts.map

package/dist/hub/lb-apply.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"lb-apply.d.ts","sourceRoot":"","sources":["../../hub/lb-apply.ts"],"names":[],"mappings":"AAcA,OAAO,EAGL,KAAK,WAAW,EAChB,KAAK,OAAO,EAEb,MAAM,kBAAkB,CAAC;AAkB1B;;;;;;;GAOG;AACH,wBAAgB,UAAU,CAAC,IAAI,EAAE,OAAO,EAAE,KAAK,EAAE,WAAW,GAAG,IAAI,CAMlE;AAmBD,sEAAsE;AACtE,wBAAgB,SAAS,CAAC,IAAI,EAAE,UAAU,EAAE,IAAI,EAAE,OAAO,GAAG,IAAI,CAY/D"}
+{"version":3,"file":"lb-apply.d.ts","sourceRoot":"","sources":["../../hub/lb-apply.ts"],"names":[],"mappings":"AA4BA,OAAO,EAEL,KAAK,OAAO,EAEZ,KAAK,UAAU,EACf,KAAK,GAAG,EACT,MAAM,kBAAkB,CAAC;AAiD1B;;;;;;;GAOG;AACH,wBAAgB,QAAQ,CAAC,IAAI,EAAE,OAAO,EAAE,GAAG,EAAE,GAAG,GAAG,IAAI,CAMtD;AAoCD;;;;;;;;;;;;GAYG;AACH,wBAAgB,SAAS,CAAC,KAAK,EAAE,OAAO,EAAE,MAAM,EAAE,UAAU,GAAG,IAAI,CAgElE;AAED,gEAAgE;AAChE,wBAAgB,SAAS,CAAC,IAAI,EAAE,UAAU,EAAE,IAAI,EAAE,OAAO,GAAG,IAAI,CAkC/D"}