@zitadel/api 0.0.0 → 0.1.0-alpha.10

package/src/generated/model/submitFlowStep200StepFields.ts

@@ -1,45 +0,0 @@
-/**
- * Generated by orval v8.10.0 🍺
- * Do not edit manually.
- * Zitadel NextGen
- * This is the next generation of the Zitadel identity platform.
- * OpenAPI spec version: 0.0.1
- */
-import type { SubmitFlowStep200StepFieldsType } from "./submitFlowStep200StepFieldsType";
-import type { SubmitFlowStep200StepFieldsValidation } from "./submitFlowStep200StepFieldsValidation";
-
-/**
- * Unordered dictionary of input fields to collect. Keyed by field name.
-The LiquidJS template controls which fields appear and in what order.
-Field metadata (type, validation) is resolved by the engine from the
-flow's user schema.
-
- */
-export type SubmitFlowStep200StepFields = {
-  [key: string]: {
-    /** The input kind the client should render. Encodes the formats that
-  have a matching HTML input type (email, url, date). For other
-  formats (e.g. uuid) the type is `text` and `validation.format`
-  carries the rule.
-   */
-    type: SubmitFlowStep200StepFieldsType;
-    /** Localization key for the field label. */
-    text_key: string;
-    /** The field MUST be present and non-empty on submit. Mirrors the
-  schema's top-level `required` array.
-   */
-    required?: boolean;
-    /** Pre-filled value (e.g., an identifier carried over from a pivot). */
-    value?: unknown;
-    /** Schema-derived rules the frontend SHOULD apply at input time. The
-  server runs the same rules on submit and is the only authority on
-  whether the step advances — these rules are a UX hint to reduce
-  round trips, not a contract guarantee.
-
-  Omitted entirely when the field has no rules beyond its `type`.
-  Each key mirrors a JSON Schema keyword on the underlying user
-  property; absent keys mean no rule.
-   */
-    validation?: SubmitFlowStep200StepFieldsValidation;
-  };
-};

package/src/generated/model/submitFlowStep200StepFieldsType.ts

@@ -1,28 +0,0 @@
-/**
- * Generated by orval v8.10.0 🍺
- * Do not edit manually.
- * Zitadel NextGen
- * This is the next generation of the Zitadel identity platform.
- * OpenAPI spec version: 0.0.1
- */
-
-/**
- * The input kind the client should render. Encodes the formats that
-have a matching HTML input type (email, url, date). For other
-formats (e.g. uuid) the type is `text` and `validation.format`
-carries the rule.
-
- */
-export type SubmitFlowStep200StepFieldsType =
-  (typeof SubmitFlowStep200StepFieldsType)[keyof typeof SubmitFlowStep200StepFieldsType];
-
-export const SubmitFlowStep200StepFieldsType = {
-  text: "text",
-  email: "email",
-  password: "password",
-  tel: "tel",
-  number: "number",
-  url: "url",
-  date: "date",
-  hidden: "hidden",
-} as const;

package/src/generated/model/submitFlowStep400StepFields.ts

@@ -1,45 +0,0 @@
-/**
- * Generated by orval v8.10.0 🍺
- * Do not edit manually.
- * Zitadel NextGen
- * This is the next generation of the Zitadel identity platform.
- * OpenAPI spec version: 0.0.1
- */
-import type { SubmitFlowStep400StepFieldsType } from "./submitFlowStep400StepFieldsType";
-import type { SubmitFlowStep400StepFieldsValidation } from "./submitFlowStep400StepFieldsValidation";
-
-/**
- * Unordered dictionary of input fields to collect. Keyed by field name.
-The LiquidJS template controls which fields appear and in what order.
-Field metadata (type, validation) is resolved by the engine from the
-flow's user schema.
-
- */
-export type SubmitFlowStep400StepFields = {
-  [key: string]: {
-    /** The input kind the client should render. Encodes the formats that
-  have a matching HTML input type (email, url, date). For other
-  formats (e.g. uuid) the type is `text` and `validation.format`
-  carries the rule.
-   */
-    type: SubmitFlowStep400StepFieldsType;
-    /** Localization key for the field label. */
-    text_key: string;
-    /** The field MUST be present and non-empty on submit. Mirrors the
-  schema's top-level `required` array.
-   */
-    required?: boolean;
-    /** Pre-filled value (e.g., an identifier carried over from a pivot). */
-    value?: unknown;
-    /** Schema-derived rules the frontend SHOULD apply at input time. The
-  server runs the same rules on submit and is the only authority on
-  whether the step advances — these rules are a UX hint to reduce
-  round trips, not a contract guarantee.
-
-  Omitted entirely when the field has no rules beyond its `type`.
-  Each key mirrors a JSON Schema keyword on the underlying user
-  property; absent keys mean no rule.
-   */
-    validation?: SubmitFlowStep400StepFieldsValidation;
-  };
-};

package/src/generated/model/submitFlowStep400StepFieldsType.ts

@@ -1,28 +0,0 @@
-/**
- * Generated by orval v8.10.0 🍺
- * Do not edit manually.
- * Zitadel NextGen
- * This is the next generation of the Zitadel identity platform.
- * OpenAPI spec version: 0.0.1
- */
-
-/**
- * The input kind the client should render. Encodes the formats that
-have a matching HTML input type (email, url, date). For other
-formats (e.g. uuid) the type is `text` and `validation.format`
-carries the rule.
-
- */
-export type SubmitFlowStep400StepFieldsType =
-  (typeof SubmitFlowStep400StepFieldsType)[keyof typeof SubmitFlowStep400StepFieldsType];
-
-export const SubmitFlowStep400StepFieldsType = {
-  text: "text",
-  email: "email",
-  password: "password",
-  tel: "tel",
-  number: "number",
-  url: "url",
-  date: "date",
-  hidden: "hidden",
-} as const;

package/src/generated/model/updateFlowDefinitionBodyStepsItemActions.ts

@@ -1,29 +0,0 @@
-/**
- * Generated by orval v8.10.0 🍺
- * Do not edit manually.
- * Zitadel NextGen
- * This is the next generation of the Zitadel identity platform.
- * OpenAPI spec version: 0.0.1
- */
-
-/**
- * Actions the user can take. Keyed by action name.
-The action name is what the frontend sends back in the submit request.
-If omitted, the engine provides a default `submit` action.
-
- */
-export type UpdateFlowDefinitionBodyStepsItemActions = {
-  [key: string]: {
-    /** Marks this as the default/primary action. The runtime template uses
-  this hint to choose visual emphasis. At most one action per step
-  should be primary; this is not enforced here.
-   */
-    primary?: boolean;
-    /** Optional localization key override for the action's label. When
-  omitted, the engine derives a key from the step and action names.
-  Display text is resolved client-side from a locale dictionary, never
-  by the engine.
-   */
-    text_key?: string;
-  };
-};