@nodii/onboarding 0.1.0-dev.0 → 0.1.0

package/dist/schema-TfyBU6JW.d.ts

@@ -1,107 +0,0 @@
-import { z } from 'zod/v3';
-
-/**
- * Contact-form Zod schema — mirrors the LOCKED hub REST contract exactly:
- *   POST /api/v1/public/onboarding/leads
- *   Schema: PublicOnboardingLeadsRequest (hub id 8686dd33)
- *
- * Constraints (per hub JSON Schema):
- *   name     — string, 1-200 chars, required
- *   email    — email format, required
- *   phone    — string, optional (no server-side constraint beyond string)
- *   message  — string, ≤4000 chars, optional
- *   botToken — string, required (reCAPTCHA token, D537)
- *
- *   additionalProperties: false
- *
- * The schema intentionally does NOT include botToken in the public-facing
- * ContactFormValues type — that field is injected by the submit client right
- * before the POST (the widget/form never exposes it to the user).
- */
-
-/**
- * The user-visible contact form fields. Validated client-side for UX.
- * Server re-validates authoritatively (D540 §2).
- */
-declare const contactFormSchema: z.ZodObject<{
-    name: z.ZodString;
-    email: z.ZodString;
-    phone: z.ZodOptional<z.ZodString>;
-    message: z.ZodOptional<z.ZodString>;
-}, "strip", z.ZodTypeAny, {
-    name: string;
-    email: string;
-    phone?: string | undefined;
-    message?: string | undefined;
-}, {
-    name: string;
-    email: string;
-    phone?: string | undefined;
-    message?: string | undefined;
-}>;
-type ContactFormValues = z.infer<typeof contactFormSchema>;
-/**
- * The full wire payload — contactFormSchema + botToken.
- *
- * STRICT mode: unknown keys are REJECTED (not stripped), mirroring the
- * server's `additionalProperties: false`. `submitLead` runs every outgoing
- * payload through this schema before the POST — an extra key never reaches
- * the wire; it fails fast client-side with OnboardingValidationError.
- */
-declare const leadsWireSchema: z.ZodObject<{
-    name: z.ZodString;
-    email: z.ZodString;
-    phone: z.ZodOptional<z.ZodString>;
-    message: z.ZodOptional<z.ZodString>;
-} & {
-    botToken: z.ZodString;
-}, "strict", z.ZodTypeAny, {
-    name: string;
-    email: string;
-    botToken: string;
-    phone?: string | undefined;
-    message?: string | undefined;
-}, {
-    name: string;
-    email: string;
-    botToken: string;
-    phone?: string | undefined;
-    message?: string | undefined;
-}>;
-type LeadsWirePayload = z.infer<typeof leadsWireSchema>;
-/**
- * Validate user-visible form values (no botToken required here).
- * Returns a Zod SafeParseReturnType (inferred).
- */
-declare function validateContactForm(values: unknown): z.SafeParseReturnType<{
-    name: string;
-    email: string;
-    phone?: string | undefined;
-    message?: string | undefined;
-}, {
-    name: string;
-    email: string;
-    phone?: string | undefined;
-    message?: string | undefined;
-}>;
-/**
- * Validate the full wire payload (including botToken) before submission.
- * STRICT: unknown keys are rejected, matching additionalProperties:false.
- * This is the exact validation `submitLead` applies on the wire path.
- * Returns a Zod SafeParseReturnType (inferred).
- */
-declare function validateLeadsPayload(payload: unknown): z.SafeParseReturnType<{
-    name: string;
-    email: string;
-    botToken: string;
-    phone?: string | undefined;
-    message?: string | undefined;
-}, {
-    name: string;
-    email: string;
-    botToken: string;
-    phone?: string | undefined;
-    message?: string | undefined;
-}>;
-
-export { type ContactFormValues as C, type LeadsWirePayload as L, validateLeadsPayload as a, contactFormSchema as c, leadsWireSchema as l, validateContactForm as v };