@wix/auto_sdk_form-templates_form-templates 1.0.11 → 1.0.13

package/build/internal/cjs/index.d.ts

@@ -16,7 +16,7 @@ interface ListFormTemplatesSignature {
      * the app that owns the templates in the app dashboard.
      * @returns Templates per namespace are hard-limited to a single page (AIP-4003), so the response isn't paged.
      */
-    (namespace: string, options?: ListFormTemplatesOptions): Promise<NonNullablePaths<ListFormTemplatesResponse, `templates` | `templates.${number}.namespace` | `templates.${number}.submitSettings.redirectOptions.target` | `templates.${number}.submitSettings.popupOptions.popupId` | `templates.${number}.submitSettings.submitSuccessAction` | `templates.${number}.requiredIndicatorProperties.requiredIndicator` | `templates.${number}.requiredIndicatorProperties.requiredIndicatorPlacement` | `templates.${number}.autoFillContact` | `templates.${number}.quizSettings.passingScorePoints` | `templates.${number}.quizSettings.passingScorePercentage` | `templates.${number}.quizSettings.resultsDisplay`, 6>>;
+    (namespace: string, options?: ListFormTemplatesOptions): Promise<NonNullablePaths<ListFormTemplatesResponse, `templates` | `templates.${number}.namespace` | `templates.${number}.submitSettings.redirectOptions.target` | `templates.${number}.submitSettings.popupOptions.popupId` | `templates.${number}.submitSettings.submitSuccessAction` | `templates.${number}.requiredIndicatorProperties.requiredIndicator` | `templates.${number}.requiredIndicatorProperties.requiredIndicatorPlacement` | `templates.${number}.autoFillContact` | `templates.${number}.quizSettings.passingScorePoints` | `templates.${number}.quizSettings.passingScorePercentage` | `templates.${number}.quizSettings.resultsDisplay`, 4>>;
 }
 
 declare const listFormTemplates: MaybeContext<BuildRESTFunction<typeof listFormTemplates$1> & typeof listFormTemplates$1>;

package/build/internal/cjs/index.typings.d.ts

@@ -146,7 +146,7 @@ interface Field extends FieldFieldTypeOptionsOneOf {
      * Identification for the field, describing its purpose. For example, `TEXT_INPUT` or `CONTACTS_EMAIL`.
      *
      * Set this to the known value for the kind of field you're creating.
-     * An unrecognized value, such as a custom string or a GUID, is dropped rather than rejected: the request still succeeds, but the field doesn't appear in the response's `formFields`, and neither the field nor its submitted values appear in the Wix dashboard.
+     * Wix accepts an unrecognized value, such as a custom string or a GUID: the request succeeds, and Wix stores the field, returns it in `formFields`, and accepts its submissions. But Wix apps use `identifier` to recognize a field, so the Wix Forms editor doesn't render it, and the Wix user can't see or edit that field. A form whose fields all carry unrecognized identifiers opens empty in the editor. Always map a field onto a known identifier, and set its display name with the component's label.
      *
      * Several fields share a general-purpose `componentType`, so `identifier` is often the only value that distinguishes them.
      * For example, both a short answer field and a long answer field use the `TEXT_INPUT` component, and are told apart by their `TEXT_INPUT` and `TEXT_AREA` identifiers.
@@ -250,6 +250,8 @@ interface InputField extends InputFieldInputTypeOptionsOneOf {
     /**
      * Whether the field is required for form submission.
      *
+     * Set this on `inputOptions`, alongside `target` and `inputType`. A `required` placed inside a validation object, such as `stringOptions.validation`, isn't part of the schema and has no effect.
+     *
      * Default: `false`
      */
     required?: boolean;
@@ -5983,7 +5985,7 @@ interface ListFormTemplatesResponse {
  * @returns Templates per namespace are hard-limited to a single page (AIP-4003), so the response isn't paged.
  * @fqn wix.forms.templates.v2.FormTemplatesService.ListFormTemplates
  */
-declare function listFormTemplates(namespace: string, options?: ListFormTemplatesOptions): Promise<NonNullablePaths<ListFormTemplatesResponse, `templates` | `templates.${number}.namespace` | `templates.${number}.submitSettings.redirectOptions.target` | `templates.${number}.submitSettings.popupOptions.popupId` | `templates.${number}.submitSettings.submitSuccessAction` | `templates.${number}.requiredIndicatorProperties.requiredIndicator` | `templates.${number}.requiredIndicatorProperties.requiredIndicatorPlacement` | `templates.${number}.autoFillContact` | `templates.${number}.quizSettings.passingScorePoints` | `templates.${number}.quizSettings.passingScorePercentage` | `templates.${number}.quizSettings.resultsDisplay`, 6>>;
+declare function listFormTemplates(namespace: string, options?: ListFormTemplatesOptions): Promise<NonNullablePaths<ListFormTemplatesResponse, `templates` | `templates.${number}.namespace` | `templates.${number}.submitSettings.redirectOptions.target` | `templates.${number}.submitSettings.popupOptions.popupId` | `templates.${number}.submitSettings.submitSuccessAction` | `templates.${number}.requiredIndicatorProperties.requiredIndicator` | `templates.${number}.requiredIndicatorProperties.requiredIndicatorPlacement` | `templates.${number}.autoFillContact` | `templates.${number}.quizSettings.passingScorePoints` | `templates.${number}.quizSettings.passingScorePercentage` | `templates.${number}.quizSettings.resultsDisplay`, 4>>;
 interface ListFormTemplatesOptions {
     /**
      * IDs of the specific templates to retrieve within the namespace. When omitted, all templates in

package/build/internal/cjs/meta.d.ts

@@ -147,7 +147,7 @@ interface Field extends FieldFieldTypeOptionsOneOf {
      * Identification for the field, describing its purpose. For example, `TEXT_INPUT` or `CONTACTS_EMAIL`.
      *
      * Set this to the known value for the kind of field you're creating.
-     * An unrecognized value, such as a custom string or a GUID, is dropped rather than rejected: the request still succeeds, but the field doesn't appear in the response's `formFields`, and neither the field nor its submitted values appear in the Wix dashboard.
+     * Wix accepts an unrecognized value, such as a custom string or a GUID: the request succeeds, and Wix stores the field, returns it in `formFields`, and accepts its submissions. But Wix apps use `identifier` to recognize a field, so the Wix Forms editor doesn't render it, and the Wix user can't see or edit that field. A form whose fields all carry unrecognized identifiers opens empty in the editor. Always map a field onto a known identifier, and set its display name with the component's label.
      *
      * Several fields share a general-purpose `componentType`, so `identifier` is often the only value that distinguishes them.
      * For example, both a short answer field and a long answer field use the `TEXT_INPUT` component, and are told apart by their `TEXT_INPUT` and `TEXT_AREA` identifiers.
@@ -251,6 +251,8 @@ interface InputField extends InputFieldInputTypeOptionsOneOf {
     /**
      * Whether the field is required for form submission.
      *
+     * Set this on `inputOptions`, alongside `target` and `inputType`. A `required` placed inside a validation object, such as `stringOptions.validation`, isn't part of the schema and has no effect.
+     *
      * Default: `false`
      */
     required?: boolean;

package/build/internal/es/index.d.mts

@@ -16,7 +16,7 @@ interface ListFormTemplatesSignature {
      * the app that owns the templates in the app dashboard.
      * @returns Templates per namespace are hard-limited to a single page (AIP-4003), so the response isn't paged.
      */
-    (namespace: string, options?: ListFormTemplatesOptions): Promise<NonNullablePaths<ListFormTemplatesResponse, `templates` | `templates.${number}.namespace` | `templates.${number}.submitSettings.redirectOptions.target` | `templates.${number}.submitSettings.popupOptions.popupId` | `templates.${number}.submitSettings.submitSuccessAction` | `templates.${number}.requiredIndicatorProperties.requiredIndicator` | `templates.${number}.requiredIndicatorProperties.requiredIndicatorPlacement` | `templates.${number}.autoFillContact` | `templates.${number}.quizSettings.passingScorePoints` | `templates.${number}.quizSettings.passingScorePercentage` | `templates.${number}.quizSettings.resultsDisplay`, 6>>;
+    (namespace: string, options?: ListFormTemplatesOptions): Promise<NonNullablePaths<ListFormTemplatesResponse, `templates` | `templates.${number}.namespace` | `templates.${number}.submitSettings.redirectOptions.target` | `templates.${number}.submitSettings.popupOptions.popupId` | `templates.${number}.submitSettings.submitSuccessAction` | `templates.${number}.requiredIndicatorProperties.requiredIndicator` | `templates.${number}.requiredIndicatorProperties.requiredIndicatorPlacement` | `templates.${number}.autoFillContact` | `templates.${number}.quizSettings.passingScorePoints` | `templates.${number}.quizSettings.passingScorePercentage` | `templates.${number}.quizSettings.resultsDisplay`, 4>>;
 }
 
 declare const listFormTemplates: MaybeContext<BuildRESTFunction<typeof listFormTemplates$1> & typeof listFormTemplates$1>;

package/build/internal/es/index.typings.d.mts

@@ -146,7 +146,7 @@ interface Field extends FieldFieldTypeOptionsOneOf {
      * Identification for the field, describing its purpose. For example, `TEXT_INPUT` or `CONTACTS_EMAIL`.
      *
      * Set this to the known value for the kind of field you're creating.
-     * An unrecognized value, such as a custom string or a GUID, is dropped rather than rejected: the request still succeeds, but the field doesn't appear in the response's `formFields`, and neither the field nor its submitted values appear in the Wix dashboard.
+     * Wix accepts an unrecognized value, such as a custom string or a GUID: the request succeeds, and Wix stores the field, returns it in `formFields`, and accepts its submissions. But Wix apps use `identifier` to recognize a field, so the Wix Forms editor doesn't render it, and the Wix user can't see or edit that field. A form whose fields all carry unrecognized identifiers opens empty in the editor. Always map a field onto a known identifier, and set its display name with the component's label.
      *
      * Several fields share a general-purpose `componentType`, so `identifier` is often the only value that distinguishes them.
      * For example, both a short answer field and a long answer field use the `TEXT_INPUT` component, and are told apart by their `TEXT_INPUT` and `TEXT_AREA` identifiers.
@@ -250,6 +250,8 @@ interface InputField extends InputFieldInputTypeOptionsOneOf {
     /**
      * Whether the field is required for form submission.
      *
+     * Set this on `inputOptions`, alongside `target` and `inputType`. A `required` placed inside a validation object, such as `stringOptions.validation`, isn't part of the schema and has no effect.
+     *
      * Default: `false`
      */
     required?: boolean;
@@ -5983,7 +5985,7 @@ interface ListFormTemplatesResponse {
  * @returns Templates per namespace are hard-limited to a single page (AIP-4003), so the response isn't paged.
  * @fqn wix.forms.templates.v2.FormTemplatesService.ListFormTemplates
  */
-declare function listFormTemplates(namespace: string, options?: ListFormTemplatesOptions): Promise<NonNullablePaths<ListFormTemplatesResponse, `templates` | `templates.${number}.namespace` | `templates.${number}.submitSettings.redirectOptions.target` | `templates.${number}.submitSettings.popupOptions.popupId` | `templates.${number}.submitSettings.submitSuccessAction` | `templates.${number}.requiredIndicatorProperties.requiredIndicator` | `templates.${number}.requiredIndicatorProperties.requiredIndicatorPlacement` | `templates.${number}.autoFillContact` | `templates.${number}.quizSettings.passingScorePoints` | `templates.${number}.quizSettings.passingScorePercentage` | `templates.${number}.quizSettings.resultsDisplay`, 6>>;
+declare function listFormTemplates(namespace: string, options?: ListFormTemplatesOptions): Promise<NonNullablePaths<ListFormTemplatesResponse, `templates` | `templates.${number}.namespace` | `templates.${number}.submitSettings.redirectOptions.target` | `templates.${number}.submitSettings.popupOptions.popupId` | `templates.${number}.submitSettings.submitSuccessAction` | `templates.${number}.requiredIndicatorProperties.requiredIndicator` | `templates.${number}.requiredIndicatorProperties.requiredIndicatorPlacement` | `templates.${number}.autoFillContact` | `templates.${number}.quizSettings.passingScorePoints` | `templates.${number}.quizSettings.passingScorePercentage` | `templates.${number}.quizSettings.resultsDisplay`, 4>>;
 interface ListFormTemplatesOptions {
     /**
      * IDs of the specific templates to retrieve within the namespace. When omitted, all templates in

package/build/internal/es/meta.d.mts

@@ -147,7 +147,7 @@ interface Field extends FieldFieldTypeOptionsOneOf {
      * Identification for the field, describing its purpose. For example, `TEXT_INPUT` or `CONTACTS_EMAIL`.
      *
      * Set this to the known value for the kind of field you're creating.
-     * An unrecognized value, such as a custom string or a GUID, is dropped rather than rejected: the request still succeeds, but the field doesn't appear in the response's `formFields`, and neither the field nor its submitted values appear in the Wix dashboard.
+     * Wix accepts an unrecognized value, such as a custom string or a GUID: the request succeeds, and Wix stores the field, returns it in `formFields`, and accepts its submissions. But Wix apps use `identifier` to recognize a field, so the Wix Forms editor doesn't render it, and the Wix user can't see or edit that field. A form whose fields all carry unrecognized identifiers opens empty in the editor. Always map a field onto a known identifier, and set its display name with the component's label.
      *
      * Several fields share a general-purpose `componentType`, so `identifier` is often the only value that distinguishes them.
      * For example, both a short answer field and a long answer field use the `TEXT_INPUT` component, and are told apart by their `TEXT_INPUT` and `TEXT_AREA` identifiers.
@@ -251,6 +251,8 @@ interface InputField extends InputFieldInputTypeOptionsOneOf {
     /**
      * Whether the field is required for form submission.
      *
+     * Set this on `inputOptions`, alongside `target` and `inputType`. A `required` placed inside a validation object, such as `stringOptions.validation`, isn't part of the schema and has no effect.
+     *
      * Default: `false`
      */
     required?: boolean;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wix/auto_sdk_form-templates_form-templates",
-  "version": "1.0.11",
+  "version": "1.0.13",
   "license": "MIT",
   "publishConfig": {
     "registry": "https://registry.npmjs.org/",
@@ -21,23 +21,16 @@
       "import": "./build/es/meta.mjs",
       "require": "./build/cjs/meta.js",
       "types": "./build/es/meta.d.mts"
-    },
-    "./schemas": {
-      "import": "./build/es/schemas.mjs",
-      "require": "./build/cjs/schemas.js",
-      "types": "./build/es/schemas.d.mts"
     }
   },
   "files": [
     "build",
     "meta",
-    "service-plugins",
-    "schemas"
+    "service-plugins"
   ],
   "dependencies": {
     "@wix/sdk-runtime": "^1.0.24",
-    "@wix/sdk-types": "^1.17.11",
-    "zod": "^4.3.6"
+    "@wix/sdk-types": "^1.17.11"
   },
   "devDependencies": {
     "tsup": "^8.4.0",
@@ -57,5 +50,5 @@
       "fqdn": "wix.forms.v2.form_template"
     }
   },
-  "falconPackageHash": "907abfb77c7ef94f94a4d45e16e8cd6dfd5ccb52aeb63a3ec4408bfd"
+  "falconPackageHash": "c75a033f09627ccf2aea5f66781b093ce8641ffd237d01d614f648c5"
 }