@softr/sdk 0.0.56-alpha.2 → 0.0.56-alpha.3

package/dist/codegen/softr-env.js

@@ -77,8 +77,8 @@ type LinkedRecordInput = { id: string };
 
 type WorkspaceUser = {
   id: string;
-  name: string;
-  email: EmailAddress;
+  name: string | null;
+  email: EmailAddress | null;
   avatarUrl: string | null;
 };
 

package/dist/default-error-overlay.d.ts

@@ -2,7 +2,7 @@ import * as react1 from "react";
 
 //#region src/default-error-overlay.d.ts
 type Props = {
-  error: Error;
+  error: unknown;
   reset?: () => void;
 };
 declare function DefaultErrorOverlay({

package/dist/default-error-overlay.js

@@ -88,9 +88,9 @@ function DevView({ error, reset }) {
 				] }),
 				/* @__PURE__ */ jsx("pre", {
 					style: s.message,
-					children: error.message
+					children: error instanceof Error ? error.message : String(error)
 				}),
-				error.stack && /* @__PURE__ */ jsx(StackTrace, { stack: error.stack }),
+				error instanceof Error && error.stack && /* @__PURE__ */ jsx(StackTrace, { stack: error.stack }),
 				/* @__PURE__ */ jsx("div", { children: /* @__PURE__ */ jsx(RetryButton, { onClick: reset }) })
 			]
 		})

package/dist/package.js

@@ -1,5 +1,5 @@
 //#region package.json
-var version = "0.0.56-alpha.2";
+var version = "0.0.56-alpha.3";
 
 //#endregion
 export { version };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@softr/sdk",
-  "version": "0.0.56-alpha.2",
+  "version": "0.0.56-alpha.3",
   "type": "module",
   "exports": {
     ".": { "types": "./dist/index.d.ts", "import": "./dist/index.js" },

package/skills/softr-sdk/record-queries/SKILL.md

@@ -183,7 +183,7 @@ A read the datasource turns down throws rather than coming back empty, and it th
 
 ## Typing
 
-Queries you write are type safe and a type error is shown when there's a mistake. For an in depth reference on what fields every datasource has, read `docs/datasources/README.md` first — it lists every registered datasource with a link to its file. Follow those links to get field ids, types, and constraints. Do not guess filenames from table names.
+Queries you write are type safe and a type error is shown when there's a mistake. The records a read returns are typed the same way, so never validate them again with a zod schema of your own. A schema guesses each field's shape, and one value it misses, such as a person with no email, throws for the whole read and the page stops loading. Show each field with a fallback instead: `record.fields.owner?.name ?? '—'`. For an in depth reference on what fields every datasource has, read `docs/datasources/README.md` first — it lists every registered datasource with a link to its file. Follow those links to get field ids, types, and constraints. Do not guess filenames from table names.
 
 ## References
 

package/skills/softr-sdk/record-queries/references/field-types.md

@@ -27,7 +27,7 @@ CHECKBOX: boolean
 SELECT: { id: string; label: string | null }          // generated with literal id and label unions
 LINKED_RECORD: { id: string; label: string | null }   // label is the linked record's primary field
 DATE_RANGE: { from: string; to: string }
-USER: { id: string; name: string; email: string; avatarUrl: string | null }
+USER: { id: string; name: string | null; email: string | null; avatarUrl: string | null }
 ATTACHMENT: {
   id: string | null
   filename: string | null
@@ -56,6 +56,10 @@ Every scalar above is `| null` on the record unless the field allows multiple en
 <td>{record.fields.status}</td>
 ```
 
+**CREATED_BY and UPDATED_BY** are the person's name as a plain string, not a `USER` object.
+
+**USER** can lack a name or an email: show `owner?.name ?? owner?.email ?? '—'`, never assume either is there.
+
 **DURATION** is milliseconds, whatever format the field displays in: `3600000` is one hour.
 
 **DATETIME at date precision** is generated as a `DATE` field and holds `'2026-03-14'`, not a timestamp.