@leaflow/sdk 0.0.0-dev.418.ge62522e → 0.0.0-dev.422.gef294af

package/dist/dns/v1/generated/validators/fieldViolation.zod.d.ts

@@ -0,0 +1,57 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow DNS API
+ * Manage DNS records across supported providers through a single API. Register a provider
+ * credential, and every domain that credential can reach becomes readable and writable here.
+ *
+ * Reads and writes always reflect the current state at the provider. Records changed through the
+ * provider's own console, an ACME client, or any other automation are visible here immediately,
+ * and changes made here take effect there.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * **Neither the path nor the headers carry a `project_id`**: the current project is determined by
+ * the token.
+ *
+ * ## Conventions
+ *
+ * - **Records are addressed as record sets, not as individual records.** All records sharing a
+ *   name and a type form one set — for example, three A records pointing at three addresses. This
+ *   API exposes no per-record identifier, because provider-assigned identifiers are neither
+ *   portable across providers nor guaranteed to be stable within one.
+ * - **`PUT` replaces an entire record set; `PATCH` names individual values.** See below; this is
+ *   the single most consequential distinction in this API.
+ * - **Confirm which credential owns a domain before writing to it.** The same domain can exist in
+ *   more than one provider account — most commonly while a domain is being migrated and the old
+ *   account still holds it — and only one of them is actually serving queries.
+ * - **Changes do not take effect everywhere at once.** A write reaches the provider immediately,
+ *   but resolvers elsewhere continue serving the previous value until its TTL expires. Allow at
+ *   least one TTL before verifying a change by resolving the name.
+ * - **Credential material is never returned.** No operation, including the one that registers it,
+ *   returns the values that were submitted. A credential that was entered incorrectly must be
+ *   deleted and registered again.
+ *
+ * ## PUT or PATCH
+ *
+ * `PUT` states what a record set should contain. `PATCH` names values to add or remove and leaves
+ * the rest alone. The distinction is concurrency.
+ *
+ * Changing part of a set with `PUT` means reading it and submitting a modified list. That is a
+ * read-modify-write: a value added in between — by a concurrent certificate issuance, by another
+ * automation, or from the provider's own console — is absent from the submitted list and is
+ * therefore removed. Every request in that sequence returns 2xx.
+ *
+ * `PATCH` reads nothing. It is the only operation on a record set safe to issue concurrently, and
+ * the one certificate issuance must use.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export declare const FieldViolation: zod.ZodObject<{
+    field: zod.ZodString;
+    reason: zod.ZodOptional<zod.ZodString>;
+}, zod.z.core.$strict>;
+export type FieldViolation = zod.input<typeof FieldViolation>;
+export type FieldViolationOutput = zod.output<typeof FieldViolation>;

package/dist/dns/v1/generated/validators/fieldViolation.zod.js

@@ -0,0 +1,60 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow DNS API
+ * Manage DNS records across supported providers through a single API. Register a provider
+ * credential, and every domain that credential can reach becomes readable and writable here.
+ *
+ * Reads and writes always reflect the current state at the provider. Records changed through the
+ * provider's own console, an ACME client, or any other automation are visible here immediately,
+ * and changes made here take effect there.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * **Neither the path nor the headers carry a `project_id`**: the current project is determined by
+ * the token.
+ *
+ * ## Conventions
+ *
+ * - **Records are addressed as record sets, not as individual records.** All records sharing a
+ *   name and a type form one set — for example, three A records pointing at three addresses. This
+ *   API exposes no per-record identifier, because provider-assigned identifiers are neither
+ *   portable across providers nor guaranteed to be stable within one.
+ * - **`PUT` replaces an entire record set; `PATCH` names individual values.** See below; this is
+ *   the single most consequential distinction in this API.
+ * - **Confirm which credential owns a domain before writing to it.** The same domain can exist in
+ *   more than one provider account — most commonly while a domain is being migrated and the old
+ *   account still holds it — and only one of them is actually serving queries.
+ * - **Changes do not take effect everywhere at once.** A write reaches the provider immediately,
+ *   but resolvers elsewhere continue serving the previous value until its TTL expires. Allow at
+ *   least one TTL before verifying a change by resolving the name.
+ * - **Credential material is never returned.** No operation, including the one that registers it,
+ *   returns the values that were submitted. A credential that was entered incorrectly must be
+ *   deleted and registered again.
+ *
+ * ## PUT or PATCH
+ *
+ * `PUT` states what a record set should contain. `PATCH` names values to add or remove and leaves
+ * the rest alone. The distinction is concurrency.
+ *
+ * Changing part of a set with `PUT` means reading it and submitting a modified list. That is a
+ * read-modify-write: a value added in between — by a concurrent certificate issuance, by another
+ * automation, or from the provider's own console — is absent from the submitted list and is
+ * therefore removed. Every request in that sequence returns 2xx.
+ *
+ * `PATCH` reads nothing. It is the only operation on a record set safe to issue concurrently, and
+ * the one certificate issuance must use.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export const FieldViolation = zod.strictObject({
+    field: zod
+        .string()
+        .describe("The path to the rejected field in the request body, such as `items[2].price_id`."),
+    reason: zod
+        .string()
+        .optional()
+        .describe("Why the field was rejected, such as `REQUIRED` or `OUT_OF_RANGE`."),
+});

package/dist/iam/v1/generated/models.d.ts

@@ -12,22 +12,64 @@
  * project. It does not state whether a given operation is allowed; each service declares which permission its own operations require.
  * OpenAPI spec version: 1.0.0
  */
+export interface FieldViolation {
+    /** The path to the rejected field in the request body, such as `items[2].price_id`. */
+    field: string;
+    /** Why the field was rejected, such as `REQUIRED` or `OUT_OF_RANGE`. */
+    reason?: string;
+}
 /**
- * What a given `code` carries alongside the message. The keys depend on the code,
- * and a client that does not recognise one ignores it.
+ * Values that belong to `reason`, one set per reason. Clients use them to fill in
+ * localized text and never parse `message` to obtain them. Keys are documented per
+ * reason; a key that has appeared once keeps appearing.
  */
-export type ErrorMeta = {
-    [key: string]: unknown;
+export type ErrorStatusMetadata = {
+    [key: string]: string;
 };
-export interface Error {
-    code?: string;
+export interface ErrorStatus {
+    /** The HTTP status code of the response. */
+    code: number;
+    /** The canonical name of the status, such as `INVALID_ARGUMENT` or `UNAVAILABLE`. */
+    status: string;
+    /**
+     * A description of the failure for developers. It is always English and is not meant
+     * to be shown to end users as is.
+     */
     message: string;
     /**
-     * What a given `code` carries alongside the message. The keys depend on the code,
-     * and a client that does not recognise one ignores it.
+     * A stable machine-readable code identifying the failure. Clients branch on this value
+     * and render their own text; it does not change once published.
+     */
+    reason?: string;
+    /**
+     * Values that belong to `reason`, one set per reason. Clients use them to fill in
+     * localized text and never parse `message` to obtain them. Keys are documented per
+     * reason; a key that has appeared once keeps appearing.
+     */
+    metadata?: ErrorStatusMetadata;
+    /**
+     * Request fields rejected by the request's constraints. Present on validation
+     * failures; one request may violate several fields.
      */
-    meta?: ErrorMeta;
-    status: number;
+    field_violations?: FieldViolation[];
+    /**
+     * How long the client should wait before retrying, as a duration string such as
+     * `30s`. Present only when waiting can succeed.
+     */
+    retry_delay?: string;
+    /**
+     * The identifier of the request in the service's logs. Quote it when reporting a
+     * failure.
+     */
+    request_id?: string;
+}
+/**
+ * A failed request. The envelope follows the Google REST error format: `code` is the HTTP
+ * status, `status` is its canonical name, and `reason` is the stable machine-readable code
+ * that identifies the failure.
+ */
+export interface Error {
+    error: ErrorStatus;
 }
 export interface PermissionResource {
     /** The code of the permission, such as compute:instance.delete. **There is no display name here** — what a permission reads as is localised, and translation belongs to the layer rendering it. Until a translation catches up, the code itself is what is shown */

package/dist/iam/v1/generated/validators/error.zod.d.ts

@@ -14,10 +14,19 @@
  */
 import * as zod from "zod";
 export declare const Error: zod.ZodObject<{
-    code: zod.ZodOptional<zod.ZodString>;
-    message: zod.ZodString;
-    meta: zod.ZodOptional<zod.ZodRecord<zod.ZodString, zod.ZodUnknown>>;
-    status: zod.ZodInt;
+    error: zod.ZodObject<{
+        code: zod.ZodInt;
+        status: zod.ZodString;
+        message: zod.ZodString;
+        reason: zod.ZodOptional<zod.ZodString>;
+        metadata: zod.ZodOptional<zod.ZodRecord<zod.ZodString, zod.ZodString>>;
+        field_violations: zod.ZodOptional<zod.ZodArray<zod.ZodObject<{
+            field: zod.ZodString;
+            reason: zod.ZodOptional<zod.ZodString>;
+        }, zod.z.core.$strict>>>;
+        retry_delay: zod.ZodOptional<zod.ZodString>;
+        request_id: zod.ZodOptional<zod.ZodString>;
+    }, zod.z.core.$strict>;
 }, zod.z.core.$strict>;
 export type Error = zod.input<typeof Error>;
 export type ErrorOutput = zod.output<typeof Error>;

package/dist/iam/v1/generated/validators/error.zod.js

@@ -13,12 +13,9 @@
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";
-export const Error = zod.strictObject({
-    code: zod.string().optional(),
-    message: zod.string(),
-    meta: zod
-        .record(zod.string(), zod.unknown())
-        .optional()
-        .describe("What a given `code` carries alongside the message. The keys depend on the code,\nand a client that does not recognise one ignores it."),
-    status: zod.int(),
-});
+import { ErrorStatus } from "./errorStatus.zod.js";
+export const Error = zod
+    .strictObject({
+    error: ErrorStatus,
+})
+    .describe("A failed request. The envelope follows the Google REST error format: `code` is the HTTP\nstatus, `status` is its canonical name, and `reason` is the stable machine-readable code\nthat identifies the failure.");

package/dist/iam/v1/generated/validators/errorStatus.zod.d.ts

@@ -0,0 +1,30 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow IAM API
+ * What happens inside a project: members, roles, invitations and SSH keys.
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme. No path carries a
+ * `projectId`, and the current project is the one the token states. Tokens are obtained from the
+ * account API.
+ *
+ * `GET /api/v1/membership` returns the roles and permissions the caller holds in the current
+ * project. It does not state whether a given operation is allowed; each service declares which permission its own operations require.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export declare const ErrorStatus: zod.ZodObject<{
+    code: zod.ZodInt;
+    status: zod.ZodString;
+    message: zod.ZodString;
+    reason: zod.ZodOptional<zod.ZodString>;
+    metadata: zod.ZodOptional<zod.ZodRecord<zod.ZodString, zod.ZodString>>;
+    field_violations: zod.ZodOptional<zod.ZodArray<zod.ZodObject<{
+        field: zod.ZodString;
+        reason: zod.ZodOptional<zod.ZodString>;
+    }, zod.z.core.$strict>>>;
+    retry_delay: zod.ZodOptional<zod.ZodString>;
+    request_id: zod.ZodOptional<zod.ZodString>;
+}, zod.z.core.$strict>;
+export type ErrorStatus = zod.input<typeof ErrorStatus>;
+export type ErrorStatusOutput = zod.output<typeof ErrorStatus>;

package/dist/iam/v1/generated/validators/errorStatus.zod.js

@@ -0,0 +1,45 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow IAM API
+ * What happens inside a project: members, roles, invitations and SSH keys.
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme. No path carries a
+ * `projectId`, and the current project is the one the token states. Tokens are obtained from the
+ * account API.
+ *
+ * `GET /api/v1/membership` returns the roles and permissions the caller holds in the current
+ * project. It does not state whether a given operation is allowed; each service declares which permission its own operations require.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+import { FieldViolation } from "./fieldViolation.zod.js";
+export const ErrorStatus = zod.strictObject({
+    code: zod.int().describe("The HTTP status code of the response."),
+    status: zod
+        .string()
+        .describe("The canonical name of the status, such as `INVALID_ARGUMENT` or `UNAVAILABLE`."),
+    message: zod
+        .string()
+        .describe("A description of the failure for developers. It is always English and is not meant\nto be shown to end users as is."),
+    reason: zod
+        .string()
+        .optional()
+        .describe("A stable machine-readable code identifying the failure. Clients branch on this value\nand render their own text; it does not change once published."),
+    metadata: zod
+        .record(zod.string(), zod.string())
+        .optional()
+        .describe("Values that belong to `reason`, one set per reason. Clients use them to fill in\nlocalized text and never parse `message` to obtain them. Keys are documented per\nreason; a key that has appeared once keeps appearing."),
+    field_violations: zod
+        .array(FieldViolation)
+        .optional()
+        .describe("Request fields rejected by the request's constraints. Present on validation\nfailures; one request may violate several fields."),
+    retry_delay: zod
+        .string()
+        .optional()
+        .describe("How long the client should wait before retrying, as a duration string such as\n`30s`. Present only when waiting can succeed."),
+    request_id: zod
+        .string()
+        .optional()
+        .describe("The identifier of the request in the service's logs. Quote it when reporting a\nfailure."),
+});

package/dist/iam/v1/generated/validators/fieldViolation.zod.d.ts

@@ -0,0 +1,21 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow IAM API
+ * What happens inside a project: members, roles, invitations and SSH keys.
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme. No path carries a
+ * `projectId`, and the current project is the one the token states. Tokens are obtained from the
+ * account API.
+ *
+ * `GET /api/v1/membership` returns the roles and permissions the caller holds in the current
+ * project. It does not state whether a given operation is allowed; each service declares which permission its own operations require.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export declare const FieldViolation: zod.ZodObject<{
+    field: zod.ZodString;
+    reason: zod.ZodOptional<zod.ZodString>;
+}, zod.z.core.$strict>;
+export type FieldViolation = zod.input<typeof FieldViolation>;
+export type FieldViolationOutput = zod.output<typeof FieldViolation>;

package/dist/iam/v1/generated/validators/fieldViolation.zod.js

@@ -0,0 +1,24 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow IAM API
+ * What happens inside a project: members, roles, invitations and SSH keys.
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme. No path carries a
+ * `projectId`, and the current project is the one the token states. Tokens are obtained from the
+ * account API.
+ *
+ * `GET /api/v1/membership` returns the roles and permissions the caller holds in the current
+ * project. It does not state whether a given operation is allowed; each service declares which permission its own operations require.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export const FieldViolation = zod.strictObject({
+    field: zod
+        .string()
+        .describe("The path to the rejected field in the request body, such as `items[2].price_id`."),
+    reason: zod
+        .string()
+        .optional()
+        .describe("Why the field was rejected, such as `REQUIRED` or `OUT_OF_RANGE`."),
+});

package/dist/membership/v1/generated/models.d.ts

@@ -5,22 +5,64 @@
  * Membership tiers and account memberships. Catalog queries support any configured currency; purchases use the billing account currency.
  * OpenAPI spec version: 1.0.0
  */
+export interface FieldViolation {
+    /** The path to the rejected field in the request body, such as `items[2].price_id`. */
+    field: string;
+    /** Why the field was rejected, such as `REQUIRED` or `OUT_OF_RANGE`. */
+    reason?: string;
+}
 /**
- * What a given `code` carries alongside the message. The keys depend on the code,
- * and a client that does not recognise one ignores it.
+ * Values that belong to `reason`, one set per reason. Clients use them to fill in
+ * localized text and never parse `message` to obtain them. Keys are documented per
+ * reason; a key that has appeared once keeps appearing.
  */
-export type ErrorMeta = {
-    [key: string]: unknown;
+export type ErrorStatusMetadata = {
+    [key: string]: string;
 };
-export interface Error {
-    code?: string;
+export interface ErrorStatus {
+    /** The HTTP status code of the response. */
+    code: number;
+    /** The canonical name of the status, such as `INVALID_ARGUMENT` or `UNAVAILABLE`. */
+    status: string;
+    /**
+     * A description of the failure for developers. It is always English and is not meant
+     * to be shown to end users as is.
+     */
     message: string;
     /**
-     * What a given `code` carries alongside the message. The keys depend on the code,
-     * and a client that does not recognise one ignores it.
+     * A stable machine-readable code identifying the failure. Clients branch on this value
+     * and render their own text; it does not change once published.
+     */
+    reason?: string;
+    /**
+     * Values that belong to `reason`, one set per reason. Clients use them to fill in
+     * localized text and never parse `message` to obtain them. Keys are documented per
+     * reason; a key that has appeared once keeps appearing.
+     */
+    metadata?: ErrorStatusMetadata;
+    /**
+     * Request fields rejected by the request's constraints. Present on validation
+     * failures; one request may violate several fields.
      */
-    meta?: ErrorMeta;
-    status: number;
+    field_violations?: FieldViolation[];
+    /**
+     * How long the client should wait before retrying, as a duration string such as
+     * `30s`. Present only when waiting can succeed.
+     */
+    retry_delay?: string;
+    /**
+     * The identifier of the request in the service's logs. Quote it when reporting a
+     * failure.
+     */
+    request_id?: string;
+}
+/**
+ * A failed request. The envelope follows the Google REST error format: `code` is the HTTP
+ * status, `status` is its canonical name, and `reason` is the stable machine-readable code
+ * that identifies the failure.
+ */
+export interface Error {
+    error: ErrorStatus;
 }
 /**
  * A decimal string, in the currency stated alongside it.

package/dist/membership/v1/generated/validators/error.zod.d.ts

@@ -7,10 +7,19 @@
  */
 import * as zod from "zod";
 export declare const Error: zod.ZodObject<{
-    code: zod.ZodOptional<zod.ZodString>;
-    message: zod.ZodString;
-    meta: zod.ZodOptional<zod.ZodRecord<zod.ZodString, zod.ZodUnknown>>;
-    status: zod.ZodInt;
+    error: zod.ZodObject<{
+        code: zod.ZodInt;
+        status: zod.ZodString;
+        message: zod.ZodString;
+        reason: zod.ZodOptional<zod.ZodString>;
+        metadata: zod.ZodOptional<zod.ZodRecord<zod.ZodString, zod.ZodString>>;
+        field_violations: zod.ZodOptional<zod.ZodArray<zod.ZodObject<{
+            field: zod.ZodString;
+            reason: zod.ZodOptional<zod.ZodString>;
+        }, zod.z.core.$strict>>>;
+        retry_delay: zod.ZodOptional<zod.ZodString>;
+        request_id: zod.ZodOptional<zod.ZodString>;
+    }, zod.z.core.$strict>;
 }, zod.z.core.$strict>;
 export type Error = zod.input<typeof Error>;
 export type ErrorOutput = zod.output<typeof Error>;

package/dist/membership/v1/generated/validators/error.zod.js

@@ -6,12 +6,9 @@
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";
-export const Error = zod.strictObject({
-    code: zod.string().optional(),
-    message: zod.string(),
-    meta: zod
-        .record(zod.string(), zod.unknown())
-        .optional()
-        .describe("What a given `code` carries alongside the message. The keys depend on the code,\nand a client that does not recognise one ignores it."),
-    status: zod.int(),
-});
+import { ErrorStatus } from "./errorStatus.zod.js";
+export const Error = zod
+    .strictObject({
+    error: ErrorStatus,
+})
+    .describe("A failed request. The envelope follows the Google REST error format: `code` is the HTTP\nstatus, `status` is its canonical name, and `reason` is the stable machine-readable code\nthat identifies the failure.");

package/dist/membership/v1/generated/validators/errorStatus.zod.d.ts

@@ -0,0 +1,23 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Membership API
+ * Membership tiers and account memberships. Catalog queries support any configured currency; purchases use the billing account currency.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export declare const ErrorStatus: zod.ZodObject<{
+    code: zod.ZodInt;
+    status: zod.ZodString;
+    message: zod.ZodString;
+    reason: zod.ZodOptional<zod.ZodString>;
+    metadata: zod.ZodOptional<zod.ZodRecord<zod.ZodString, zod.ZodString>>;
+    field_violations: zod.ZodOptional<zod.ZodArray<zod.ZodObject<{
+        field: zod.ZodString;
+        reason: zod.ZodOptional<zod.ZodString>;
+    }, zod.z.core.$strict>>>;
+    retry_delay: zod.ZodOptional<zod.ZodString>;
+    request_id: zod.ZodOptional<zod.ZodString>;
+}, zod.z.core.$strict>;
+export type ErrorStatus = zod.input<typeof ErrorStatus>;
+export type ErrorStatusOutput = zod.output<typeof ErrorStatus>;

package/dist/membership/v1/generated/validators/errorStatus.zod.js

@@ -0,0 +1,38 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Membership API
+ * Membership tiers and account memberships. Catalog queries support any configured currency; purchases use the billing account currency.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+import { FieldViolation } from "./fieldViolation.zod.js";
+export const ErrorStatus = zod.strictObject({
+    code: zod.int().describe("The HTTP status code of the response."),
+    status: zod
+        .string()
+        .describe("The canonical name of the status, such as `INVALID_ARGUMENT` or `UNAVAILABLE`."),
+    message: zod
+        .string()
+        .describe("A description of the failure for developers. It is always English and is not meant\nto be shown to end users as is."),
+    reason: zod
+        .string()
+        .optional()
+        .describe("A stable machine-readable code identifying the failure. Clients branch on this value\nand render their own text; it does not change once published."),
+    metadata: zod
+        .record(zod.string(), zod.string())
+        .optional()
+        .describe("Values that belong to `reason`, one set per reason. Clients use them to fill in\nlocalized text and never parse `message` to obtain them. Keys are documented per\nreason; a key that has appeared once keeps appearing."),
+    field_violations: zod
+        .array(FieldViolation)
+        .optional()
+        .describe("Request fields rejected by the request's constraints. Present on validation\nfailures; one request may violate several fields."),
+    retry_delay: zod
+        .string()
+        .optional()
+        .describe("How long the client should wait before retrying, as a duration string such as\n`30s`. Present only when waiting can succeed."),
+    request_id: zod
+        .string()
+        .optional()
+        .describe("The identifier of the request in the service's logs. Quote it when reporting a\nfailure."),
+});

package/dist/membership/v1/generated/validators/fieldViolation.zod.d.ts

@@ -0,0 +1,14 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Membership API
+ * Membership tiers and account memberships. Catalog queries support any configured currency; purchases use the billing account currency.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export declare const FieldViolation: zod.ZodObject<{
+    field: zod.ZodString;
+    reason: zod.ZodOptional<zod.ZodString>;
+}, zod.z.core.$strict>;
+export type FieldViolation = zod.input<typeof FieldViolation>;
+export type FieldViolationOutput = zod.output<typeof FieldViolation>;

package/dist/membership/v1/generated/validators/fieldViolation.zod.js

@@ -0,0 +1,17 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Membership API
+ * Membership tiers and account memberships. Catalog queries support any configured currency; purchases use the billing account currency.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export const FieldViolation = zod.strictObject({
+    field: zod
+        .string()
+        .describe("The path to the rejected field in the request body, such as `items[2].price_id`."),
+    reason: zod
+        .string()
+        .optional()
+        .describe("Why the field was rejected, such as `REQUIRED` or `OUT_OF_RANGE`."),
+});