nucleus-core-ts 0.10.74 → 0.10.76

package/dist/src/Nucleus/utils.d.ts

@@ -104,6 +104,24 @@ export declare function isSensitiveOutputKey(key: string): boolean;
 export declare function redactSensitiveOutput<T>(row: T): T;
 export declare function sanitizePayload(payload: Record<string, unknown>, columns: NucleusColumn[], opts?: {
     isFormData?: boolean;
+    /**
+     * Filled with the field names that were dropped for a reason the CALLER
+     * cannot see in the response — protected auth columns and per-column
+     * write-protection.
+     *
+     * Dropping them is right; doing it in silence is not. Measured on a
+     * pharmaceutical-leaflet install: `PATCH /users` carrying `isGod`,
+     * `password`, `emailVerified` and `loginCount` answered 200 with
+     * success:true and changed none of them. `GET /users` returns three of
+     * those four, so a read-modify-write client sends them back in good faith
+     * and is told its write succeeded.
+     *
+     * Server-managed audit columns (id, timestamps, createdBy) are NOT
+     * reported: every read-modify-write client sends those back, the handler
+     * sets them itself, and naming them every time would bury the cases that
+     * matter.
+     */
+    dropped?: string[];
 }): Record<string, unknown>;
 export interface AuditLogEntry {
     user_id: string;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "nucleus-core-ts",
-  "version": "0.10.74",
+  "version": "0.10.76",
   "description": "Production-ready, enterprise-grade TypeScript framework for building multi-tenant APIs",
   "author": "Hidayet Can Özcan <hidayetcan@gmail.com>",
   "license": "SEE LICENSE IN LICENSE",