@leaflow/sdk 0.0.0-dev.429.gf6440ec → 0.0.0-dev.433.g7e48b8f

package/dist/eventbus/v1/generated/validators/createEventRequest.zod.d.ts

@@ -0,0 +1,50 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Event Bus API
+ * Event definitions, versions, publishing, and realtime access.
+ *
+ * ## 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.
+ *
+ * ## Definitions and messages
+ *
+ * An event is a definition: a name, a description, and one or more versions. A version carries a
+ * JSON Schema that every published payload must satisfy. Messages are not stored here and are
+ * not part of the event definition.
+ *
+ * A project event belongs to the current project. A global event has no `project_id`; it is
+ * defined by a platform service and is read-only in this API. Global events are listed alongside
+ * the project's own events.
+ *
+ * A version number never changes meaning. Adding optional properties is allowed within a version;
+ * a breaking change creates a new version. Publishing without a version uses the highest active
+ * version.
+ *
+ * ## Publishing
+ *
+ * Publishing returns the identity of the message and does not wait for consumers. Messages are
+ * not stored and are not replayed: a consumer that connects later does not receive earlier
+ * messages. Consumers receive messages through the realtime API or the platform's service API.
+ *
+ * ## Realtime
+ *
+ * Create a ticket, connect to the returned URL with the ticket, and authenticate the connection
+ * with a scoped token. A ticket is single-use and short-lived. The connection ends when the
+ * token expires unless it is refreshed with a new scoped token for the same user and project.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export declare const createEventRequestNameMax = 128;
+export declare const createEventRequestNameRegExp: RegExp;
+export declare const createEventRequestDescriptionMax = 1024;
+export declare const CreateEventRequest: zod.ZodObject<{
+    name: zod.ZodString;
+    description: zod.ZodOptional<zod.ZodString>;
+    schema: zod.ZodRecord<zod.ZodString, zod.ZodUnknown>;
+    data_example: zod.ZodOptional<zod.ZodRecord<zod.ZodString, zod.ZodUnknown>>;
+}, zod.z.core.$strict>;
+export type CreateEventRequest = zod.input<typeof CreateEventRequest>;
+export type CreateEventRequestOutput = zod.output<typeof CreateEventRequest>;

package/dist/eventbus/v1/generated/validators/createEventRequest.zod.js

@@ -0,0 +1,59 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Event Bus API
+ * Event definitions, versions, publishing, and realtime access.
+ *
+ * ## 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.
+ *
+ * ## Definitions and messages
+ *
+ * An event is a definition: a name, a description, and one or more versions. A version carries a
+ * JSON Schema that every published payload must satisfy. Messages are not stored here and are
+ * not part of the event definition.
+ *
+ * A project event belongs to the current project. A global event has no `project_id`; it is
+ * defined by a platform service and is read-only in this API. Global events are listed alongside
+ * the project's own events.
+ *
+ * A version number never changes meaning. Adding optional properties is allowed within a version;
+ * a breaking change creates a new version. Publishing without a version uses the highest active
+ * version.
+ *
+ * ## Publishing
+ *
+ * Publishing returns the identity of the message and does not wait for consumers. Messages are
+ * not stored and are not replayed: a consumer that connects later does not receive earlier
+ * messages. Consumers receive messages through the realtime API or the platform's service API.
+ *
+ * ## Realtime
+ *
+ * Create a ticket, connect to the returned URL with the ticket, and authenticate the connection
+ * with a scoped token. A ticket is single-use and short-lived. The connection ends when the
+ * token expires unless it is refreshed with a new scoped token for the same user and project.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export const createEventRequestNameMax = 128;
+export const createEventRequestNameRegExp = new RegExp("^[a-z](?:[a-z0-9_]*[a-z0-9])?(?:\\.[a-z](?:[a-z0-9_]*[a-z0-9])?){2,}$");
+export const createEventRequestDescriptionMax = 1024;
+export const CreateEventRequest = zod.strictObject({
+    name: zod
+        .string()
+        .max(createEventRequestNameMax)
+        .regex(createEventRequestNameRegExp)
+        .describe("The full event name; its first segment is the namespace"),
+    description: zod
+        .string()
+        .max(createEventRequestDescriptionMax)
+        .optional()
+        .describe("What the event means, for developers"),
+    schema: zod.record(zod.string(), zod.unknown()).describe("The JSON Schema for version 1"),
+    data_example: zod
+        .record(zod.string(), zod.unknown())
+        .optional()
+        .describe("An example payload that satisfies the schema"),
+});

package/dist/eventbus/v1/generated/validators/createVersionRequest.zod.d.ts

@@ -0,0 +1,46 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Event Bus API
+ * Event definitions, versions, publishing, and realtime access.
+ *
+ * ## 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.
+ *
+ * ## Definitions and messages
+ *
+ * An event is a definition: a name, a description, and one or more versions. A version carries a
+ * JSON Schema that every published payload must satisfy. Messages are not stored here and are
+ * not part of the event definition.
+ *
+ * A project event belongs to the current project. A global event has no `project_id`; it is
+ * defined by a platform service and is read-only in this API. Global events are listed alongside
+ * the project's own events.
+ *
+ * A version number never changes meaning. Adding optional properties is allowed within a version;
+ * a breaking change creates a new version. Publishing without a version uses the highest active
+ * version.
+ *
+ * ## Publishing
+ *
+ * Publishing returns the identity of the message and does not wait for consumers. Messages are
+ * not stored and are not replayed: a consumer that connects later does not receive earlier
+ * messages. Consumers receive messages through the realtime API or the platform's service API.
+ *
+ * ## Realtime
+ *
+ * Create a ticket, connect to the returned URL with the ticket, and authenticate the connection
+ * with a scoped token. A ticket is single-use and short-lived. The connection ends when the
+ * token expires unless it is refreshed with a new scoped token for the same user and project.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export declare const CreateVersionRequest: zod.ZodObject<{
+    version: zod.ZodInt;
+    schema: zod.ZodRecord<zod.ZodString, zod.ZodUnknown>;
+    data_example: zod.ZodOptional<zod.ZodRecord<zod.ZodString, zod.ZodUnknown>>;
+}, zod.z.core.$strict>;
+export type CreateVersionRequest = zod.input<typeof CreateVersionRequest>;
+export type CreateVersionRequestOutput = zod.output<typeof CreateVersionRequest>;

package/dist/eventbus/v1/generated/validators/createVersionRequest.zod.js

@@ -0,0 +1,47 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Event Bus API
+ * Event definitions, versions, publishing, and realtime access.
+ *
+ * ## 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.
+ *
+ * ## Definitions and messages
+ *
+ * An event is a definition: a name, a description, and one or more versions. A version carries a
+ * JSON Schema that every published payload must satisfy. Messages are not stored here and are
+ * not part of the event definition.
+ *
+ * A project event belongs to the current project. A global event has no `project_id`; it is
+ * defined by a platform service and is read-only in this API. Global events are listed alongside
+ * the project's own events.
+ *
+ * A version number never changes meaning. Adding optional properties is allowed within a version;
+ * a breaking change creates a new version. Publishing without a version uses the highest active
+ * version.
+ *
+ * ## Publishing
+ *
+ * Publishing returns the identity of the message and does not wait for consumers. Messages are
+ * not stored and are not replayed: a consumer that connects later does not receive earlier
+ * messages. Consumers receive messages through the realtime API or the platform's service API.
+ *
+ * ## Realtime
+ *
+ * Create a ticket, connect to the returned URL with the ticket, and authenticate the connection
+ * with a scoped token. A ticket is single-use and short-lived. The connection ends when the
+ * token expires unless it is refreshed with a new scoped token for the same user and project.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export const CreateVersionRequest = zod.strictObject({
+    version: zod.int().min(1).describe("The new version number, greater than every existing version"),
+    schema: zod.record(zod.string(), zod.unknown()).describe("The JSON Schema for this version"),
+    data_example: zod
+        .record(zod.string(), zod.unknown())
+        .optional()
+        .describe("An example payload that satisfies the schema"),
+});

package/dist/eventbus/v1/generated/validators/cursorPagination.zod.d.ts

@@ -0,0 +1,45 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Event Bus API
+ * Event definitions, versions, publishing, and realtime access.
+ *
+ * ## 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.
+ *
+ * ## Definitions and messages
+ *
+ * An event is a definition: a name, a description, and one or more versions. A version carries a
+ * JSON Schema that every published payload must satisfy. Messages are not stored here and are
+ * not part of the event definition.
+ *
+ * A project event belongs to the current project. A global event has no `project_id`; it is
+ * defined by a platform service and is read-only in this API. Global events are listed alongside
+ * the project's own events.
+ *
+ * A version number never changes meaning. Adding optional properties is allowed within a version;
+ * a breaking change creates a new version. Publishing without a version uses the highest active
+ * version.
+ *
+ * ## Publishing
+ *
+ * Publishing returns the identity of the message and does not wait for consumers. Messages are
+ * not stored and are not replayed: a consumer that connects later does not receive earlier
+ * messages. Consumers receive messages through the realtime API or the platform's service API.
+ *
+ * ## Realtime
+ *
+ * Create a ticket, connect to the returned URL with the ticket, and authenticate the connection
+ * with a scoped token. A ticket is single-use and short-lived. The connection ends when the
+ * token expires unless it is refreshed with a new scoped token for the same user and project.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export declare const CursorPagination: zod.ZodObject<{
+    page_size: zod.ZodInt;
+    next_cursor: zod.ZodOptional<zod.ZodNullable<zod.ZodString>>;
+}, zod.z.core.$strict>;
+export type CursorPagination = zod.input<typeof CursorPagination>;
+export type CursorPaginationOutput = zod.output<typeof CursorPagination>;

package/dist/eventbus/v1/generated/validators/cursorPagination.zod.js

@@ -0,0 +1,45 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Event Bus API
+ * Event definitions, versions, publishing, and realtime access.
+ *
+ * ## 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.
+ *
+ * ## Definitions and messages
+ *
+ * An event is a definition: a name, a description, and one or more versions. A version carries a
+ * JSON Schema that every published payload must satisfy. Messages are not stored here and are
+ * not part of the event definition.
+ *
+ * A project event belongs to the current project. A global event has no `project_id`; it is
+ * defined by a platform service and is read-only in this API. Global events are listed alongside
+ * the project's own events.
+ *
+ * A version number never changes meaning. Adding optional properties is allowed within a version;
+ * a breaking change creates a new version. Publishing without a version uses the highest active
+ * version.
+ *
+ * ## Publishing
+ *
+ * Publishing returns the identity of the message and does not wait for consumers. Messages are
+ * not stored and are not replayed: a consumer that connects later does not receive earlier
+ * messages. Consumers receive messages through the realtime API or the platform's service API.
+ *
+ * ## Realtime
+ *
+ * Create a ticket, connect to the returned URL with the ticket, and authenticate the connection
+ * with a scoped token. A ticket is single-use and short-lived. The connection ends when the
+ * token expires unless it is refreshed with a new scoped token for the same user and project.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export const CursorPagination = zod
+    .strictObject({
+    page_size: zod.int().min(1),
+    next_cursor: zod.string().nullish(),
+})
+    .describe("Pagination metadata for keyset traversal. Pass next_cursor as cursor to read the following page; null means there is no following page.");

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

@@ -0,0 +1,56 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Event Bus API
+ * Event definitions, versions, publishing, and realtime access.
+ *
+ * ## 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.
+ *
+ * ## Definitions and messages
+ *
+ * An event is a definition: a name, a description, and one or more versions. A version carries a
+ * JSON Schema that every published payload must satisfy. Messages are not stored here and are
+ * not part of the event definition.
+ *
+ * A project event belongs to the current project. A global event has no `project_id`; it is
+ * defined by a platform service and is read-only in this API. Global events are listed alongside
+ * the project's own events.
+ *
+ * A version number never changes meaning. Adding optional properties is allowed within a version;
+ * a breaking change creates a new version. Publishing without a version uses the highest active
+ * version.
+ *
+ * ## Publishing
+ *
+ * Publishing returns the identity of the message and does not wait for consumers. Messages are
+ * not stored and are not replayed: a consumer that connects later does not receive earlier
+ * messages. Consumers receive messages through the realtime API or the platform's service API.
+ *
+ * ## Realtime
+ *
+ * Create a ticket, connect to the returned URL with the ticket, and authenticate the connection
+ * with a scoped token. A ticket is single-use and short-lived. The connection ends when the
+ * token expires unless it is refreshed with a new scoped token for the same user and project.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export declare const Error: zod.ZodObject<{
+    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/eventbus/v1/generated/validators/error.zod.js

@@ -0,0 +1,45 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Event Bus API
+ * Event definitions, versions, publishing, and realtime access.
+ *
+ * ## 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.
+ *
+ * ## Definitions and messages
+ *
+ * An event is a definition: a name, a description, and one or more versions. A version carries a
+ * JSON Schema that every published payload must satisfy. Messages are not stored here and are
+ * not part of the event definition.
+ *
+ * A project event belongs to the current project. A global event has no `project_id`; it is
+ * defined by a platform service and is read-only in this API. Global events are listed alongside
+ * the project's own events.
+ *
+ * A version number never changes meaning. Adding optional properties is allowed within a version;
+ * a breaking change creates a new version. Publishing without a version uses the highest active
+ * version.
+ *
+ * ## Publishing
+ *
+ * Publishing returns the identity of the message and does not wait for consumers. Messages are
+ * not stored and are not replayed: a consumer that connects later does not receive earlier
+ * messages. Consumers receive messages through the realtime API or the platform's service API.
+ *
+ * ## Realtime
+ *
+ * Create a ticket, connect to the returned URL with the ticket, and authenticate the connection
+ * with a scoped token. A ticket is single-use and short-lived. The connection ends when the
+ * token expires unless it is refreshed with a new scoped token for the same user and project.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+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/eventbus/v1/generated/validators/errorStatus.zod.d.ts

@@ -0,0 +1,54 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Event Bus API
+ * Event definitions, versions, publishing, and realtime access.
+ *
+ * ## 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.
+ *
+ * ## Definitions and messages
+ *
+ * An event is a definition: a name, a description, and one or more versions. A version carries a
+ * JSON Schema that every published payload must satisfy. Messages are not stored here and are
+ * not part of the event definition.
+ *
+ * A project event belongs to the current project. A global event has no `project_id`; it is
+ * defined by a platform service and is read-only in this API. Global events are listed alongside
+ * the project's own events.
+ *
+ * A version number never changes meaning. Adding optional properties is allowed within a version;
+ * a breaking change creates a new version. Publishing without a version uses the highest active
+ * version.
+ *
+ * ## Publishing
+ *
+ * Publishing returns the identity of the message and does not wait for consumers. Messages are
+ * not stored and are not replayed: a consumer that connects later does not receive earlier
+ * messages. Consumers receive messages through the realtime API or the platform's service API.
+ *
+ * ## Realtime
+ *
+ * Create a ticket, connect to the returned URL with the ticket, and authenticate the connection
+ * with a scoped token. A ticket is single-use and short-lived. The connection ends when the
+ * token expires unless it is refreshed with a new scoped token for the same user and project.
+ * 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/eventbus/v1/generated/validators/errorStatus.zod.js

@@ -0,0 +1,69 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Event Bus API
+ * Event definitions, versions, publishing, and realtime access.
+ *
+ * ## 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.
+ *
+ * ## Definitions and messages
+ *
+ * An event is a definition: a name, a description, and one or more versions. A version carries a
+ * JSON Schema that every published payload must satisfy. Messages are not stored here and are
+ * not part of the event definition.
+ *
+ * A project event belongs to the current project. A global event has no `project_id`; it is
+ * defined by a platform service and is read-only in this API. Global events are listed alongside
+ * the project's own events.
+ *
+ * A version number never changes meaning. Adding optional properties is allowed within a version;
+ * a breaking change creates a new version. Publishing without a version uses the highest active
+ * version.
+ *
+ * ## Publishing
+ *
+ * Publishing returns the identity of the message and does not wait for consumers. Messages are
+ * not stored and are not replayed: a consumer that connects later does not receive earlier
+ * messages. Consumers receive messages through the realtime API or the platform's service API.
+ *
+ * ## Realtime
+ *
+ * Create a ticket, connect to the returned URL with the ticket, and authenticate the connection
+ * with a scoped token. A ticket is single-use and short-lived. The connection ends when the
+ * token expires unless it is refreshed with a new scoped token for the same user and project.
+ * 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/eventbus/v1/generated/validators/eventDetail.zod.d.ts

@@ -0,0 +1,65 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Event Bus API
+ * Event definitions, versions, publishing, and realtime access.
+ *
+ * ## 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.
+ *
+ * ## Definitions and messages
+ *
+ * An event is a definition: a name, a description, and one or more versions. A version carries a
+ * JSON Schema that every published payload must satisfy. Messages are not stored here and are
+ * not part of the event definition.
+ *
+ * A project event belongs to the current project. A global event has no `project_id`; it is
+ * defined by a platform service and is read-only in this API. Global events are listed alongside
+ * the project's own events.
+ *
+ * A version number never changes meaning. Adding optional properties is allowed within a version;
+ * a breaking change creates a new version. Publishing without a version uses the highest active
+ * version.
+ *
+ * ## Publishing
+ *
+ * Publishing returns the identity of the message and does not wait for consumers. Messages are
+ * not stored and are not replayed: a consumer that connects later does not receive earlier
+ * messages. Consumers receive messages through the realtime API or the platform's service API.
+ *
+ * ## Realtime
+ *
+ * Create a ticket, connect to the returned URL with the ticket, and authenticate the connection
+ * with a scoped token. A ticket is single-use and short-lived. The connection ends when the
+ * token expires unless it is refreshed with a new scoped token for the same user and project.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export declare const eventDetailNameMax = 128;
+export declare const eventDetailDescriptionMax = 1024;
+export declare const eventDetailTagsItemMax = 64;
+export declare const EventDetail: zod.ZodObject<{
+    name: zod.ZodString;
+    project_id: zod.ZodOptional<zod.ZodNullable<zod.ZodUUID>>;
+    description: zod.ZodString;
+    status: zod.ZodEnum<{
+        active: "active";
+        archived: "archived";
+    }>;
+    tags: zod.ZodOptional<zod.ZodArray<zod.ZodString>>;
+    latest_version: zod.ZodOptional<zod.ZodInt>;
+    versions: zod.ZodArray<zod.ZodObject<{
+        version: zod.ZodInt;
+        schema: zod.ZodRecord<zod.ZodString, zod.ZodUnknown>;
+        data_example: zod.ZodOptional<zod.ZodRecord<zod.ZodString, zod.ZodUnknown>>;
+        status: zod.ZodEnum<{
+            active: "active";
+            archived: "archived";
+        }>;
+        schema_hash: zod.ZodString;
+    }, zod.z.core.$strict>>;
+}, zod.z.core.$strict>;
+export type EventDetail = zod.input<typeof EventDetail>;
+export type EventDetailOutput = zod.output<typeof EventDetail>;

package/dist/eventbus/v1/generated/validators/eventDetail.zod.js

@@ -0,0 +1,62 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Event Bus API
+ * Event definitions, versions, publishing, and realtime access.
+ *
+ * ## 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.
+ *
+ * ## Definitions and messages
+ *
+ * An event is a definition: a name, a description, and one or more versions. A version carries a
+ * JSON Schema that every published payload must satisfy. Messages are not stored here and are
+ * not part of the event definition.
+ *
+ * A project event belongs to the current project. A global event has no `project_id`; it is
+ * defined by a platform service and is read-only in this API. Global events are listed alongside
+ * the project's own events.
+ *
+ * A version number never changes meaning. Adding optional properties is allowed within a version;
+ * a breaking change creates a new version. Publishing without a version uses the highest active
+ * version.
+ *
+ * ## Publishing
+ *
+ * Publishing returns the identity of the message and does not wait for consumers. Messages are
+ * not stored and are not replayed: a consumer that connects later does not receive earlier
+ * messages. Consumers receive messages through the realtime API or the platform's service API.
+ *
+ * ## Realtime
+ *
+ * Create a ticket, connect to the returned URL with the ticket, and authenticate the connection
+ * with a scoped token. A ticket is single-use and short-lived. The connection ends when the
+ * token expires unless it is refreshed with a new scoped token for the same user and project.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+import { EventStatus } from "./eventStatus.zod.js";
+import { EventVersion } from "./eventVersion.zod.js";
+export const eventDetailNameMax = 128;
+export const eventDetailDescriptionMax = 1024;
+export const eventDetailTagsItemMax = 64;
+export const EventDetail = zod.strictObject({
+    name: zod.string().max(eventDetailNameMax).describe("The full event name"),
+    project_id: zod.uuid().nullish().describe("The owning project; absent for a global event"),
+    description: zod
+        .string()
+        .max(eventDetailDescriptionMax)
+        .describe("What the event means, for developers"),
+    status: EventStatus,
+    tags: zod
+        .array(zod.string().max(eventDetailTagsItemMax))
+        .optional()
+        .describe("Free-form labels for grouping"),
+    latest_version: zod
+        .int()
+        .optional()
+        .describe("The highest active version; absent when the event has none"),
+    versions: zod.array(EventVersion).describe("Every version, newest first"),
+});