@colixsystems/widget-sdk 0.50.0 → 0.52.0

package/README.md

@@ -51,7 +51,15 @@ See the design reference for the full architecture: [`docs/architecture/widget-m
 
 ## Status
 
-`v0.49.0` — pre-publish. The package surface (types, function names, export paths) is the v1 contract; runtime behaviour for some hooks is stubbed (each hook documents what's wired and what isn't). It is **not yet published to npm**.
+`v0.52.0` — pre-publish. The package surface (types, function names, export paths) is the v1 contract; runtime behaviour for some hooks is stubbed (each hook documents what's wired and what isn't). It is **not yet published to npm**.
+
+### What's new in 0.52.0
+
+**Lucide icon names accept any case (sc-2088).** A new `normalizeLucideIconName(name)` export maps a human-typed icon name to the PascalCase form Lucide exports its components under — `arrow-right`, `arrow_right`, `arrow right`, `arrowRight`, and `ArrowRight` all resolve to `ArrowRight`; `building-2` → `Building2`. The lucide.dev gallery and its copy button hand you kebab-case, so authors no longer have to hand-convert. The `<Icon name="…">` primitive normalizes its `name` before lookup, and the `icon` propertySchema type accepts any case. Additive — one new pure export; no existing export changed signature. `CONTRACT` is unchanged.
+
+### What's new in 0.51.0
+
+**`datastoreTemplate` tables can ship sample `rows` (sc-2070).** Each `WidgetDatastoreTemplateTable` now takes an optional `rows` array — sample data seeded into the table at install time so the widget renders with real content instead of an empty state. Each entry is an object keyed by column `name`; only the scalar/array column types are seedable (`STRING`, `TEXT`, `NUMBER`, `FLOAT`, `BOOL`, `DATE`, `STRING_ARRAY`, `INT_ARRAY`). RELATION, FILE, USER, and USER_GROUP columns are rejected at validation time (a sample row has no way to express their ids). A `null` value skips that cell; at most 25 rows per table. The "Seed data" action and every install path seed these rows in the same transaction that creates the tables. Additive — `rows` is optional and existing templates that omit it behave exactly as before.
 
 ### What's new in 0.49.0
 
@@ -102,7 +110,7 @@ See the design reference for the full architecture: [`docs/architecture/widget-m
 
 ### What's new in 0.42.0
 
-**RELATION columns hydrate with a display label (sc-1181).** Record reads now return `{ id, label }` for ONE_TO_ONE / ONE_TO_MANY and `[{ id, label }, ...]` for MANY_TO_MANY (empty array when no links) — `label` is the value of the column pointed at by the new optional `display_column_id` on `DatastoreSchemaColumn`, or, when unset, the first STRING/TEXT column on the target table. Widgets should render `record.<rel>.label` (or `record.<rel>.map(r => r.label).join(", ")` for M:M) directly; `.id` is still there for the foreign-key case. The cell-formatting helpers in the built-in `DataList`, `TabbedDatalist`, and `FieldValue` widgets already walk arrays and prefer `label` over `name` / `id` — author widgets that need the same can copy that pattern. `CONTRACT.version` is unchanged.
+**RELATION columns hydrate with a display label (sc-1181).** Record reads now return `{ id, label }` for ONE_TO_ONE / ONE_TO_MANY and `[{ id, label }, ...]` for MANY_TO_MANY (empty array when no links) — `label` is the value of the column pointed at by the new optional `display_column_id` on `DatastoreSchemaColumn`, or, when unset, the first STRING/TEXT column on the target table. Widgets should render `record.<rel>.label` (or `record.<rel>.map(r => r.label).join(", ")` for M:M) directly; `.id` is still there for the foreign-key case. The cell-formatting helpers in the built-in `DataList` and `FieldValue` widgets already walk arrays and prefer `label` over `name` / `id` — author widgets that need the same can copy that pattern. `CONTRACT.version` is unchanged.
 
 ### What's new in 0.41.0
 

package/dist/hooks.js

@@ -569,8 +569,11 @@ function toDatastoreError(err) {
  * resolves to the `{ data, meta }` list envelope VERBATIM (the client no
  * longer unwraps to a bare array), so we read `res.data` (defaulting to `[]`)
  * into component state. Author column values inside each row keep whatever
- * the author named them. We re-fetch when [table, JSON.stringify(query)]
- * changes. `refetch` re-runs the same call on demand.
+ * the author named them. `query.sort` accepts `"col:desc"` or `{ field, dir }`;
+ * `query.filter` accepts a `{ col: "op:value" }` map or a `[{ column,
+ * operator, value }]` array — the client normalises both to the wire form. We
+ * re-fetch when [table, JSON.stringify(query)] changes. `refetch` re-runs the
+ * same call on demand.
  *
  * When `table` is falsy (e.g. the user hasn't bound a `tableRef` property
  * yet), the hook resolves to { data: [], loading: false, error: null,

package/dist/icon.js

@@ -16,10 +16,11 @@
 
 import React from "react";
 import * as LucideIcons from "lucide-react-native";
+import { normalizeLucideIconName } from "./lucideIconName.js";
 
 export function Icon({ name, size, color }) {
-  const candidate =
-    typeof name === "string" && name.length > 0 ? LucideIcons[name] : null;
+  const resolved = normalizeLucideIconName(name);
+  const candidate = resolved ? LucideIcons[resolved] : null;
   const Component = candidate || LucideIcons.Square;
   const pixelSize = Number.isFinite(size) && size > 0 ? size : 24;
   return React.createElement(Component, {

package/dist/index.d.ts

@@ -168,6 +168,15 @@ export interface WidgetDatastoreTemplateTable {
    */
   publicGrant?: { canRead?: boolean; canWrite?: boolean; canDelete?: boolean };
   columns: WidgetDatastoreTemplateColumn[];
+  /**
+   * Optional sample rows seeded into the table at install time so the widget
+   * renders with real data instead of an empty state. Each key is a column
+   * `name`; only non-relation/file/user columns are seedable (RELATION, FILE,
+   * USER, USER_GROUP are rejected). `null` skips that cell. Max 25 rows.
+   */
+  rows?: Array<
+    Record<string, string | number | boolean | string[] | number[] | null>
+  >;
 }
 
 export interface WidgetDatastoreTemplate {

package/dist/index.js

@@ -70,3 +70,4 @@ export {
 } from "./primitives.js";
 export { lintSource, bannedIdentifiers } from "./linter.js";
 export { CONTRACT, isHookAllowed, requiredContextKeys } from "./contract.js";
+export { normalizeLucideIconName } from "./lucideIconName.js";

package/dist/index.native.js

@@ -66,3 +66,4 @@ export {
 } from "./primitives.native.js";
 export { lintSource, bannedIdentifiers } from "./linter.js";
 export { CONTRACT, isHookAllowed, requiredContextKeys } from "./contract.js";
+export { normalizeLucideIconName } from "./lucideIconName.js";

package/dist/lucideIconName.cjs

@@ -0,0 +1,17 @@
+// CommonJS twin of lucideIconName.js for the backend (the page service +
+// any other Node consumer require this). Keep the two in sync — same
+// algorithm, same behaviour. See lucideIconName.js for the rationale.
+"use strict";
+
+function normalizeLucideIconName(name) {
+  if (typeof name !== "string") return "";
+  const trimmed = name.trim();
+  if (trimmed === "") return "";
+  return trimmed
+    .split(/[-_\s]+/)
+    .filter(Boolean)
+    .map((segment) => segment.charAt(0).toUpperCase() + segment.slice(1))
+    .join("");
+}
+
+module.exports = { normalizeLucideIconName };

package/dist/lucideIconName.js

@@ -0,0 +1,19 @@
+// Normalize a human-typed Lucide icon name to the PascalCase form Lucide
+// exports its components under. The lucide.dev gallery shows kebab-case
+// (`arrow-right`) and its copy button hands you kebab-case, but
+// `lucide-react` / `lucide-react-native` key their components in PascalCase
+// (`ArrowRight`). This bridges the two so any of kebab / snake / spaced /
+// camel / PascalCase resolves: `arrow-right`, `arrow_right`, `arrow right`,
+// `arrowRight`, and `ArrowRight` all become `ArrowRight`; `building-2` becomes
+// `Building2`. Non-strings and blanks return "" so callers fall back to a
+// placeholder. Already-PascalCase names pass through unchanged.
+export function normalizeLucideIconName(name) {
+  if (typeof name !== "string") return "";
+  const trimmed = name.trim();
+  if (trimmed === "") return "";
+  return trimmed
+    .split(/[-_\s]+/)
+    .filter(Boolean)
+    .map((segment) => segment.charAt(0).toUpperCase() + segment.slice(1))
+    .join("");
+}