@stndrds/schema 1.0.0-alpha.294 → 1.0.0-alpha.68

package/dist/helpers-CXkVwpsl.d.ts

@@ -1,76 +0,0 @@
-import { z } from 'zod';
-import { A as Attribute } from './attributes-CNYwg_Nr.js';
-import { V as ValidationMessages, a as ValidationResult } from './types-NGEww_ln.js';
-import { O as ObjectDefinition } from './objects-DJv6WrDE.js';
-
-/**
- * Create a Zod schema for any attribute type.
- * Returns a strict validator that does NOT handle optional fields.
- * Use createFormAttributeValidator for form validation with optional support.
- *
- * @param attr - The attribute to create a validator for
- * @param messages - Custom validation messages for i18n support
- */
-declare function createAttributeValidator(attr: Attribute, messages?: ValidationMessages): z.ZodTypeAny;
-/**
- * Create a Zod schema for form validation.
- * - Normalizes empty values (empty strings, empty objects) to null for optional fields
- * - Accepts custom messages for i18n support
- *
- * Use this in UI forms where optional fields may have null/undefined values.
- *
- * @param attr - The attribute to create a validator for
- * @param messages - Custom validation messages for i18n support
- */
-declare function createFormAttributeValidator(attr: Attribute, messages?: ValidationMessages): z.ZodTypeAny;
-
-/**
- * Validate data against an attribute schema
- */
-declare function validateAttribute(attr: Attribute, value: unknown): ValidationResult;
-/**
- * Validate data against an object schema
- */
-declare function validateObject(objectDef: ObjectDefinition, data: Record<string, unknown>): ValidationResult;
-/**
- * Validate and throw if invalid.
- *
- * Throws `ValidationError` (code `SCHEMA_VALIDATION_FAILED`) on failure so HTTP
- * adapters can map it to 400. Generic `Error` would bubble up to a 500.
- */
-declare function validateObjectOrThrow(objectDef: ObjectDefinition, data: Record<string, unknown>): Record<string, unknown>;
-/**
- * Validate data in draft mode.
- * - All attributes are treated as optional (no required validation)
- * - Provided values are still validated for format/type correctness
- */
-declare function validateDraft(objectDef: ObjectDefinition, data: Record<string, unknown>): ValidationResult;
-/**
- * Validate draft data and throw if format validation fails.
- *
- * Same contract as `validateObjectOrThrow` but skips `required()` checks.
- * Throws `ValidationError` so HTTP adapters map it to 400.
- */
-declare function validateDraftOrThrow(objectDef: ObjectDefinition, data: Record<string, unknown>): Record<string, unknown>;
-/**
- * Throw a `ValidationError` when `data` contains keys that do not correspond
- * to any attribute declared on `objectDef`.
- *
- * Call this on **client-supplied input** before Zod validation so the error
- * message clearly names every offending key.  Do NOT call on merged data that
- * includes existing record values — older records may legitimately carry stale
- * keys that predate this guard (see issue #658).
- *
- * Maps to HTTP 400 via `SchemaExceptionFilter` (code SCHEMA_VALIDATION_FAILED).
- */
-declare function rejectUnknownAttributesOrThrow(objectDef: ObjectDefinition, data: Record<string, unknown>): void;
-/**
- * Get the list of required attributes that are missing values.
- */
-declare function getMissingRequiredAttributes(objectDef: ObjectDefinition, data: Record<string, unknown>): Attribute[];
-/**
- * Check if a record is complete (all required attributes have valid values).
- */
-declare function isRecordComplete(objectDef: ObjectDefinition, data: Record<string, unknown>): boolean;
-
-export { createFormAttributeValidator as a, validateDraft as b, createAttributeValidator as c, validateDraftOrThrow as d, validateObject as e, validateObjectOrThrow as f, getMissingRequiredAttributes as g, isRecordComplete as i, rejectUnknownAttributesOrThrow as r, validateAttribute as v };

package/dist/helpers-Dul_r9rJ.d.mts

@@ -1,76 +0,0 @@
-import { z } from 'zod';
-import { A as Attribute } from './attributes-CWPLbp7c.mjs';
-import { V as ValidationMessages, a as ValidationResult } from './types-CVYiFc69.mjs';
-import { O as ObjectDefinition } from './objects-CDwMSnqv.mjs';
-
-/**
- * Create a Zod schema for any attribute type.
- * Returns a strict validator that does NOT handle optional fields.
- * Use createFormAttributeValidator for form validation with optional support.
- *
- * @param attr - The attribute to create a validator for
- * @param messages - Custom validation messages for i18n support
- */
-declare function createAttributeValidator(attr: Attribute, messages?: ValidationMessages): z.ZodTypeAny;
-/**
- * Create a Zod schema for form validation.
- * - Normalizes empty values (empty strings, empty objects) to null for optional fields
- * - Accepts custom messages for i18n support
- *
- * Use this in UI forms where optional fields may have null/undefined values.
- *
- * @param attr - The attribute to create a validator for
- * @param messages - Custom validation messages for i18n support
- */
-declare function createFormAttributeValidator(attr: Attribute, messages?: ValidationMessages): z.ZodTypeAny;
-
-/**
- * Validate data against an attribute schema
- */
-declare function validateAttribute(attr: Attribute, value: unknown): ValidationResult;
-/**
- * Validate data against an object schema
- */
-declare function validateObject(objectDef: ObjectDefinition, data: Record<string, unknown>): ValidationResult;
-/**
- * Validate and throw if invalid.
- *
- * Throws `ValidationError` (code `SCHEMA_VALIDATION_FAILED`) on failure so HTTP
- * adapters can map it to 400. Generic `Error` would bubble up to a 500.
- */
-declare function validateObjectOrThrow(objectDef: ObjectDefinition, data: Record<string, unknown>): Record<string, unknown>;
-/**
- * Validate data in draft mode.
- * - All attributes are treated as optional (no required validation)
- * - Provided values are still validated for format/type correctness
- */
-declare function validateDraft(objectDef: ObjectDefinition, data: Record<string, unknown>): ValidationResult;
-/**
- * Validate draft data and throw if format validation fails.
- *
- * Same contract as `validateObjectOrThrow` but skips `required()` checks.
- * Throws `ValidationError` so HTTP adapters map it to 400.
- */
-declare function validateDraftOrThrow(objectDef: ObjectDefinition, data: Record<string, unknown>): Record<string, unknown>;
-/**
- * Throw a `ValidationError` when `data` contains keys that do not correspond
- * to any attribute declared on `objectDef`.
- *
- * Call this on **client-supplied input** before Zod validation so the error
- * message clearly names every offending key.  Do NOT call on merged data that
- * includes existing record values — older records may legitimately carry stale
- * keys that predate this guard (see issue #658).
- *
- * Maps to HTTP 400 via `SchemaExceptionFilter` (code SCHEMA_VALIDATION_FAILED).
- */
-declare function rejectUnknownAttributesOrThrow(objectDef: ObjectDefinition, data: Record<string, unknown>): void;
-/**
- * Get the list of required attributes that are missing values.
- */
-declare function getMissingRequiredAttributes(objectDef: ObjectDefinition, data: Record<string, unknown>): Attribute[];
-/**
- * Check if a record is complete (all required attributes have valid values).
- */
-declare function isRecordComplete(objectDef: ObjectDefinition, data: Record<string, unknown>): boolean;
-
-export { createFormAttributeValidator as a, validateDraft as b, createAttributeValidator as c, validateDraftOrThrow as d, validateObject as e, validateObjectOrThrow as f, getMissingRequiredAttributes as g, isRecordComplete as i, rejectUnknownAttributesOrThrow as r, validateAttribute as v };