@warlock.js/notifications 4.15.0 → 5.0.0

package/esm/seal/src/validators/union-validator.mjs

@@ -0,0 +1,66 @@
+import { getRuleOptions } from "../standard-schema/json-schema.mjs";
+import { BaseValidator } from "./base-validator.mjs";
+import { unionRule } from "../rules/core/union.mjs";
+import "../rules/index.mjs";
+
+//#region ../seal/src/validators/union-validator.ts
+/**
+* Union validator class - validates value against multiple validator types
+*
+* Tries each validator in order until one passes. If a validator's matchesType()
+* returns false, it's skipped for optimization. First validator that both matches
+* the type and passes validation wins.
+*
+* @example
+* ```ts
+* // Accept email or username
+* const identifier = v.union([
+*   v.string().email(),
+*   v.string().alphanumeric().min(3).max(20)
+* ]);
+*
+* // Accept different types
+* const customValue = v.union([
+*   v.string().required(),
+*   v.number().required(),
+*   v.boolean().required(),
+*   v.file().required()
+* ]);
+* ```
+*/
+var UnionValidator = class extends BaseValidator {
+	/**
+	* Set the validators to try for union validation
+	*
+	* @param validators - Array of validators to try
+	* @param errorMessage - Optional custom error message if all validators fail
+	* @returns This validator for chaining
+	*
+	* @example
+	* ```ts
+	* new UnionValidator()
+	*   .union([v.string(), v.number()], 'Must be string or number');
+	* ```
+	*/
+	union(validators, errorMessage) {
+		return this.addRule(unionRule, errorMessage, { validators });
+	}
+	/**
+	* @inheritdoc
+	*
+	* Generates `{ oneOf: [...] }` by mapping each sub-validator to its JSON Schema.
+	*
+	* @example
+	* ```ts
+	* v.union([v.string(), v.number()]).toJsonSchema("draft-2020-12")
+	* // → { oneOf: [{ type: "string" }, { type: "number" }] }
+	* ```
+	*/
+	toJsonSchema(target = "draft-2020-12") {
+		return { oneOf: (getRuleOptions(this.rules, "union")?.validators ?? []).map((v) => v.toJsonSchema(target)) };
+	}
+};
+
+//#endregion
+export { UnionValidator };
+//# sourceMappingURL=union-validator.mjs.map

package/esm/seal/src/validators/union-validator.mjs.map

@@ -0,0 +1 @@
+{"version":3,"file":"union-validator.mjs","names":[],"sources":["../../../../../../../../../seal/src/validators/union-validator.ts"],"sourcesContent":["import { unionRule } from \"../rules\";\r\nimport { BaseValidator } from \"./base-validator\";\r\nimport { getRuleOptions } from \"../standard-schema/json-schema\";\r\nimport type { JsonSchemaResult, JsonSchemaTarget } from \"../standard-schema/json-schema\";\r\n\r\n/**\r\n * Union validator class - validates value against multiple validator types\r\n *\r\n * Tries each validator in order until one passes. If a validator's matchesType()\r\n * returns false, it's skipped for optimization. First validator that both matches\r\n * the type and passes validation wins.\r\n *\r\n * @example\r\n * ```ts\r\n * // Accept email or username\r\n * const identifier = v.union([\r\n *   v.string().email(),\r\n *   v.string().alphanumeric().min(3).max(20)\r\n * ]);\r\n *\r\n * // Accept different types\r\n * const customValue = v.union([\r\n *   v.string().required(),\r\n *   v.number().required(),\r\n *   v.boolean().required(),\r\n *   v.file().required()\r\n * ]);\r\n * ```\r\n */\r\nexport class UnionValidator extends BaseValidator {\r\n  /**\r\n   * Set the validators to try for union validation\r\n   *\r\n   * @param validators - Array of validators to try\r\n   * @param errorMessage - Optional custom error message if all validators fail\r\n   * @returns This validator for chaining\r\n   *\r\n   * @example\r\n   * ```ts\r\n   * new UnionValidator()\r\n   *   .union([v.string(), v.number()], 'Must be string or number');\r\n   * ```\r\n   */\r\n  public union(validators: BaseValidator[], errorMessage?: string) {\r\n    return this.addRule(unionRule, errorMessage, { validators });\r\n  }\r\n\r\n  /**\r\n   * @inheritdoc\r\n   *\r\n   * Generates `{ oneOf: [...] }` by mapping each sub-validator to its JSON Schema.\r\n   *\r\n   * @example\r\n   * ```ts\r\n   * v.union([v.string(), v.number()]).toJsonSchema(\"draft-2020-12\")\r\n   * // → { oneOf: [{ type: \"string\" }, { type: \"number\" }] }\r\n   * ```\r\n   */\r\n  public override toJsonSchema(target: JsonSchemaTarget = \"draft-2020-12\"): JsonSchemaResult {\r\n    const opts = getRuleOptions(this.rules, \"union\");\r\n    const validators = (opts?.validators ?? []) as BaseValidator[];\r\n\r\n    return {\r\n      oneOf: validators.map(v => v.toJsonSchema(target)),\r\n    };\r\n  }\r\n}\r\n"],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AA6BA,IAAa,iBAAb,cAAoC,cAAc;;;;;;;;;;;;;;CAchD,AAAO,MAAM,YAA6B,cAAuB;EAC/D,OAAO,KAAK,QAAQ,WAAW,cAAc,EAAE,WAAW,CAAC;CAC7D;;;;;;;;;;;;CAaA,AAAgB,aAAa,SAA2B,iBAAmC;EAIzF,OAAO,EACL,QAJW,eAAe,KAAK,OAAO,OACjB,CAAC,EAAE,cAAc,CAAC,EAGtB,CAAC,KAAI,MAAK,EAAE,aAAa,MAAM,CAAC,EACnD;CACF;AACF"}

package/llms-full.txt

@@ -697,7 +697,7 @@ const channelName = await chooseChannelForUser(user);
 await notify.channel(channelName).send(user, payload);
 ```
 
-This is the only path with `unknown`-typed payloads — prefer the literal `notify.<channel>` when you can.
+This is the only path with `unknown`-typed payloads — prefer the literal `notify.<channel>` when you can. `to` is still what decides the recipient: even for the `database` channel, a `recipientId`-shaped key on `payload` (or the model's physical recipient column name) is stripped before the row is built, so an untyped payload assembled from request JSON can't redirect the write to another recipient — see [`use-in-app/SKILL.md`](../use-in-app/SKILL.md#createfor-write-side--no-idor-either-since-4150).
 
 ## Opt into preference/rate-limit gating
 
@@ -835,6 +835,10 @@ class BaseNotificationsRepository extends RepositoryManager {
 }
 ```
 
+### `createFor` write side — no IDOR either (since 4.15.0)
+
+`recipientId` is always the trusted argument, applied **after** the payload — `createFor`/`createManyFor` strip server-owned keys (`id`, `recipientId`, `tenant`, `readAt`, `isRead`, and their resolved `columnMap` physical column names) off `input` before merging. Before this, a caller passing an untyped payload straight through (request JSON, a channel's `send` args) could smuggle its own `recipientId` — or the raw physical column name — and write the notification into someone else's inbox. `type` / `title` / `body` / `payload` / `idempotencyKey` are untouched; you don't need to sanitize `input` yourself.
+
 ### `columnMap` — map logical roles → your columns
 
 ```ts

package/package.json

@@ -2,10 +2,10 @@
   "name": "@warlock.js/notifications",
   "description": "Multi-channel notifications for Warlock.js — define once, fire anywhere; mail / in-app database / pluggable custom channels with preferences, rate limits, and idempotency.",
   "dependencies": {
-    "@warlock.js/cache": "4.15.0",
-    "@warlock.js/cascade": "4.15.0",
-    "@warlock.js/core": "4.15.0",
-    "@warlock.js/logger": "4.15.0"
+    "@warlock.js/cache": "5.0.0",
+    "@warlock.js/cascade": "5.0.0",
+    "@warlock.js/core": "5.0.0",
+    "@warlock.js/logger": "5.0.0"
   },
   "optionalDependencies": {
     "@warlock.js/herald": "*"
@@ -24,7 +24,7 @@
   ],
   "author": "hassanzohdy",
   "license": "MIT",
-  "version": "4.15.0",
+  "version": "5.0.0",
   "main": "./cjs/index.cjs",
   "module": "./esm/index.mjs",
   "types": "./esm/index.d.mts",

package/skills/send-ad-hoc/SKILL.md

@@ -46,7 +46,7 @@ const channelName = await chooseChannelForUser(user);
 await notify.channel(channelName).send(user, payload);
 ```
 
-This is the only path with `unknown`-typed payloads — prefer the literal `notify.<channel>` when you can.
+This is the only path with `unknown`-typed payloads — prefer the literal `notify.<channel>` when you can. `to` is still what decides the recipient: even for the `database` channel, a `recipientId`-shaped key on `payload` (or the model's physical recipient column name) is stripped before the row is built, so an untyped payload assembled from request JSON can't redirect the write to another recipient — see [`use-in-app/SKILL.md`](../use-in-app/SKILL.md#createfor-write-side--no-idor-either-since-4150).
 
 ## Opt into preference/rate-limit gating
 

package/skills/use-in-app/SKILL.md

@@ -85,6 +85,10 @@ class BaseNotificationsRepository extends RepositoryManager {
 }
 ```
 
+### `createFor` write side — no IDOR either (since 4.15.0)
+
+`recipientId` is always the trusted argument, applied **after** the payload — `createFor`/`createManyFor` strip server-owned keys (`id`, `recipientId`, `tenant`, `readAt`, `isRead`, and their resolved `columnMap` physical column names) off `input` before merging. Before this, a caller passing an untyped payload straight through (request JSON, a channel's `send` args) could smuggle its own `recipientId` — or the raw physical column name — and write the notification into someone else's inbox. `type` / `title` / `body` / `payload` / `idempotencyKey` are untouched; you don't need to sanitize `input` yourself.
+
 ### `columnMap` — map logical roles → your columns
 
 ```ts