@standards/schema 0.0.0-stage → 1.0.0-alpha.382

package/dist/date-CxqDOhA0.d.mts

@@ -0,0 +1,24 @@
+
+import { u as DateAttribute } from "./attributes-aTeqx6cK.mjs";
+import { r as ValidationMessages } from "./index-3HZjBOpj.mjs";
+import { z as z$1 } from "zod";
+//#region src/validation/primitives/date.d.ts
+/**
+ * Create a Zod schema for a date attribute.
+ *
+ * Non-range attributes validate a single coercible date bounded by
+ * `minDate`/`maxDate`. Range attributes (`.endDate()`) validate a
+ * `{ start, end }` object — `end` may be null, and when present must be
+ * on or after `start`. Plain strings normalize to `{ start, end: null }`
+ * (mirroring `normalizeDateValue`) so legacy values written before
+ * `endDate` was enabled keep validating.
+ *
+ * Coercion to `Date` only backs correctness/bounds checks against a
+ * throwaway copy — the schema never mutates the value itself, so
+ * `result.data` is always the original input (ISO string, or `{ start, end }`
+ * of ISO strings), never a coerced `Date`. This keeps the stored shape intact
+ * for callers that persist `validator.safeParse(value).data`.
+ */
+declare function createDateValidator(attr: DateAttribute, messages?: ValidationMessages): z$1.ZodTypeAny;
+//#endregion
+export { createDateValidator as t };

package/dist/date-D007KyTI.d.ts

@@ -0,0 +1,24 @@
+
+import { u as DateAttribute } from "./attributes-kAhQzg8-.js";
+import { r as ValidationMessages } from "./index-DLO8JpnY.js";
+import { z as z$1 } from "zod";
+//#region src/validation/primitives/date.d.ts
+/**
+ * Create a Zod schema for a date attribute.
+ *
+ * Non-range attributes validate a single coercible date bounded by
+ * `minDate`/`maxDate`. Range attributes (`.endDate()`) validate a
+ * `{ start, end }` object — `end` may be null, and when present must be
+ * on or after `start`. Plain strings normalize to `{ start, end: null }`
+ * (mirroring `normalizeDateValue`) so legacy values written before
+ * `endDate` was enabled keep validating.
+ *
+ * Coercion to `Date` only backs correctness/bounds checks against a
+ * throwaway copy — the schema never mutates the value itself, so
+ * `result.data` is always the original input (ISO string, or `{ start, end }`
+ * of ISO strings), never a coerced `Date`. This keeps the stored shape intact
+ * for callers that persist `validator.safeParse(value).data`.
+ */
+declare function createDateValidator(attr: DateAttribute, messages?: ValidationMessages): z$1.ZodTypeAny;
+//#endregion
+export { createDateValidator as t };