zitejs 0.9.106 → 0.9.107

package/dist/cjs/runtime/index.d.ts

@@ -99,15 +99,37 @@ export interface TableFindAllOptions<T = Record<string, unknown>> {
     filter?: unknown;
     fields?: Array<FieldSelector<T>>;
 }
+/**
+ * Both write results carry the record twice — flat, and again under `fields`.
+ *
+ * That is not a quirk of the type. Both dispatchers build it deliberately, with
+ * the same code and the same comment ("Return both flat fields and nested
+ * fields for backwards compatibility"):
+ * `cloudflare-lambda/src/integrations/databases.ts` and
+ * `workflow-runner/src/sdk/databases.ts`.
+ *
+ * The types said otherwise, each in a different direction — `BulkCreateResult`
+ * declared only the flat form, `UpdateResult` only the nested one. So a 1.0 app
+ * reading `created.fields.token`, which is what 1.0's SDK typed, stopped
+ * compiling after migrating even though the value was sitting right there at
+ * runtime. DSA Employee Portal migrated "successfully" and then would not build.
+ *
+ * Declaring both is the whole fix: nothing about the running code changes, and
+ * no app source has to be rewritten to match a type narrower than what the
+ * runtime actually returns.
+ */
 export interface BulkCreateResult<T> {
     /** Absent when `records: []` was passed — the dispatch short-circuits before setting it. */
     success?: boolean;
-    records: T[];
+    records: Array<T & {
+        fields: T;
+    }>;
 }
-export interface UpdateResult<T> {
+/** A type alias, not an interface: an interface cannot extend a generic `Partial<T>`. */
+export type UpdateResult<T> = Partial<T> & {
     id: string;
     fields: Partial<T>;
-}
+};
 export interface DeleteResult {
     success: true;
     id: string;

package/dist/cjs/runtime/writeResultTypes.test-d.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/cjs/runtime/writeResultTypes.test-d.js

@@ -0,0 +1,29 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+const vitest_1 = require("vitest");
+(0, vitest_1.describe)("BulkCreateResult", () => {
+    // The 1.0 spelling. This is the one that regressed.
+    (0, vitest_1.it)("reads through .fields", () => {
+        (0, vitest_1.expectTypeOf)().toEqualTypeOf();
+        (0, vitest_1.expectTypeOf)().toEqualTypeOf();
+    });
+    // The 2.0 spelling, which must keep working — apps written since migration
+    // use it, so this is not a case of swapping one shape for the other.
+    (0, vitest_1.it)("reads flat", () => {
+        (0, vitest_1.expectTypeOf)().toEqualTypeOf();
+        (0, vitest_1.expectTypeOf)().toEqualTypeOf();
+    });
+    (0, vitest_1.it)("keeps success optional", () => {
+        (0, vitest_1.expectTypeOf)().toEqualTypeOf();
+    });
+});
+(0, vitest_1.describe)("UpdateResult", () => {
+    // The mirror image: `update` returned `{ ...transformed, fields: transformed }`
+    // but the type declared only `id` and `fields`, so reading a column straight
+    // off an update result failed to compile.
+    (0, vitest_1.it)("reads flat and through .fields", () => {
+        (0, vitest_1.expectTypeOf)().toEqualTypeOf();
+        (0, vitest_1.expectTypeOf)().toEqualTypeOf();
+        (0, vitest_1.expectTypeOf)().toEqualTypeOf();
+    });
+});

package/dist/esm/runtime/index.d.ts

@@ -99,15 +99,37 @@ export interface TableFindAllOptions<T = Record<string, unknown>> {
     filter?: unknown;
     fields?: Array<FieldSelector<T>>;
 }
+/**
+ * Both write results carry the record twice — flat, and again under `fields`.
+ *
+ * That is not a quirk of the type. Both dispatchers build it deliberately, with
+ * the same code and the same comment ("Return both flat fields and nested
+ * fields for backwards compatibility"):
+ * `cloudflare-lambda/src/integrations/databases.ts` and
+ * `workflow-runner/src/sdk/databases.ts`.
+ *
+ * The types said otherwise, each in a different direction — `BulkCreateResult`
+ * declared only the flat form, `UpdateResult` only the nested one. So a 1.0 app
+ * reading `created.fields.token`, which is what 1.0's SDK typed, stopped
+ * compiling after migrating even though the value was sitting right there at
+ * runtime. DSA Employee Portal migrated "successfully" and then would not build.
+ *
+ * Declaring both is the whole fix: nothing about the running code changes, and
+ * no app source has to be rewritten to match a type narrower than what the
+ * runtime actually returns.
+ */
 export interface BulkCreateResult<T> {
     /** Absent when `records: []` was passed — the dispatch short-circuits before setting it. */
     success?: boolean;
-    records: T[];
+    records: Array<T & {
+        fields: T;
+    }>;
 }
-export interface UpdateResult<T> {
+/** A type alias, not an interface: an interface cannot extend a generic `Partial<T>`. */
+export type UpdateResult<T> = Partial<T> & {
     id: string;
     fields: Partial<T>;
-}
+};
 export interface DeleteResult {
     success: true;
     id: string;

package/dist/esm/runtime/writeResultTypes.test-d.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/esm/runtime/writeResultTypes.test-d.js

@@ -0,0 +1,27 @@
+import { describe, it, expectTypeOf } from "vitest";
+describe("BulkCreateResult", () => {
+    // The 1.0 spelling. This is the one that regressed.
+    it("reads through .fields", () => {
+        expectTypeOf().toEqualTypeOf();
+        expectTypeOf().toEqualTypeOf();
+    });
+    // The 2.0 spelling, which must keep working — apps written since migration
+    // use it, so this is not a case of swapping one shape for the other.
+    it("reads flat", () => {
+        expectTypeOf().toEqualTypeOf();
+        expectTypeOf().toEqualTypeOf();
+    });
+    it("keeps success optional", () => {
+        expectTypeOf().toEqualTypeOf();
+    });
+});
+describe("UpdateResult", () => {
+    // The mirror image: `update` returned `{ ...transformed, fields: transformed }`
+    // but the type declared only `id` and `fields`, so reading a column straight
+    // off an update result failed to compile.
+    it("reads flat and through .fields", () => {
+        expectTypeOf().toEqualTypeOf();
+        expectTypeOf().toEqualTypeOf();
+        expectTypeOf().toEqualTypeOf();
+    });
+});

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "zitejs",
-  "version": "0.9.106",
+  "version": "0.9.107",
   "description": "The Zite framework — build apps on Zite Database",
   "type": "module",
   "main": "./dist/cjs/index.js",