@opensite/ui 1.8.2 → 1.8.4

package/dist/contact-catering.d.cts

@@ -1,5 +1,6 @@
 import * as React from 'react';
-import { P as PageSpeedFormConfig } from './forms-nGgHUTBw.cjs';
+import { F as FormFieldConfig } from './form-field-types-flMXhIjG.cjs';
+import { P as PageSpeedFormConfig } from './forms-CStlFhnh.cjs';
 import { f as SectionBackground, g as SectionSpacing, s as PatternName } from './community-initiatives-k1_FqqBQ.cjs';
 import { A as ActionConfig } from './blocks-rgCERYOC.cjs';
 import '@page-speed/forms/integration';
@@ -8,23 +9,6 @@ import 'class-variance-authority';
 import './button-variants-lRElsmTc.cjs';
 import 'class-variance-authority/types';
 
-interface CateringFormValues {
-    eventType: string;
-    eventDate: string;
-    guestCount: string;
-    startTime: string;
-    endTime: string;
-    venue: string;
-    serviceStyle: string;
-    cuisinePreferences: string[];
-    dietaryAccommodations: string[];
-    budget: string;
-    name: string;
-    phone: string;
-    email: string;
-    details: string;
-    tasting: boolean;
-}
 interface ContactCateringProps {
     /**
      * Main heading content
@@ -50,12 +34,23 @@ interface ContactCateringProps {
      * Custom slot for rendering actions (overrides actions array and default submit)
      */
     actionsSlot?: React.ReactNode;
+    /**
+     * Array of form field configurations
+     * If not provided, defaults to: eventType, eventDate, guestCount, budget, serviceStyle, cuisinePreferences, dietaryAccommodations, name, email, phone, venue, details, tasting
+     */
+    formFields?: FormFieldConfig[];
+    /**
+     * Success message to display after form submission
+     * @default "Thank you for your inquiry! We'll get back to you within 24 hours with a custom proposal."
+     */
+    successMessage?: React.ReactNode;
     /**
      * Additional CSS classes for the section
      */
     className?: string;
     /**
      * Additional CSS classes for the container
+     * @default "px-6 sm:px-6 md:px-8 lg:px-8"
      */
     containerClassName?: string;
     /**
@@ -82,6 +77,14 @@ interface ContactCateringProps {
      * Additional CSS classes for the form
      */
     formClassName?: string;
+    /**
+     * Additional CSS classes for success message
+     */
+    successMessageClassName?: string;
+    /**
+     * Additional CSS classes for error message
+     */
+    errorMessageClassName?: string;
     /**
      * Additional CSS classes for the submit button
      */
@@ -92,6 +95,7 @@ interface ContactCateringProps {
     background?: SectionBackground;
     /**
      * Vertical spacing for the section
+     * @default "py-8 md:py-32"
      */
     spacing?: SectionSpacing;
     /**
@@ -103,57 +107,19 @@ interface ContactCateringProps {
      */
     patternOpacity?: number;
     /**
-     * Optional form submission configuration.
-     *
-     * **Universal Usage**: Works with ANY REST API endpoint. Simply provide an `endpoint` URL
-     * and the form will submit to it in JSON format.
-     *
-     * @example
-     * // Works with any API
-     * formConfig={{ endpoint: "https://api.mysite.com/catering", format: "json" }}
-     *
-     * @example
-     * // With custom headers (e.g., authentication)
-     * formConfig={{
-     *   endpoint: "/api/catering",
-     *   headers: { "Authorization": "Bearer token123" }
-     * }}
-     *
-     * **Note**: The `apiKey`, `contactCategoryToken`, and other platform-specific fields
-     * are OPTIONAL and only needed when integrating with DashTrack's Rails backend.
-     * For generic REST APIs, just use `endpoint`, `method`, `format`, and `headers`.
-     *
-     * See `FORMS_INTEGRATION_GUIDE.md` for complete examples with Next.js, React, and more.
+     * Optional form submission configuration. See FORMS_INTEGRATION_GUIDE.md for complete examples.
      */
     formConfig?: PageSpeedFormConfig;
     /**
-     * Optional custom submission handler for maximum flexibility.
-     *
-     * Use this when you need complete control over the submission logic,
-     * such as custom API calls, analytics tracking, or multi-step workflows.
-     *
-     * Can be used alone or in combination with `formConfig` for hybrid approaches.
-     *
-     * @example
-     * onSubmit={async (values) => {
-     *   await fetch("/api/catering", {
-     *     method: "POST",
-     *     body: JSON.stringify(values)
-     *   });
-     * }}
-     */
-    onSubmit?: (values: CateringFormValues) => void | Promise<void>;
+     * Optional custom submission handler.
+     */
+    onSubmit?: (values: Record<string, unknown>) => void | Promise<void>;
     /**
      * Optional success callback invoked after successful submission.
-     *
-     * Called after `formConfig` submission and/or `onSubmit` completes successfully.
-     * Use for showing success messages, redirecting, analytics tracking, etc.
      */
     onSuccess?: (data: unknown) => void;
     /**
      * Optional error callback invoked if submission fails.
-     *
-     * Receives the error object for custom error handling, logging, or user notifications.
      */
     onError?: (error: Error) => void;
 }
@@ -172,6 +138,6 @@ interface ContactCateringProps {
  * />
  * ```
  */
-declare function ContactCatering({ heading, description, buttonText, buttonIcon, actions, actionsSlot, className, spacing, containerClassName, headerClassName, headingClassName, descriptionClassName, cardClassName, cardContentClassName, formClassName, submitClassName, background, pattern, patternOpacity, formConfig, onSubmit, onSuccess, onError, }: ContactCateringProps): React.JSX.Element;
+declare function ContactCatering({ heading, description, buttonText, buttonIcon, actions, actionsSlot, formFields, successMessage, className, spacing, containerClassName, headerClassName, headingClassName, descriptionClassName, cardClassName, cardContentClassName, formClassName, successMessageClassName, errorMessageClassName, submitClassName, background, pattern, patternOpacity, formConfig, onSubmit, onSuccess, onError, }: ContactCateringProps): React.JSX.Element;
 
 export { ContactCatering, type ContactCateringProps };

package/dist/contact-catering.d.ts

@@ -1,5 +1,6 @@
 import * as React from 'react';
-import { P as PageSpeedFormConfig } from './forms-nGgHUTBw.js';
+import { F as FormFieldConfig } from './form-field-types-flMXhIjG.js';
+import { P as PageSpeedFormConfig } from './forms-CStlFhnh.js';
 import { f as SectionBackground, g as SectionSpacing, s as PatternName } from './community-initiatives-AwBlQu1a.js';
 import { A as ActionConfig } from './blocks-ClXAGlHQ.js';
 import '@page-speed/forms/integration';
@@ -8,23 +9,6 @@ import 'class-variance-authority';
 import './button-variants-lRElsmTc.js';
 import 'class-variance-authority/types';
 
-interface CateringFormValues {
-    eventType: string;
-    eventDate: string;
-    guestCount: string;
-    startTime: string;
-    endTime: string;
-    venue: string;
-    serviceStyle: string;
-    cuisinePreferences: string[];
-    dietaryAccommodations: string[];
-    budget: string;
-    name: string;
-    phone: string;
-    email: string;
-    details: string;
-    tasting: boolean;
-}
 interface ContactCateringProps {
     /**
      * Main heading content
@@ -50,12 +34,23 @@ interface ContactCateringProps {
      * Custom slot for rendering actions (overrides actions array and default submit)
      */
     actionsSlot?: React.ReactNode;
+    /**
+     * Array of form field configurations
+     * If not provided, defaults to: eventType, eventDate, guestCount, budget, serviceStyle, cuisinePreferences, dietaryAccommodations, name, email, phone, venue, details, tasting
+     */
+    formFields?: FormFieldConfig[];
+    /**
+     * Success message to display after form submission
+     * @default "Thank you for your inquiry! We'll get back to you within 24 hours with a custom proposal."
+     */
+    successMessage?: React.ReactNode;
     /**
      * Additional CSS classes for the section
      */
     className?: string;
     /**
      * Additional CSS classes for the container
+     * @default "px-6 sm:px-6 md:px-8 lg:px-8"
      */
     containerClassName?: string;
     /**
@@ -82,6 +77,14 @@ interface ContactCateringProps {
      * Additional CSS classes for the form
      */
     formClassName?: string;
+    /**
+     * Additional CSS classes for success message
+     */
+    successMessageClassName?: string;
+    /**
+     * Additional CSS classes for error message
+     */
+    errorMessageClassName?: string;
     /**
      * Additional CSS classes for the submit button
      */
@@ -92,6 +95,7 @@ interface ContactCateringProps {
     background?: SectionBackground;
     /**
      * Vertical spacing for the section
+     * @default "py-8 md:py-32"
      */
     spacing?: SectionSpacing;
     /**
@@ -103,57 +107,19 @@ interface ContactCateringProps {
      */
     patternOpacity?: number;
     /**
-     * Optional form submission configuration.
-     *
-     * **Universal Usage**: Works with ANY REST API endpoint. Simply provide an `endpoint` URL
-     * and the form will submit to it in JSON format.
-     *
-     * @example
-     * // Works with any API
-     * formConfig={{ endpoint: "https://api.mysite.com/catering", format: "json" }}
-     *
-     * @example
-     * // With custom headers (e.g., authentication)
-     * formConfig={{
-     *   endpoint: "/api/catering",
-     *   headers: { "Authorization": "Bearer token123" }
-     * }}
-     *
-     * **Note**: The `apiKey`, `contactCategoryToken`, and other platform-specific fields
-     * are OPTIONAL and only needed when integrating with DashTrack's Rails backend.
-     * For generic REST APIs, just use `endpoint`, `method`, `format`, and `headers`.
-     *
-     * See `FORMS_INTEGRATION_GUIDE.md` for complete examples with Next.js, React, and more.
+     * Optional form submission configuration. See FORMS_INTEGRATION_GUIDE.md for complete examples.
      */
     formConfig?: PageSpeedFormConfig;
     /**
-     * Optional custom submission handler for maximum flexibility.
-     *
-     * Use this when you need complete control over the submission logic,
-     * such as custom API calls, analytics tracking, or multi-step workflows.
-     *
-     * Can be used alone or in combination with `formConfig` for hybrid approaches.
-     *
-     * @example
-     * onSubmit={async (values) => {
-     *   await fetch("/api/catering", {
-     *     method: "POST",
-     *     body: JSON.stringify(values)
-     *   });
-     * }}
-     */
-    onSubmit?: (values: CateringFormValues) => void | Promise<void>;
+     * Optional custom submission handler.
+     */
+    onSubmit?: (values: Record<string, unknown>) => void | Promise<void>;
     /**
      * Optional success callback invoked after successful submission.
-     *
-     * Called after `formConfig` submission and/or `onSubmit` completes successfully.
-     * Use for showing success messages, redirecting, analytics tracking, etc.
      */
     onSuccess?: (data: unknown) => void;
     /**
      * Optional error callback invoked if submission fails.
-     *
-     * Receives the error object for custom error handling, logging, or user notifications.
      */
     onError?: (error: Error) => void;
 }
@@ -172,6 +138,6 @@ interface ContactCateringProps {
  * />
  * ```
  */
-declare function ContactCatering({ heading, description, buttonText, buttonIcon, actions, actionsSlot, className, spacing, containerClassName, headerClassName, headingClassName, descriptionClassName, cardClassName, cardContentClassName, formClassName, submitClassName, background, pattern, patternOpacity, formConfig, onSubmit, onSuccess, onError, }: ContactCateringProps): React.JSX.Element;
+declare function ContactCatering({ heading, description, buttonText, buttonIcon, actions, actionsSlot, formFields, successMessage, className, spacing, containerClassName, headerClassName, headingClassName, descriptionClassName, cardClassName, cardContentClassName, formClassName, successMessageClassName, errorMessageClassName, submitClassName, background, pattern, patternOpacity, formConfig, onSubmit, onSuccess, onError, }: ContactCateringProps): React.JSX.Element;
 
 export { ContactCatering, type ContactCateringProps };