@wildo-ai/saas-models 1.1.5 → 1.1.6

package/dist/esm/resources/resources.shared.schemas.js

@@ -1053,27 +1053,21 @@ export const ResourceRelationshipSchema = z.object({
 /**
  * Default response patterns for resource operations based on best practices
  */
+/*
+ * Both delete envelopes are exactly what `composeDefaultOperationResponse` builds from the
+ * repository's deleted id(s). They carried an optional `deletedAt` too, which no delete path ever
+ * set, so the API reference advertised a timestamp no response contained. It was removed rather than
+ * described (#1625); a delete that should report when it happened must set it before declaring it.
+ */
 export const DefaultDeleteResponseSchema = z.object({
-    id: z.string(),
-    deletedAt: z.date().optional()
+    id: z.string().describe("The id of the record that was deleted."),
 });
 export const DefaultBulkDeleteResponseSchema = z.object({
-    deletedIds: z.array(z.string()),
-    deletedCount: z.number(),
-    deletedAt: z.date().optional()
-});
-export const DefaultUpdateManyResponseSchema = z.object({
-    updatedCount: z.number(),
-    updatedIds: z.array(z.string()).optional(),
-    updatedAt: z.date().optional()
+    deletedIds: z.array(z.string()).describe("The ids of the records that were deleted. Empty when nothing matched."),
+    deletedCount: z.number().describe("How many records were deleted."),
 });
 export const DefaultCountResponseSchema = z.object({
-    count: z.number().int().min(0),
-});
-export const DefaultCreateManyResponseSchema = (itemSchema) => z.object({
-    items: z.array(itemSchema),
-    createdCount: z.number(),
-    createdAt: z.date().optional()
+    count: z.number().int().min(0).describe("How many records match the request's filters."),
 });
 /**
  * Generic success envelope for explicit custom action-style operations.
@@ -1113,10 +1107,20 @@ export function getDefaultResponseSchemaForOperation(operation, mainSchema) {
             return DefaultDeleteResponseSchema;
         case CoreResourceOperation.DELETE_MANY:
             return DefaultBulkDeleteResponseSchema;
+        // The ROW schema, validated per item: `updateMany` returns the updated rows and
+        // `composeDefaultOperationResponse` passes them through, the same array a bulk UPDATE twin
+        // answers. There used to be a `DefaultUpdateManyResponseSchema` (`{ updatedCount, updatedIds?,
+        // updatedAt? }`) here, which nothing produced: a response that satisfied the operation would
+        // have failed its own validation, and the API reference published the envelope — whose
+        // `updatedAt` even picked up the resource's own field description by name (#1793).
         case CoreResourceOperation.UPDATE_MANY:
-            return DefaultUpdateManyResponseSchema;
+            return mainSchema;
+        // The ROW schema, for the same reason as UPDATE_MANY above (#1873). The repository returns the created rows
+        // and the serializer validates each against this schema; the `{ items, createdCount, createdAt? }` envelope
+        // that stood here was produced by nothing, so every created row failed its parse after the rows were written,
+        // and the API reference published an envelope no response carried.
         case CoreResourceOperation.CREATE_MANY:
-            return DefaultCreateManyResponseSchema(mainSchema);
+            return mainSchema;
         case CoreResourceOperation.LIST:
             // List operations should use pagination wrapper - handled separately
             return mainSchema;
@@ -1331,8 +1335,8 @@ export var ResourceIdFormat;
      * The synthesized id of an `INTROSPECTION`-backed resource: the key of a row DERIVED from the
      * application's own structure, never minted and never stored.
      *
-     * A distinct member from {@link HTTP_API_SYNTHESIZED} even though both admit the same charset,
-     * because they answer different questions and will diverge: an HTTP-API id encodes a REMOTE
+     * A distinct member from {@link HTTP_API_SYNTHESIZED}, because they answer different questions and have
+     * diverged: this one also admits the element-ref separators `:` `/` `[` `]` (#2048). An HTTP-API id encodes a REMOTE
      * entity's key through a codec that can round-trip it, while an introspected id is whatever the
      * companion behavior's projection already calls the row — a module name, a composed structural
      * key. Merging them would put one name on two origins, and the next reader could not tell which