@hey-api/openapi-ts 0.53.11 → 0.54.0

package/dist/index.d.cts

@@ -1,722 +1,471 @@
-interface Dictionary<T = unknown> {
-    [key: string]: T;
-}
+type PluginNames =
+  | '@hey-api/schemas'
+  | '@hey-api/services'
+  | '@hey-api/transformers'
+  | '@hey-api/types'
+  | '@tanstack/react-query'
+  | '@tanstack/solid-query'
+  | '@tanstack/svelte-query'
+  | '@tanstack/vue-query'
+  | 'zod';
 
-/**
- * {@link} https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#reference-object
- */
-interface OpenApiReference$1 {
-    $ref?: string;
+interface PluginName<Name extends PluginNames> {
+  name: Name;
 }
 
-/**
- * {@link} https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#example-object
- */
-interface OpenApiExample extends OpenApiReference$1 {
-    description?: string;
-    externalValue?: string;
-    summary?: string;
-    value?: unknown;
+interface CommonConfig {
+  name: PluginNames;
+  output?: string;
 }
 
-interface WithEnumExtension {
-    'x-enum-descriptions'?: ReadonlyArray<string>;
-    'x-enum-varnames'?: ReadonlyArray<string>;
-    'x-enumNames'?: ReadonlyArray<string>;
-}
+type UserConfig$1<Config extends CommonConfig> = Omit<Config, 'output'>;
 
-/**
- * {@link} https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#discriminator-object
- */
-interface OpenApiDiscriminator {
-    mapping?: Dictionary<string>;
-    propertyName: string;
+interface EnumExtensions {
+  /**
+   * `x-enum-descriptions` are {@link https://stackoverflow.com/a/66471626 supported} by OpenAPI Generator.
+   */
+  'x-enum-descriptions'?: ReadonlyArray<string>;
+  /**
+   * `x-enum-varnames` are {@link https://stackoverflow.com/a/66471626 supported} by OpenAPI Generator.
+   */
+  'x-enum-varnames'?: ReadonlyArray<string>;
+  /**
+   * {@link https://github.com/RicoSuter/NSwag NSwag} generates `x-enumNames` field containing custom enum names.
+   */
+  'x-enumNames'?: ReadonlyArray<string>;
 }
 
-/**
- * {@link} https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#external-documentation-object
- */
-interface OpenApiExternalDocs$1 {
-    description?: string;
-    url: string;
+interface OpenApiSchemaExtensions {
+  /**
+   * Adds support for polymorphism. The discriminator is an object name that is used to differentiate between other schemas which may satisfy the payload description. See {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#composition-and-inheritance-polymorphism Composition and Inheritance} for more details.
+   */
+  discriminator?: DiscriminatorObject;
+  /**
+   * A free-form property to include an example of an instance for this schema. To represent examples that cannot be naturally represented in JSON or YAML, a string value can be used to contain the example with escaping where necessary.
+   *
+   * **Deprecated**: The `example` property has been deprecated in favor of the JSON Schema `examples` keyword. Use of `example` is discouraged, and later versions of this specification may remove it.
+   */
+  example?: unknown;
+  /**
+   * Additional external documentation for this schema.
+   */
+  externalDocs?: ExternalDocumentationObject;
+  /**
+   * This MAY be used only on properties schemas. It has no effect on root schemas. Adds additional metadata to describe the XML representation of this property.
+   */
+  xml?: XMLObject;
 }
 
-/**
- * {@link} https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#xml-object
- */
-interface OpenApiXml$1 {
-    attribute?: boolean;
-    name?: string;
-    namespace?: string;
-    prefix?: string;
-    wrapped?: boolean;
+// TODO: left out some keywords related to structuring a complex schema and declaring a dialect
+interface JsonSchemaDraft2020_12
+  extends ArrayKeywords,
+    NumberKeywords,
+    ObjectKeywords,
+    StringKeywords,
+    EnumExtensions,
+    OpenApiSchemaExtensions {
+  /**
+   * The `$comment` {@link https://json-schema.org/learn/glossary#keyword keyword} is strictly intended for adding comments to a schema. Its value must always be a string. Unlike the annotations `title`, `description`, and `examples`, JSON schema {@link https://json-schema.org/learn/glossary#implementation implementations} aren't allowed to attach any meaning or behavior to it whatsoever, and may even strip them at any time. Therefore, they are useful for leaving notes to future editors of a JSON schema, but should not be used to communicate to users of the schema.
+   */
+  $comment?: string;
+  /**
+   * A schema can reference another schema using the `$ref` keyword. The value of `$ref` is a URI-reference that is resolved against the schema's {@link https://json-schema.org/understanding-json-schema/structuring#base-uri Base URI}. When evaluating a `$ref`, an implementation uses the resolved identifier to retrieve the referenced schema and applies that schema to the {@link https://json-schema.org/learn/glossary#instance instance}.
+   *
+   * The `$ref` keyword may be used to create recursive schemas that refer to themselves.
+   */
+  $ref?: string;
+  /**
+   * `allOf`: (AND) Must be valid against _all_ of the {@link https://json-schema.org/learn/glossary#subschema subschemas}
+   *
+   * To validate against `allOf`, the given data must be valid against all of the given subschemas.
+   *
+   * {@link https://json-schema.org/understanding-json-schema/reference/combining#allof allOf} can not be used to "extend" a schema to add more details to it in the sense of object-oriented inheritance. {@link https://json-schema.org/learn/glossary#instance Instances} must independently be valid against "all of" the schemas in the `allOf`. See the section on {@link https://json-schema.org/understanding-json-schema/reference/object#extending Extending Closed Schemas} for more information.
+   */
+  allOf?: ReadonlyArray<JsonSchemaDraft2020_12>;
+  /**
+   * `anyOf`: (OR) Must be valid against _any_ of the subschemas
+   *
+   * To validate against `anyOf`, the given data must be valid against any (one or more) of the given subschemas.
+   */
+  anyOf?: ReadonlyArray<JsonSchemaDraft2020_12>;
+  /**
+   * The `const` keyword is used to restrict a value to a single value.
+   */
+  const?: unknown;
+  /**
+   * The `contentEncoding` keyword specifies the encoding used to store the contents, as specified in {@link https://tools.ietf.org/html/rfc2045 RFC 2054, part 6.1} and {@link https://datatracker.ietf.org/doc/html/rfc4648 RFC 4648}.
+   *
+   * The acceptable values are `quoted-printable`, `base16`, `base32`, and `base64`. If not specified, the encoding is the same as the containing JSON document.
+   *
+   * Without getting into the low-level details of each of these encodings, there are really only two options useful for modern usage:
+   * - If the content is encoded in the same encoding as the enclosing JSON document (which for practical purposes, is almost always UTF-8), leave `contentEncoding` unspecified, and include the content in a string as-is. This includes text-based content types, such as `text/html` or `application/xml`.
+   * - If the content is binary data, set `contentEncoding` to `base64` and encode the contents using {@link https://tools.ietf.org/html/rfc4648 Base64}. This would include many image types, such as `image/png` or audio types, such as `audio/mpeg`.
+   */
+  contentEncoding?: 'base16' | 'base32' | 'base64' | 'quoted-printable';
+  /**
+   * The `contentMediaType` keyword specifies the MIME type of the contents of a string, as described in {@link https://tools.ietf.org/html/rfc2046 RFC 2046}. There is a list of {@link http://www.iana.org/assignments/media-types/media-types.xhtml MIME types officially registered by the IANA}, but the set of types supported will be application and operating system dependent. Mozilla Developer Network also maintains a {@link https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types/Complete_list_of_MIME_types shorter list of MIME types that are important for the web}
+   */
+  contentMediaType?: string;
+  /**
+   * The `default` keyword specifies a default value. This value is not used to fill in missing values during the validation process. Non-validation tools such as documentation generators or form generators may use this value to give hints to users about how to use a value. However, `default` is typically used to express that if a value is missing, then the value is semantically the same as if the value was present with the default value. The value of `default` should validate against the schema in which it resides, but that isn't required.
+   */
+  default?: unknown;
+  /**
+   * The `dependentRequired` {@link https://json-schema.org/learn/glossary#keyword keyword} conditionally requires that certain properties must be present if a given property is present in an object. For example, suppose we have a {@link https://json-schema.org/learn/glossary#schema schema} representing a customer. If you have their credit card number, you also want to ensure you have a billing address. If you don't have their credit card number, a billing address would not be required. We represent this dependency of one property on another using the `dependentRequired` keyword. The value of the `dependentRequired` keyword is an object. Each entry in the object maps from the name of a property, _p_, to an array of strings listing properties that are required if _p_ is present.
+   */
+  dependentRequired?: Record<string, ReadonlyArray<string>>;
+  /**
+   * The `dependentSchemas` keyword conditionally applies a {@link https://json-schema.org/learn/glossary#subschema subschema} when a given property is present. This schema is applied in the same way {@link https://json-schema.org/understanding-json-schema/reference/combining#allof allOf} applies schemas. Nothing is merged or extended. Both schemas apply independently.
+   */
+  dependentSchemas?: Record<string, JsonSchemaDraft2020_12>;
+  /**
+   * The `deprecated` keyword is a boolean that indicates that the {@link https://json-schema.org/learn/glossary#instance instance} value the keyword applies to should not be used and may be removed in the future.
+   */
+  deprecated?: boolean;
+  /**
+   * The `title` and `description` keywords must be strings. A "title" will preferably be short, whereas a "description" will provide a more lengthy explanation about the purpose of the data described by the schema.
+   */
+  description?: string;
+  /**
+   * The `if`, `then` and `else` keywords allow the application of a subschema based on the outcome of another schema, much like the `if`/`then`/`else` constructs you've probably seen in traditional programming languages.
+   *
+   * If `if` is valid, `then` must also be valid (and `else` is ignored.) If `if` is invalid, `else` must also be valid (and `then` is ignored).
+   *
+   * If `then` or `else` is not defined, `if` behaves as if they have a value of `true`.
+   *
+   * If `then` and/or `else` appear in a schema without `if`, `then` and `else` are ignored.
+   */
+  else?: JsonSchemaDraft2020_12;
+  /**
+   * The `enum` {@link https://json-schema.org/learn/glossary#keyword keyword} is used to restrict a value to a fixed set of values. It must be an array with at least one element, where each element is unique.
+   *
+   * You can use `enum` even without a type, to accept values of different types.
+   */
+  enum?: ReadonlyArray<unknown>;
+  /**
+   * The `examples` keyword is a place to provide an array of examples that validate against the schema. This isn't used for validation, but may help with explaining the effect and purpose of the schema to a reader. Each entry should validate against the schema in which it resides, but that isn't strictly required. There is no need to duplicate the `default` value in the `examples` array, since `default` will be treated as another example.
+   */
+  examples?: ReadonlyArray<unknown>;
+  /**
+   * The `format` keyword allows for basic semantic identification of certain kinds of string values that are commonly used. For example, because JSON doesn't have a "DateTime" type, dates need to be encoded as strings. `format` allows the schema author to indicate that the string value should be interpreted as a date. By default, `format` is just an annotation and does not effect validation.
+   *
+   * Optionally, validator {@link https://json-schema.org/learn/glossary#implementation implementations} can provide a configuration option to enable `format` to function as an assertion rather than just an annotation. That means that validation will fail if, for example, a value with a `date` format isn't in a form that can be parsed as a date. This can allow values to be constrained beyond what the other tools in JSON Schema, including {@link https://json-schema.org/understanding-json-schema/reference/regular_expressions Regular Expressions} can do.
+   *
+   * There is a bias toward networking-related formats in the JSON Schema specification, most likely due to its heritage in web technologies. However, custom formats may also be used, as long as the parties exchanging the JSON documents also exchange information about the custom format types. A JSON Schema validator will ignore any format type that it does not understand.
+   */
+  format?: JsonSchemaFormats;
+  /**
+   * The `if`, `then` and `else` keywords allow the application of a subschema based on the outcome of another schema, much like the `if`/`then`/`else` constructs you've probably seen in traditional programming languages.
+   *
+   * If `if` is valid, `then` must also be valid (and `else` is ignored.) If `if` is invalid, `else` must also be valid (and `then` is ignored).
+   *
+   * If `then` or `else` is not defined, `if` behaves as if they have a value of `true`.
+   *
+   * If `then` and/or `else` appear in a schema without `if`, `then` and `else` are ignored.
+   */
+  if?: JsonSchemaDraft2020_12;
+  /**
+   * `not`: (NOT) Must _not_ be valid against the given schema
+   *
+   * The `not` keyword declares that an instance validates if it doesn't validate against the given subschema.
+   */
+  not?: JsonSchemaDraft2020_12;
+  /**
+   * `oneOf`: (XOR) Must be valid against _exactly one_ of the subschemas
+   *
+   * To validate against `oneOf`, the given data must be valid against exactly one of the given subschemas.
+   *
+   * Careful consideration should be taken when using `oneOf` entries as the nature of it requires verification of _every_ sub-schema which can lead to increased processing times. Prefer `anyOf` where possible.
+   */
+  oneOf?: ReadonlyArray<JsonSchemaDraft2020_12>;
+  /**
+   * The boolean keywords `readOnly` and `writeOnly` are typically used in an API context. `readOnly` indicates that a value should not be modified. It could be used to indicate that a `PUT` request that changes a value would result in a `400 Bad Request` response. `writeOnly` indicates that a value may be set, but will remain hidden. In could be used to indicate you can set a value with a `PUT` request, but it would not be included when retrieving that record with a `GET` request.
+   */
+  readOnly?: boolean;
+  /**
+   * The `if`, `then` and `else` keywords allow the application of a subschema based on the outcome of another schema, much like the `if`/`then`/`else` constructs you've probably seen in traditional programming languages.
+   *
+   * If `if` is valid, `then` must also be valid (and `else` is ignored.) If `if` is invalid, `else` must also be valid (and `then` is ignored).
+   *
+   * If `then` or `else` is not defined, `if` behaves as if they have a value of `true`.
+   *
+   * If `then` and/or `else` appear in a schema without `if`, `then` and `else` are ignored.
+   */
+  then?: JsonSchemaDraft2020_12;
+  /**
+   * The `title` and `description` keywords must be strings. A "title" will preferably be short, whereas a "description" will provide a more lengthy explanation about the purpose of the data described by the schema.
+   */
+  title?: string;
+  /**
+   * If it is an array, it must be an array of strings, where each string is the name of one of the basic types, and each element is unique. In this case, the JSON snippet is valid if it matches any of the given types.
+   */
+  type?: JsonSchemaTypes | ReadonlyArray<JsonSchemaTypes>;
+  /**
+   * The boolean keywords `readOnly` and `writeOnly` are typically used in an API context. `readOnly` indicates that a value should not be modified. It could be used to indicate that a `PUT` request that changes a value would result in a `400 Bad Request` response. `writeOnly` indicates that a value may be set, but will remain hidden. In could be used to indicate you can set a value with a `PUT` request, but it would not be included when retrieving that record with a `GET` request.
+   */
+  writeOnly?: boolean;
 }
 
-/**
- * {@link} https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#schema-object
- */
-interface OpenApiSchema$1 extends OpenApiReference$1, WithEnumExtension {
-    additionalProperties?: boolean | OpenApiSchema$1;
-    allOf?: OpenApiSchema$1[];
-    anyOf?: OpenApiSchema$1[];
-    const?: string | number | boolean | null;
-    default?: unknown;
-    deprecated?: boolean;
-    description?: string;
-    discriminator?: OpenApiDiscriminator;
-    enum?: (string | number)[];
-    example?: unknown;
-    exclusiveMaximum?: boolean;
-    exclusiveMinimum?: boolean;
-    externalDocs?: OpenApiExternalDocs$1;
-    format?: 'binary' | 'boolean' | 'byte' | 'date-time' | 'date' | 'double' | 'float' | 'int32' | 'int64' | 'password' | 'string';
-    items?: OpenApiSchema$1;
-    maxItems?: number;
-    maxLength?: number;
-    maxProperties?: number;
-    maximum?: number;
-    minItems?: number;
-    minLength?: number;
-    minProperties?: number;
-    minimum?: number;
-    multipleOf?: number;
-    not?: OpenApiSchema$1[];
-    nullable?: boolean;
-    oneOf?: OpenApiSchema$1[];
-    pattern?: string;
-    prefixItems?: OpenApiSchema$1[];
-    properties?: Dictionary<OpenApiSchema$1>;
-    readOnly?: boolean;
-    required?: string[];
-    title?: string;
-    type?: string | string[];
-    uniqueItems?: boolean;
-    writeOnly?: boolean;
-    xml?: OpenApiXml$1;
+interface ArrayKeywords {
+  /**
+   * While the `items` schema must be valid for every item in the array, the `contains` schema only needs to validate against one or more items in the array.
+   */
+  contains?: JsonSchemaDraft2020_12;
+  /**
+   * List validation is useful for arrays of arbitrary length where each item matches the same schema. For this kind of array, set the `items` {@link https://json-schema.org/learn/glossary#keyword keyword} to a single schema that will be used to validate all of the items in the array.
+   *
+   * The `items` keyword can be used to control whether it's valid to have additional items in a tuple beyond what is defined in `prefixItems`. The value of the `items` keyword is a schema that all additional items must pass in order for the keyword to validate.
+   *
+   * Note that `items` doesn't "see inside" any {@link https://json-schema.org/learn/glossary#instance instances} of `allOf`, `anyOf`, or `oneOf` in the same {@link https://json-schema.org/learn/glossary#subschema subschema}.
+   */
+  items?: JsonSchemaDraft2020_12 | false;
+  /**
+   * `minContains` and `maxContains` can be used with `contains` to further specify how many times a schema matches a `contains` constraint. These keywords can be any non-negative number including zero.
+   */
+  maxContains?: number;
+  /**
+   * The length of the array can be specified using the `minItems` and `maxItems` keywords. The value of each keyword must be a non-negative number. These keywords work whether doing {@link https://json-schema.org/understanding-json-schema/reference/array#items list validation} or {@link https://json-schema.org/understanding-json-schema/reference/array#tupleValidation tuple-validation}.
+   */
+  maxItems?: number;
+  /**
+   * `minContains` and `maxContains` can be used with `contains` to further specify how many times a schema matches a `contains` constraint. These keywords can be any non-negative number including zero.
+   */
+  minContains?: number;
+  /**
+   * The length of the array can be specified using the `minItems` and `maxItems` keywords. The value of each keyword must be a non-negative number. These keywords work whether doing {@link https://json-schema.org/understanding-json-schema/reference/array#items list validation} or {@link https://json-schema.org/understanding-json-schema/reference/array#tupleValidation tuple-validation}.
+   */
+  minItems?: number;
+  /**
+   * `prefixItems` is an array, where each item is a schema that corresponds to each index of the document's array. That is, an array where the first element validates the first element of the input array, the second element validates the second element of the input array, etc.
+   */
+  prefixItems?: ReadonlyArray<JsonSchemaDraft2020_12>;
+  /**
+   * The `unevaluatedItems` keyword is useful mainly when you want to add or disallow extra items to an array.
+   *
+   * `unevaluatedItems` applies to any values not evaluated by an `items`, `prefixItems`, or `contains` keyword. Just as `unevaluatedProperties` affects only properties in an object, `unevaluatedItems` affects only items in an array.
+   *
+   * Watch out! The word "unevaluated" _does not mean_ "not evaluated by `items`, `prefixItems`, or `contains`." "Unevaluated" means "not successfully evaluated", or "does not evaluate to true".
+   *
+   * Like with `items`, if you set `unevaluatedItems` to false, you can disallow extra items in the array.
+   */
+  unevaluatedItems?: JsonSchemaDraft2020_12 | false;
+  /**
+   * A schema can ensure that each of the items in an array is unique. Simply set the `uniqueItems` keyword to `true`.
+   */
+  uniqueItems?: boolean;
 }
 
-/**
- * add only one type for now as that's needed to resolve the reported issue,
- * more types should be added though
- * {@link https://github.com/hey-api/openapi-ts/issues/612}
- */
-type MediaType = 'application/json';
-/**
- * encoding interface should be added, not adding it for now as it's not needed
- * to resolve the issue reported
- * {@link https://github.com/hey-api/openapi-ts/issues/612}
- */
-interface MediaTypeObject$1 {
-    example?: unknown;
-    examples?: Dictionary<OpenApiExample>;
-    schema: OpenApiSchema$1;
-}
-/**
- * {@link} https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#parameter-object
- */
-interface OpenApiParameter extends OpenApiReference$1 {
-    allowEmptyValue?: boolean;
-    allowReserved?: boolean;
-    content?: Record<MediaType, MediaTypeObject$1>;
-    deprecated?: boolean;
-    description?: string;
-    example?: unknown;
-    examples?: Dictionary<OpenApiExample>;
-    explode?: boolean;
-    in: 'cookie' | 'formData' | 'header' | 'path' | 'query';
-    name: string;
-    nullable?: boolean;
-    required?: boolean;
-    schema?: OpenApiSchema$1;
-    style?: string;
+interface NumberKeywords {
+  /**
+   * Ranges of numbers are specified using a combination of the `minimum` and `maximum` keywords, (or `exclusiveMinimum` and `exclusiveMaximum` for expressing exclusive range).
+   *
+   * If _x_ is the value being validated, the following must hold true:
+   *
+   * ```
+   * x ≥ minimum
+   * x > exclusiveMinimum
+   * x ≤ maximum
+   * x < exclusiveMaximum
+   * ```
+   *
+   * While you can specify both of `minimum` and `exclusiveMinimum` or both of `maximum` and `exclusiveMaximum`, it doesn't really make sense to do so.
+   */
+  exclusiveMaximum?: number;
+  /**
+   * Ranges of numbers are specified using a combination of the `minimum` and `maximum` keywords, (or `exclusiveMinimum` and `exclusiveMaximum` for expressing exclusive range).
+   *
+   * If _x_ is the value being validated, the following must hold true:
+   *
+   * ```
+   * x ≥ minimum
+   * x > exclusiveMinimum
+   * x ≤ maximum
+   * x < exclusiveMaximum
+   * ```
+   *
+   * While you can specify both of `minimum` and `exclusiveMinimum` or both of `maximum` and `exclusiveMaximum`, it doesn't really make sense to do so.
+   */
+  exclusiveMinimum?: number;
+  /**
+   * Ranges of numbers are specified using a combination of the `minimum` and `maximum` keywords, (or `exclusiveMinimum` and `exclusiveMaximum` for expressing exclusive range).
+   *
+   * If _x_ is the value being validated, the following must hold true:
+   *
+   * ```
+   * x ≥ minimum
+   * x > exclusiveMinimum
+   * x ≤ maximum
+   * x < exclusiveMaximum
+   * ```
+   *
+   * While you can specify both of `minimum` and `exclusiveMinimum` or both of `maximum` and `exclusiveMaximum`, it doesn't really make sense to do so.
+   */
+  maximum?: number;
+  /**
+   * Ranges of numbers are specified using a combination of the `minimum` and `maximum` keywords, (or `exclusiveMinimum` and `exclusiveMaximum` for expressing exclusive range).
+   *
+   * If _x_ is the value being validated, the following must hold true:
+   *
+   * ```
+   * x ≥ minimum
+   * x > exclusiveMinimum
+   * x ≤ maximum
+   * x < exclusiveMaximum
+   * ```
+   *
+   * While you can specify both of `minimum` and `exclusiveMinimum` or both of `maximum` and `exclusiveMaximum`, it doesn't really make sense to do so.
+   */
+  minimum?: number;
+  /**
+   * Numbers can be restricted to a multiple of a given number, using the `multipleOf` keyword. It may be set to any positive number. The multiple can be a floating point number.
+   */
+  multipleOf?: number;
 }
 
-interface Enum {
-    customDescription?: string;
-    customName?: string;
-    description?: string;
-    value: string | number;
-}
-interface OperationParameter extends Model {
-    in: 'body' | 'cookie' | 'formData' | 'header' | 'path' | 'query';
-    mediaType: string | null;
-    prop: string;
-}
-interface OperationParameters extends Pick<Model, '$refs' | 'imports'> {
-    parameters: OperationParameter[];
-    parametersBody: OperationParameter | null;
-    parametersCookie: OperationParameter[];
-    parametersForm: OperationParameter[];
-    parametersHeader: OperationParameter[];
-    parametersPath: OperationParameter[];
-    parametersQuery: OperationParameter[];
-}
-interface OperationResponse extends Model {
-    code: number | 'default' | '1XX' | '2XX' | '3XX' | '4XX' | '5XX';
-    in: 'header' | 'response';
-    responseTypes: Array<'error' | 'success'>;
-}
-type Method = 'CONNECT' | 'DELETE' | 'GET' | 'HEAD' | 'OPTIONS' | 'PATCH' | 'POST' | 'PUT' | 'TRACE';
-interface Operation$1 extends OperationParameters {
-    deprecated: boolean;
-    description: string | null;
-    /**
-     * The operationId from OpenAPI specification.
-     */
-    id: string | null;
-    method: Method;
-    name: string;
-    path: string;
-    responseHeader: string | null;
-    /**
-     * All operation responses defined in OpenAPI specification.
-     * Sorted by status code.
-     */
-    responses: OperationResponse[];
-    summary: string | null;
-    tags: string[] | null;
-}
-interface Schema {
-    default?: unknown;
-    exclusiveMaximum?: boolean;
-    exclusiveMinimum?: boolean;
-    format?: 'binary' | 'boolean' | 'byte' | 'date-time' | 'date' | 'double' | 'float' | 'int32' | 'int64' | 'password' | 'string';
-    isDefinition: boolean;
-    isNullable: boolean;
-    isReadOnly: boolean;
-    isRequired: boolean;
-    maxItems?: number;
-    maxLength?: number;
-    maxProperties?: number;
-    maximum?: number;
-    minItems?: number;
-    minLength?: number;
-    minProperties?: number;
-    minimum?: number;
-    multipleOf?: number;
-    pattern?: string;
-    uniqueItems?: boolean;
-}
-interface ModelMeta {
-    /**
-     * Ref to the type in OpenAPI specification.
-     */
-    $ref: string;
-    /**
-     * Name passed to the initial `getModel()` call.
-     */
-    name: string;
-}
-interface Model extends Schema {
-    /**
-     * **Experimental.** Contains list of original refs so they can be used
-     * to access the schema from anywhere instead of relying on string name.
-     * This allows us to do things like detect type of ref.
-     */
-    $refs: string[];
-    base: string;
-    deprecated?: boolean;
-    description: string | null;
-    enum: Enum[];
-    enums: Model[];
-    export: 'all-of' | 'any-of' | 'array' | 'const' | 'dictionary' | 'enum' | 'generic' | 'interface' | 'one-of' | 'reference';
-    imports: string[];
-    in: OperationParameter['in'] | OpenApiParameter['in'] | OperationResponse['in'] | '';
-    link: Model | Model[] | null;
-    meta?: ModelMeta;
-    /**
-     * @deprecated use `meta.name` instead
-     */
-    name: string;
-    properties: Model[];
-    template: string | null;
-    type: string;
-}
-interface Client$2 {
-    models: Model[];
-    operations: Operation$1[];
-    server: string;
-    /**
-     * Map of generated types where type names are keys. This is used to track
-     * uniquely generated types as we may want to deduplicate if there are
-     * multiple definitions with the same name but different value, or if we
-     * want to transform names.
-     */
-    types: Record<string, ModelMeta>;
-    version: string;
+interface ObjectKeywords {
+  /**
+   * The `additionalProperties` keyword is used to control the handling of extra stuff, that is, properties whose names are not listed in the `properties` keyword or match any of the regular expressions in the `patternProperties` keyword. By default any additional properties are allowed.
+   *
+   * The value of the `additionalProperties` keyword is a schema that will be used to validate any properties in the {@link https://json-schema.org/learn/glossary#instance instance} that are not matched by `properties` or `patternProperties`. Setting the `additionalProperties` schema to `false` means no additional properties will be allowed.
+   *
+   * It's important to note that `additionalProperties` only recognizes properties declared in the same {@link https://json-schema.org/learn/glossary#subschema subschema} as itself. So, `additionalProperties` can restrict you from "extending" a schema using {@link https://json-schema.org/understanding-json-schema/reference/combining combining} keywords such as {@link https://json-schema.org/understanding-json-schema/reference/combining#allof allOf}.
+   */
+  additionalProperties?: JsonSchemaDraft2020_12 | false;
+  /**
+   * The number of properties on an object can be restricted using the `minProperties` and `maxProperties` keywords. Each of these must be a non-negative integer.
+   */
+  maxProperties?: number;
+  /**
+   * The number of properties on an object can be restricted using the `minProperties` and `maxProperties` keywords. Each of these must be a non-negative integer.
+   */
+  minProperties?: number;
+  /**
+   * Sometimes you want to say that, given a particular kind of property name, the value should match a particular schema. That's where `patternProperties` comes in: it maps regular expressions to schemas. If a property name matches the given regular expression, the property value must validate against the corresponding schema.
+   */
+  patternProperties?: Record<string, JsonSchemaDraft2020_12>;
+  /**
+   * The properties (key-value pairs) on an object are defined using the `properties` {@link https://json-schema.org/learn/glossary#keyword keyword}. The value of `properties` is an object, where each key is the name of a property and each value is a {@link https://json-schema.org/learn/glossary#schema schema} used to validate that property. Any property that doesn't match any of the property names in the `properties` keyword is ignored by this keyword.
+   */
+  properties?: Record<string, JsonSchemaDraft2020_12 | true>;
+  /**
+   * The names of properties can be validated against a schema, irrespective of their values. This can be useful if you don't want to enforce specific properties, but you want to make sure that the names of those properties follow a specific convention. You might, for example, want to enforce that all names are valid ASCII tokens so they can be used as attributes in a particular programming language.
+   *
+   * Since object keys must always be strings anyway, it is implied that the schema given to `propertyNames` is always at least:
+   *
+   * ```json
+   * { "type": "string" }
+   * ```
+   */
+  propertyNames?: JsonSchemaDraft2020_12;
+  /**
+   * By default, the properties defined by the `properties` keyword are not required. However, one can provide a list of required properties using the `required` keyword.
+   *
+   * The `required` keyword takes an array of zero or more strings. Each of these strings must be unique.
+   */
+  required?: ReadonlyArray<string>;
+  /**
+   * The `unevaluatedProperties` keyword is similar to `additionalProperties` except that it can recognize properties declared in subschemas. So, the example from the previous section can be rewritten without the need to redeclare properties.
+   *
+   * `unevaluatedProperties` works by collecting any properties that are successfully validated when processing the schemas and using those as the allowed list of properties. This allows you to do more complex things like conditionally adding properties.
+   */
+  unevaluatedProperties?: JsonSchemaDraft2020_12 | false;
 }
 
-/**
- * {@link} https://github.com/OAI/OpenAPI-Specification/blob/main/versions/2.0.md#external-documentation-object
- */
-interface OpenApiExternalDocs {
-    description?: string;
-    url: string;
+interface StringKeywords {
+  /**
+   * The length of a string can be constrained using the `minLength` and `maxLength` {@link https://json-schema.org/learn/glossary#keyword keywords}. For both keywords, the value must be a non-negative number.
+   */
+  maxLength?: number;
+  /**
+   * The length of a string can be constrained using the `minLength` and `maxLength` {@link https://json-schema.org/learn/glossary#keyword keywords}. For both keywords, the value must be a non-negative number.
+   */
+  minLength?: number;
+  /**
+   * The `pattern` keyword is used to restrict a string to a particular regular expression. The regular expression syntax is the one defined in JavaScript ({@link https://www.ecma-international.org/publications-and-standards/standards/ecma-262/ ECMA 262} specifically) with Unicode support. See {@link https://json-schema.org/understanding-json-schema/reference/regular_expressions Regular Expressions} for more information.
+   */
+  pattern?: string;
 }
 
-interface WithNullableExtension {
-    'x-nullable'?: boolean;
-}
+type JsonSchemaFormats =
+  | 'date'
+  | 'date-time'
+  | 'duration'
+  | 'email'
+  | 'hostname'
+  | 'idn-email'
+  | 'idn-hostname'
+  | 'ipv4'
+  | 'ipv6'
+  | 'iri'
+  | 'iri-reference'
+  | 'json-pointer'
+  | 'regex'
+  | 'relative-json-pointer'
+  | 'time'
+  | 'uri'
+  | 'uri-reference'
+  | 'uri-template'
+  | 'uuid'
+  // eslint-disable-next-line @typescript-eslint/ban-types
+  | (string & {});
 
-/**
- * {@link} https://github.com/OAI/OpenAPI-Specification/blob/main/versions/2.0.md#reference-object
- */
-interface OpenApiReference {
-    $ref?: string;
-}
+type JsonSchemaTypes =
+  | 'array'
+  | 'boolean'
+  | 'integer'
+  | 'null'
+  | 'number'
+  | 'object'
+  | 'string';
 
 /**
- * {@link} https://github.com/OAI/OpenAPI-Specification/blob/main/versions/2.0.md#xml-object
+ * This is the root object of the {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#openapi-document OpenAPI document}.
+ *
+ * This object MAY be extended with {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#specification-extensions Specification Extensions}.
  */
-interface OpenApiXml {
-    attribute?: boolean;
-    name?: string;
-    namespace?: string;
-    prefix?: string;
-    wrapped?: boolean;
+interface OpenApiV3_1_0 {
+  /**
+   * An element to hold various schemas for the document.
+   */
+  components?: ComponentsObject;
+  /**
+   * Additional external documentation.
+   */
+  externalDocs?: ExternalDocumentationObject;
+  /**
+   * **REQUIRED**. Provides metadata about the API. The metadata MAY be used by tooling as required.
+   */
+  info: InfoObject;
+  /**
+   * The default value for the `$schema` keyword within {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#schema-object Schema Objects} contained within this OAS document. This MUST be in the form of a URI.
+   */
+  jsonSchemaDialect?: string;
+  /**
+   * **REQUIRED**. This string MUST be the {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#versions version number} of the OpenAPI Specification that the OpenAPI document uses. The `openapi` field SHOULD be used by tooling to interpret the OpenAPI document. This is _not_ related to the API {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#infoVersion `info.version`} string.
+   */
+  openapi: '3.1.0';
+  /**
+   * The available paths and operations for the API.
+   */
+  paths?: PathsObject;
+  /**
+   * A declaration of which security mechanisms can be used across the API. The list of values includes alternative security requirement objects that can be used. Only one of the security requirement objects need to be satisfied to authorize a request. Individual operations can override this definition. To make security optional, an empty security requirement (`{}`) can be included in the array.
+   */
+  security?: ReadonlyArray<SecurityRequirementObject>;
+  /**
+   * An array of Server Objects, which provide connectivity information to a target server. If the `servers` property is not provided, or is an empty array, the default value would be a {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#server-object Server Object} with a {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#serverUrl url} value of `/`.
+   */
+  servers?: ReadonlyArray<ServerObject>;
+  /**
+   * A list of tags used by the document with additional metadata. The order of the tags can be used to reflect on their order by the parsing tools. Not all tags that are used by the {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#operation-object Operation Object} must be declared. The tags that are not declared MAY be organized randomly or based on the tools' logic. Each tag name in the list MUST be unique.
+   */
+  tags?: ReadonlyArray<TagObject>;
+  /**
+   * The incoming webhooks that MAY be received as part of this API and that the API consumer MAY choose to implement. Closely related to the `callbacks` feature, this section describes requests initiated other than by an API call, for example by an out of band registration. The key name is a unique string to refer to each webhook, while the (optionally referenced) Path Item Object describes a request that may be initiated by the API provider and the expected responses. An {@link https://github.com/OAI/OpenAPI-Specification/blob/main/examples/v3.1/webhook-example.yaml example} is available.
+   */
+  webhooks?: Record<string, PathItemObject | ReferenceObject>;
 }
 
-/**
- * {@link} https://github.com/OAI/OpenAPI-Specification/blob/main/versions/2.0.md#schema-object
- */
-interface OpenApiSchema extends OpenApiReference, WithEnumExtension, WithNullableExtension {
-    additionalProperties?: boolean | OpenApiSchema;
-    allOf?: OpenApiSchema[];
-    default?: unknown;
-    description?: string;
-    discriminator?: string;
-    enum?: (string | number)[];
-    example?: unknown;
-    exclusiveMaximum?: boolean;
-    exclusiveMinimum?: boolean;
-    externalDocs?: OpenApiExternalDocs;
-    format?: 'int32' | 'int64' | 'float' | 'double' | 'string' | 'boolean' | 'byte' | 'binary' | 'date' | 'date-time' | 'password';
-    items?: OpenApiSchema;
-    maxItems?: number;
-    maxLength?: number;
-    maxProperties?: number;
-    maximum?: number;
-    minItems?: number;
-    minLength?: number;
-    minProperties?: number;
-    minimum?: number;
-    multipleOf?: number;
-    pattern?: string;
-    properties?: Dictionary<OpenApiSchema>;
-    readOnly?: boolean;
-    required?: string[];
-    title?: string;
-    type?: string;
-    uniqueItems?: boolean;
-    xml?: OpenApiXml;
-}
-
-interface Operation extends Omit<Operation$1, 'tags'> {
-    service: string;
-}
-interface Service extends Pick<Model, '$refs' | 'imports' | 'name'> {
-    operations: Operation[];
-}
-interface Client$1 extends Omit<Client$2, 'operations'> {
-    services: Service[];
-}
-
-interface Config$3 {
-    /**
-     * Generate {@link https://tanstack.com/query/v5/docs/framework/react/reference/infiniteQueryOptions `infiniteQueryOptions()`} helpers? These will be generated from GET and POST requests where a pagination parameter is detected.
-     * @default true
-     */
-    infiniteQueryOptions?: boolean;
-    /**
-     * Generate {@link https://tanstack.com/query/v5/docs/framework/react/reference/useMutation `useMutation()`} helpers? These will be generated from DELETE, PATCH, POST, and PUT requests.
-     * @default true
-     */
-    mutationOptions?: boolean;
-    /**
-     * Generate TanStack React Query output from the provided input.
-     */
-    name: '@tanstack/react-query';
-    /**
-     * Name of the generated file.
-     * @default '@tanstack/react-query'
-     */
-    output?: string;
-    /**
-     * Generate {@link https://tanstack.com/query/v5/docs/framework/react/reference/queryOptions `queryOptions()`} helpers?
-     * These will be generated from all requests.
-     * @default true
-     */
-    queryOptions?: boolean;
-}
-interface UserConfig$4 extends Omit<Config$3, 'output'> {
-}
-
-interface Config$2 {
-    /**
-     * Generate `createInfiniteQuery()` helpers? These will be generated from GET and POST requests where a pagination parameter is detected.
-     * @default true
-     */
-    infiniteQueryOptions?: boolean;
-    /**
-     * Generate `createMutation()` helpers? These will be generated from DELETE, PATCH, POST, and PUT requests.
-     * @default true
-     */
-    mutationOptions?: boolean;
-    /**
-     * Generate TanStack Solid Query output from the provided input.
-     */
-    name: '@tanstack/solid-query';
-    /**
-     * Name of the generated file.
-     * @default '@tanstack/solid-query'
-     */
-    output?: string;
-    /**
-     * Generate {@link https://tanstack.com/query/v5/docs/framework/solid/reference/createQuery `createQuery()`} helpers?
-     * These will be generated from all requests.
-     * @default true
-     */
-    queryOptions?: boolean;
-}
-interface UserConfig$3 extends Omit<Config$2, 'output'> {
-}
-
-interface Config$1 {
-    /**
-     * Generate `createInfiniteQuery()` helpers? These will be generated from GET and POST requests where a pagination parameter is detected.
-     * @default true
-     */
-    infiniteQueryOptions?: boolean;
-    /**
-     * Generate {@link https://tanstack.com/query/v5/docs/framework/svelte/reference/functions/createmutation `createMutation()`} helpers? These will be generated from DELETE, PATCH, POST, and PUT requests.
-     * @default true
-     */
-    mutationOptions?: boolean;
-    /**
-     * Generate TanStack Svelte Query output from the provided input.
-     */
-    name: '@tanstack/svelte-query';
-    /**
-     * Name of the generated file.
-     * @default '@tanstack/svelte-query'
-     */
-    output?: string;
-    /**
-     * Generate {@link https://tanstack.com/query/v5/docs/framework/svelte/reference/functions/createquery `createQuery()`} helpers?
-     * These will be generated from all requests.
-     * @default true
-     */
-    queryOptions?: boolean;
-}
-interface UserConfig$2 extends Omit<Config$1, 'output'> {
-}
-
-interface Config {
-    /**
-     * Generate {@link https://tanstack.com/query/v5/docs/framework/vue/reference/infiniteQueryOptions `infiniteQueryOptions()`} helpers? These will be generated from GET and POST requests where a pagination parameter is detected.
-     * @default true
-     */
-    infiniteQueryOptions?: boolean;
-    /**
-     * Generate {@link https://tanstack.com/query/v5/docs/framework/vue/reference/useMutation `useMutation()`} helpers? These will be generated from DELETE, PATCH, POST, and PUT requests.
-     * @default true
-     */
-    mutationOptions?: boolean;
-    /**
-     * Generate TanStack Vue Query output from the provided input.
-     */
-    name: '@tanstack/vue-query';
-    /**
-     * Name of the generated file.
-     * @default '@tanstack/vue-query'
-     */
-    output?: string;
-    /**
-     * Generate {@link https://tanstack.com/query/v5/docs/framework/vue/guides/query-options `queryOptions()`} helpers?
-     * These will be generated from all requests.
-     * @default true
-     */
-    queryOptions?: boolean;
-}
-interface UserConfig$1 extends Omit<Config, 'output'> {
-}
-
-/**
- * User-facing plugin types.
- */
-type UserPlugins = UserConfig$4 | UserConfig$3 | UserConfig$2 | UserConfig$1;
-
-declare const CLIENTS: readonly ["@hey-api/client-axios", "@hey-api/client-fetch", "legacy/angular", "legacy/axios", "legacy/fetch", "legacy/node", "legacy/xhr"];
-type Client = (typeof CLIENTS)[number];
-interface ClientConfig {
-    /**
-     * Manually set base in OpenAPI config instead of inferring from server value
-     * @deprecated
-     */
-    base?: string;
-    /**
-     * HTTP client to generate
-     */
-    client?: Client | false | {
-        /**
-         * Bundle the client module? Set this to true if you're using a standalone
-         * client package and don't want to declare it as a separate dependency.
-         * When true, the client module will be generated from the standalone
-         * package and bundled with the rest of the generated output. This is
-         * useful if you're repackaging the output, publishing it to other users,
-         * and you don't want them to install any dependencies.
-         * @default false
-         */
-        bundle?: boolean;
-        /**
-         * HTTP client to generate
-         */
-        name: Client;
-    };
-    /**
-     * Path to the config file. Set this value if you don't use the default
-     * config file name, or it's not located in the project root.
-     */
-    configFile?: string;
-    /**
-     * Run in debug mode?
-     * @default false
-     */
-    debug?: boolean;
-    /**
-     * Skip writing files to disk?
-     * @default false
-     */
-    dryRun?: boolean;
-    /**
-     * Use the experimental parser?
-     * @default false
-     */
-    experimental_parser?: boolean;
-    /**
-     * Generate core client classes?
-     * @default true
-     */
-    exportCore?: boolean;
-    /**
-     * The relative location of the OpenAPI spec
-     */
-    input: string | Record<string, unknown>;
-    /**
-     * Custom client class name
-     * @deprecated
-     */
-    name?: string;
-    /**
-     * The relative location of the output directory
-     */
-    output: string | {
-        /**
-         * Process output folder with formatter?
-         * @default false
-         */
-        format?: 'biome' | 'prettier' | false;
-        /**
-         * Process output folder with linter?
-         * @default false
-         */
-        lint?: 'biome' | 'eslint' | false;
-        /**
-         * The relative location of the output directory
-         */
-        path: string;
-    };
-    /**
-     * Plugins are used to generate additional output files from provided input.
-     */
-    plugins?: ReadonlyArray<UserPlugins['name'] | UserPlugins>;
-    /**
-     * Path to custom request file
-     * @deprecated
-     */
-    request?: string;
-    /**
-     * Generate JSON schemas?
-     * @default true
-     */
-    schemas?: boolean | {
-        /**
-         * Generate JSON schemas?
-         * @default true
-         */
-        export?: boolean;
-        /**
-         * Customise the schema name. By default, `{{name}}Schema` is used. `name` is a
-         * valid JavaScript/TypeScript identifier, e.g. if your schema name is
-         * "Foo-Bar", `name` value would be "FooBar".
-         */
-        name?: (name: string, schema: OpenApiSchema | OpenApiSchema$1) => string;
-        /**
-         * Choose schema type to generate. Select 'form' if you don't want
-         * descriptions to reduce bundle size and you plan to use schemas
-         * for form validation
-         * @default 'json'
-         */
-        type?: 'form' | 'json';
-    };
-    /**
-     * Generate services?
-     * @default true
-     */
-    services?: boolean | string | {
-        /**
-         * Group operation methods into service classes? When enabled, you can
-         * select which classes to export with `services.include` and/or
-         * transform their names with `services.name`.
-         *
-         * Note that by enabling this option, your services will **NOT**
-         * support {@link https://developer.mozilla.org/docs/Glossary/Tree_shaking tree-shaking}.
-         * For this reason, it is disabled by default.
-         * @default false
-         */
-        asClass?: boolean;
-        /**
-         * Generate services?
-         * @default true
-         */
-        export?: boolean;
-        /**
-         * Filter endpoints to be included in the generated services.
-         * The provided string should be a regular expression where matched
-         * results will be included in the output. The input pattern this
-         * string will be tested against is `{method} {path}`. For example,
-         * you can match `POST /api/v1/foo` with `^POST /api/v1/foo$`.
-         */
-        filter?: string;
-        /**
-         * Include only service classes with names matching regular expression
-         *
-         * This option has no effect if `services.asClass` is `false`.
-         */
-        include?: string;
-        /**
-         * Customise the name of methods within the service. By default, {@link Operation.name} is used.
-         */
-        methodNameBuilder?: (operation: Operation) => string;
-        /**
-         * Customize the generated service class names. The name variable is
-         * obtained from your OpenAPI specification tags.
-         *
-         * This option has no effect if `services.asClass` is `false`.
-         * @default '{{name}}Service'
-         */
-        name?: string;
-        /**
-         * Use operation ID to generate operation names?
-         * @default true
-         */
-        operationId?: boolean;
-        /**
-         * Define shape of returned value from service calls
-         * @default 'body'
-         * @deprecated
-         */
-        response?: 'body' | 'response';
-    };
-    /**
-     * Generate types?
-     * @default true
-     */
-    types?: boolean | string | {
-        /**
-         * Output Date type and possibly runtime transform instead of string for format "date-time"
-         * @default false
-         */
-        dates?: boolean | 'types+transform' | 'types';
-        /**
-         * Generate enum definitions?
-         * @default false
-         */
-        enums?: 'javascript' | 'typescript' | 'typescript+namespace' | false;
-        /**
-         * Generate types?
-         * @default true
-         */
-        export?: boolean;
-        /**
-         * Include only types matching regular expression
-         */
-        include?: string;
-        /**
-         * Use your preferred naming pattern
-         * @default 'preserve'
-         */
-        name?: 'PascalCase' | 'preserve';
-        /**
-         * Generate a tree of types containing all operations? It will be named
-         * $OpenApiTs and is generated by default only when not using services.
-         */
-        tree?: boolean;
-    };
-    /**
-     * Use options or arguments functions
-     * @deprecated
-     * @default true
-     */
-    useOptions?: boolean;
-}
-interface UserConfig extends ClientConfig {
-}
-
-interface OpenApiV3_0_3 {
-    /**
-     * **REQUIRED**. This string MUST be the {@link https://semver.org/spec/v2.0.0.html semantic version number} of the {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.0.3.md#versions OpenAPI Specification version} that the OpenAPI document uses. The `openapi` field SHOULD be used by tooling specifications and clients to interpret the OpenAPI document. This is _not_ related to the API {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.0.3.md#infoVersion `info.version`} string.
-     */
-    openapi: '3.0.3';
-}
-
-/**
- * This is the root object of the {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#openapi-document OpenAPI document}.
- *
- * This object MAY be extended with {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#specification-extensions Specification Extensions}.
- */
-interface OpenApiV3_1 {
-    /**
-     * An element to hold various schemas for the document.
-     */
-    components?: ComponentsObject;
-    /**
-     * Additional external documentation.
-     */
-    externalDocs?: ExternalDocumentationObject;
-    /**
-     * **REQUIRED**. Provides metadata about the API. The metadata MAY be used by tooling as required.
-     */
-    info: InfoObject;
-    /**
-     * The default value for the `$schema` keyword within {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#schema-object Schema Objects} contained within this OAS document. This MUST be in the form of a URI.
-     */
-    jsonSchemaDialect?: string;
-    /**
-     * **REQUIRED**. This string MUST be the {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#versions version number} of the OpenAPI Specification that the OpenAPI document uses. The `openapi` field SHOULD be used by tooling to interpret the OpenAPI document. This is _not_ related to the API {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#infoVersion `info.version`} string.
-     */
-    openapi: '3.1.0';
-    /**
-     * The available paths and operations for the API.
-     */
-    paths?: PathsObject;
-    /**
-     * A declaration of which security mechanisms can be used across the API. The list of values includes alternative security requirement objects that can be used. Only one of the security requirement objects need to be satisfied to authorize a request. Individual operations can override this definition. To make security optional, an empty security requirement (`{}`) can be included in the array.
-     */
-    security?: ReadonlyArray<SecurityRequirementObject>;
-    /**
-     * An array of Server Objects, which provide connectivity information to a target server. If the `servers` property is not provided, or is an empty array, the default value would be a {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#server-object Server Object} with a {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#serverUrl url} value of `/`.
-     */
-    servers?: ReadonlyArray<ServerObject>;
-    /**
-     * A list of tags used by the document with additional metadata. The order of the tags can be used to reflect on their order by the parsing tools. Not all tags that are used by the {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#operation-object Operation Object} must be declared. The tags that are not declared MAY be organized randomly or based on the tools' logic. Each tag name in the list MUST be unique.
-     */
-    tags?: ReadonlyArray<TagObject>;
-    /**
-     * The incoming webhooks that MAY be received as part of this API and that the API consumer MAY choose to implement. Closely related to the `callbacks` feature, this section describes requests initiated other than by an API call, for example by an out of band registration. The key name is a unique string to refer to each webhook, while the (optionally referenced) Path Item Object describes a request that may be initiated by the API provider and the expected responses. An {@link https://github.com/OAI/OpenAPI-Specification/blob/main/examples/v3.1/webhook-example.yaml example} is available.
-     */
-    webhooks?: Record<string, PathItemObject | ReferenceObject>;
-}
 /**
  * A map of possible out-of band callbacks related to the parent operation. Each value in the map is a {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#path-item-object Path Item Object} that describes a set of requests that may be initiated by the API provider and the expected responses. The key value used to identify the path item object is an expression, evaluated at runtime, that identifies a URL to use for the callback operation.
  *
@@ -799,11 +548,12 @@ interface OpenApiV3_1 {
  * ```
  */
 interface CallbackObject {
-    /**
-     * A Path Item Object, or a reference to one, used to define a callback request and expected responses. A {@link https://github.com/OAI/OpenAPI-Specification/blob/main/examples/v3.0/callback-example.yaml complete example} is available.
-     */
-    [expression: string]: PathItemObject | ReferenceObject;
+  /**
+   * A Path Item Object, or a reference to one, used to define a callback request and expected responses. A {@link https://github.com/OAI/OpenAPI-Specification/blob/main/examples/v3.0/callback-example.yaml complete example} is available.
+   */
+  [expression: string]: PathItemObject | ReferenceObject;
 }
+
 /**
  * Holds a set of reusable objects for different aspects of the OAS. All objects defined within the components object will have no effect on the API unless they are explicitly referenced from properties outside the components object.
  *
@@ -883,58 +633,59 @@ interface CallbackObject {
  *       type: apiKey
  *       name: api_key
  *       in: header
- *     petstore_auth:
- *       type: oauth2
- *       flows:
- *         implicit:
- *           authorizationUrl: https://example.org/api/oauth/dialog
- *           scopes:
- *             write:pets: modify pets in your account
- *             read:pets: read your pets
- * ```
- */
-interface ComponentsObject {
-    /**
-     * An object to hold reusable {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#callback-object Callback Objects}.
-     */
-    callbacks?: Record<string, CallbackObject | ReferenceObject>;
-    /**
-     * An object to hold reusable {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#example-object Example Objects}.
-     */
-    examples?: Record<string, ExampleObject | ReferenceObject>;
-    /**
-     * An object to hold reusable {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#header-object Header Objects}.
-     */
-    headers?: Record<string, HeaderObject | ReferenceObject>;
-    /**
-     * An object to hold reusable {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#link-object Link Objects}.
-     */
-    links?: Record<string, LinkObject | ReferenceObject>;
-    /**
-     * An object to hold reusable {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#parameter-object Parameter Objects}.
-     */
-    parameters?: Record<string, ParameterObject | ReferenceObject>;
-    /**
-     * An object to hold reusable {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#path-item-object Path Item Object}.
-     */
-    pathItems?: Record<string, PathItemObject | ReferenceObject>;
-    /**
-     * An object to hold reusable {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#request-body-object Request Body Objects}.
-     */
-    requestBodies?: Record<string, RequestBodyObject | ReferenceObject>;
-    /**
-     * An object to hold reusable {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#response-object Response Objects}.
-     */
-    responses?: Record<string, ResponseObject | ReferenceObject>;
-    /**
-     * An object to hold reusable {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#schema-object Schema Objects}.
-     */
-    schemas?: Record<string, SchemaObject>;
-    /**
-     * An object to hold reusable {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#security-scheme-object Security Scheme Objects}.
-     */
-    securitySchemes?: Record<string, SecuritySchemeObject | ReferenceObject>;
+ *     petstore_auth:
+ *       type: oauth2
+ *       flows:
+ *         implicit:
+ *           authorizationUrl: https://example.org/api/oauth/dialog
+ *           scopes:
+ *             write:pets: modify pets in your account
+ *             read:pets: read your pets
+ * ```
+ */
+interface ComponentsObject {
+  /**
+   * An object to hold reusable {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#callback-object Callback Objects}.
+   */
+  callbacks?: Record<string, CallbackObject | ReferenceObject>;
+  /**
+   * An object to hold reusable {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#example-object Example Objects}.
+   */
+  examples?: Record<string, ExampleObject | ReferenceObject>;
+  /**
+   * An object to hold reusable {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#header-object Header Objects}.
+   */
+  headers?: Record<string, HeaderObject | ReferenceObject>;
+  /**
+   * An object to hold reusable {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#link-object Link Objects}.
+   */
+  links?: Record<string, LinkObject | ReferenceObject>;
+  /**
+   * An object to hold reusable {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#parameter-object Parameter Objects}.
+   */
+  parameters?: Record<string, ParameterObject | ReferenceObject>;
+  /**
+   * An object to hold reusable {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#path-item-object Path Item Object}.
+   */
+  pathItems?: Record<string, PathItemObject | ReferenceObject>;
+  /**
+   * An object to hold reusable {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#request-body-object Request Body Objects}.
+   */
+  requestBodies?: Record<string, RequestBodyObject | ReferenceObject>;
+  /**
+   * An object to hold reusable {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#response-object Response Objects}.
+   */
+  responses?: Record<string, ResponseObject | ReferenceObject>;
+  /**
+   * An object to hold reusable {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#schema-object Schema Objects}.
+   */
+  schemas?: Record<string, SchemaObject>;
+  /**
+   * An object to hold reusable {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#security-scheme-object Security Scheme Objects}.
+   */
+  securitySchemes?: Record<string, SecuritySchemeObject | ReferenceObject>;
 }
+
 /**
  * Contact information for the exposed API.
  *
@@ -948,19 +699,20 @@ interface ComponentsObject {
  * ```
  */
 interface ContactObject {
-    /**
-     * The email address of the contact person/organization. This MUST be in the form of an email address.
-     */
-    email?: string;
-    /**
-     * The identifying name of the contact person/organization.
-     */
-    name?: string;
-    /**
-     * The URL pointing to the contact information. This MUST be in the form of a URL.
-     */
-    url?: string;
+  /**
+   * The email address of the contact person/organization. This MUST be in the form of an email address.
+   */
+  email?: string;
+  /**
+   * The identifying name of the contact person/organization.
+   */
+  name?: string;
+  /**
+   * The URL pointing to the contact information. This MUST be in the form of a URL.
+   */
+  url?: string;
 }
+
 /**
  * When request bodies or response payloads may be one of a number of different schemas, a `discriminator` object can be used to aid in serialization, deserialization, and validation. The discriminator is a specific object in a schema which is used to inform the consumer of the document of an alternative schema based on the value associated with it.
  *
@@ -1088,15 +840,16 @@ interface ContactObject {
  * will map to `Dog` because of the definition in the `mapping` element.
  */
 interface DiscriminatorObject {
-    /**
-     * An object to hold mappings between payload values and schema names or references.
-     */
-    mapping?: Record<string, string>;
-    /**
-     * **REQUIRED**. The name of the property in the payload that will hold the discriminator value.
-     */
-    propertyName: string;
+  /**
+   * An object to hold mappings between payload values and schema names or references.
+   */
+  mapping?: Record<string, string>;
+  /**
+   * **REQUIRED**. The name of the property in the payload that will hold the discriminator value.
+   */
+  propertyName: string;
 }
+
 /**
  * A single encoding definition applied to a single schema property.
  *
@@ -1139,27 +892,28 @@ interface DiscriminatorObject {
  * ```
  */
 interface EncodingObject {
-    /**
-     * Determines whether the parameter value SHOULD allow reserved characters, as defined by {@link https://tools.ietf.org/html/rfc3986#section-2.2 RFC3986} `:/?#[]@!$&'()*+,;=` to be included without percent-encoding. The default value is `false`. This property SHALL be ignored if the request body media type is not `application/x-www-form-urlencoded` or `multipart/form-data`. If a value is explicitly defined, then the value of {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#encodingContentType `contentType`} (implicit or explicit) SHALL be ignored.
-     */
-    allowReserved?: boolean;
-    /**
-     * The Content-Type for encoding a specific property. Default value depends on the property type: for `object` - `application/json`; for `array` – the default is defined based on the inner type; for all other cases the default is `application/octet-stream`. The value can be a specific media type (e.g. `application/json`), a wildcard media type (e.g. `image/*`), or a comma-separated list of the two types.
-     */
-    contentType?: string;
-    /**
-     * When this is true, property values of type `array` or `object` generate separate parameters for each value of the array, or key-value-pair of the map. For other types of properties this property has no effect. When {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#encodingStyle `style`} is `form`, the default value is `true`. For all other styles, the default value is `false`. This property SHALL be ignored if the request body media type is not `application/x-www-form-urlencoded` or `multipart/form-data`. If a value is explicitly defined, then the value of {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#encodingContentType `contentType`} (implicit or explicit) SHALL be ignored.
-     */
-    explode?: boolean;
-    /**
-     * A map allowing additional information to be provided as headers, for example `Content-Disposition`. `Content-Type` is described separately and SHALL be ignored in this section. This property SHALL be ignored if the request body media type is not a `multipart`.
-     */
-    headers?: Record<string, HeaderObject | ReferenceObject>;
-    /**
-     * Describes how a specific property value will be serialized depending on its type. See {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#parameter-object Parameter Object} for details on the {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#parameterStyle `style`} property. The behavior follows the same values as `query` parameters, including default values. This property SHALL be ignored if the request body media type is not `application/x-www-form-urlencoded` or `multipart/form-data`. If a value is explicitly defined, then the value of {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#encodingContentType `contentType`} (implicit or explicit) SHALL be ignored.
-     */
-    style?: string;
+  /**
+   * Determines whether the parameter value SHOULD allow reserved characters, as defined by {@link https://tools.ietf.org/html/rfc3986#section-2.2 RFC3986} `:/?#[]@!$&'()*+,;=` to be included without percent-encoding. The default value is `false`. This property SHALL be ignored if the request body media type is not `application/x-www-form-urlencoded` or `multipart/form-data`. If a value is explicitly defined, then the value of {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#encodingContentType `contentType`} (implicit or explicit) SHALL be ignored.
+   */
+  allowReserved?: boolean;
+  /**
+   * The Content-Type for encoding a specific property. Default value depends on the property type: for `object` - `application/json`; for `array` – the default is defined based on the inner type; for all other cases the default is `application/octet-stream`. The value can be a specific media type (e.g. `application/json`), a wildcard media type (e.g. `image/*`), or a comma-separated list of the two types.
+   */
+  contentType?: string;
+  /**
+   * When this is true, property values of type `array` or `object` generate separate parameters for each value of the array, or key-value-pair of the map. For other types of properties this property has no effect. When {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#encodingStyle `style`} is `form`, the default value is `true`. For all other styles, the default value is `false`. This property SHALL be ignored if the request body media type is not `application/x-www-form-urlencoded` or `multipart/form-data`. If a value is explicitly defined, then the value of {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#encodingContentType `contentType`} (implicit or explicit) SHALL be ignored.
+   */
+  explode?: boolean;
+  /**
+   * A map allowing additional information to be provided as headers, for example `Content-Disposition`. `Content-Type` is described separately and SHALL be ignored in this section. This property SHALL be ignored if the request body media type is not a `multipart`.
+   */
+  headers?: Record<string, HeaderObject | ReferenceObject>;
+  /**
+   * Describes how a specific property value will be serialized depending on its type. See {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#parameter-object Parameter Object} for details on the {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#parameterStyle `style`} property. The behavior follows the same values as `query` parameters, including default values. This property SHALL be ignored if the request body media type is not `application/x-www-form-urlencoded` or `multipart/form-data`. If a value is explicitly defined, then the value of {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#encodingContentType `contentType`} (implicit or explicit) SHALL be ignored.
+   */
+  style?: string;
 }
+
 /**
  * This object MAY be extended with {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#specification-extensions Specification Extensions}.
  *
@@ -1227,23 +981,24 @@ interface EncodingObject {
  * ```
  */
 interface ExampleObject {
-    /**
-     * Long description for the example. {@link https://spec.commonmark.org/ CommonMark syntax} MAY be used for rich text representation.
-     */
-    description?: string;
-    /**
-     * A URI that points to the literal example. This provides the capability to reference examples that cannot easily be included in JSON or YAML documents. The `value` field and `externalValue` field are mutually exclusive. See the rules for resolving {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#relative-references-in-uris Relative References}.
-     */
-    externalValue?: string;
-    /**
-     * Short description for the example.
-     */
-    summary?: string;
-    /**
-     * Embedded literal example. The `value` field and `externalValue` field are mutually exclusive. To represent examples of media types that cannot naturally represented in JSON or YAML, use a string value to contain the example, escaping where necessary.
-     */
-    value?: unknown;
+  /**
+   * Long description for the example. {@link https://spec.commonmark.org/ CommonMark syntax} MAY be used for rich text representation.
+   */
+  description?: string;
+  /**
+   * A URI that points to the literal example. This provides the capability to reference examples that cannot easily be included in JSON or YAML documents. The `value` field and `externalValue` field are mutually exclusive. See the rules for resolving {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#relative-references-in-uris Relative References}.
+   */
+  externalValue?: string;
+  /**
+   * Short description for the example.
+   */
+  summary?: string;
+  /**
+   * Embedded literal example. The `value` field and `externalValue` field are mutually exclusive. To represent examples of media types that cannot naturally represented in JSON or YAML, use a string value to contain the example, escaping where necessary.
+   */
+  value?: unknown;
 }
+
 /**
  * Allows referencing an external resource for extended documentation.
  *
@@ -1256,15 +1011,16 @@ interface ExampleObject {
  * ```
  */
 interface ExternalDocumentationObject {
-    /**
-     * A description of the target documentation. {@link https://spec.commonmark.org/ CommonMark syntax} MAY be used for rich text representation.
-     */
-    description?: string;
-    /**
-     * **REQUIRED**. The URL for the target documentation. This MUST be in the form of a URL.
-     */
-    url: string;
+  /**
+   * A description of the target documentation. {@link https://spec.commonmark.org/ CommonMark syntax} MAY be used for rich text representation.
+   */
+  description?: string;
+  /**
+   * **REQUIRED**. The URL for the target documentation. This MUST be in the form of a URL.
+   */
+  url: string;
 }
+
 /**
  * The Header Object follows the structure of the {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#parameter-object Parameter Object} with the following changes:
  *
@@ -1279,8 +1035,8 @@ interface ExternalDocumentationObject {
  *   type: integer
  * ```
  */
-interface HeaderObject extends Omit<ParameterObject, 'in' | 'name'> {
-}
+interface HeaderObject extends Omit<ParameterObject, 'in' | 'name'> {}
+
 /**
  * The object provides metadata about the API. The metadata MAY be used by the clients if needed, and MAY be presented in editing or documentation generation tools for convenience.
  *
@@ -1303,35 +1059,36 @@ interface HeaderObject extends Omit<ParameterObject, 'in' | 'name'> {
  * ```
  */
 interface InfoObject {
-    /**
-     * The contact information for the exposed API.
-     */
-    contact?: ContactObject;
-    /**
-     * A description of the API. {@link https://spec.commonmark.org/ CommonMark syntax} MAY be used for rich text representation.
-     */
-    description?: string;
-    /**
-     * The license information for the exposed API.
-     */
-    license?: LicenseObject;
-    /**
-     * A short summary of the API.
-     */
-    summary?: string;
-    /**
-     * A URL to the Terms of Service for the API. This MUST be in the form of a URL.
-     */
-    termsOfService?: string;
-    /**
-     * **REQUIRED**. The title of the API.
-     */
-    title: string;
-    /**
-     * **REQUIRED**. The version of the OpenAPI document (which is distinct from the {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#oasVersion OpenAPI Specification version} or the API implementation version).
-     */
-    version: string;
+  /**
+   * The contact information for the exposed API.
+   */
+  contact?: ContactObject;
+  /**
+   * A description of the API. {@link https://spec.commonmark.org/ CommonMark syntax} MAY be used for rich text representation.
+   */
+  description?: string;
+  /**
+   * The license information for the exposed API.
+   */
+  license?: LicenseObject;
+  /**
+   * A short summary of the API.
+   */
+  summary?: string;
+  /**
+   * A URL to the Terms of Service for the API. This MUST be in the form of a URL.
+   */
+  termsOfService?: string;
+  /**
+   * **REQUIRED**. The title of the API.
+   */
+  title: string;
+  /**
+   * **REQUIRED**. The version of the OpenAPI document (which is distinct from the {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#oasVersion OpenAPI Specification version} or the API implementation version).
+   */
+  version: string;
 }
+
 /**
  * License information for the exposed API.
  *
@@ -1344,19 +1101,20 @@ interface InfoObject {
  * ```
  */
 interface LicenseObject {
-    /**
-     * An {@link https://spdx.org/licenses/ SPDX} license expression for the API. The `identifier` field is mutually exclusive of the `url` field.
-     */
-    identifier?: string;
-    /**
-     * **REQUIRED**. The license name used for the API.
-     */
-    name: string;
-    /**
-     * A URL to the license used for the API. This MUST be in the form of a URL. The `url` field is mutually exclusive of the `identifier` field.
-     */
-    url?: string;
+  /**
+   * An {@link https://spdx.org/licenses/ SPDX} license expression for the API. The `identifier` field is mutually exclusive of the `url` field.
+   */
+  identifier?: string;
+  /**
+   * **REQUIRED**. The license name used for the API.
+   */
+  name: string;
+  /**
+   * A URL to the license used for the API. This MUST be in the form of a URL. The `url` field is mutually exclusive of the `identifier` field.
+   */
+  url?: string;
 }
+
 /**
  * The `Link object` represents a possible design-time link for a response. The presence of a link does not guarantee the caller's ability to successfully invoke it, rather it provides a known relationship and traversal mechanism between responses and other operations.
  *
@@ -1505,31 +1263,32 @@ interface LicenseObject {
  * Runtime expressions preserve the type of the referenced value. Expressions can be embedded into string values by surrounding the expression with `{}` curly braces.
  */
 interface LinkObject {
-    /**
-     * A description of the link. {@link https://spec.commonmark.org/ CommonMark syntax} MAY be used for rich text representation.
-     */
-    description?: string;
-    /**
-     * The name of an _existing_, resolvable OAS operation, as defined with a unique `operationId`. This field is mutually exclusive of the `operationRef` field.
-     */
-    operationId?: string;
-    /**
-     * A relative or absolute URI reference to an OAS operation. This field is mutually exclusive of the `operationId` field, and MUST point to an {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#operation-object Operation Object}. Relative `operationRef` values MAY be used to locate an existing {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#operation-object Operation Object} in the OpenAPI definition. See the rules for resolving {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#relative-references-in-uris Relative References}.
-     */
-    operationRef?: string;
-    /**
-     * A map representing parameters to pass to an operation as specified with `operationId` or identified via `operationRef`. The key is the parameter name to be used, whereas the value can be a constant or an expression to be evaluated and passed to the linked operation. The parameter name can be qualified using the {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#parameterIn parameter location} `[{in}.]{name}` for operations that use the same parameter name in different locations (e.g. path.id).
-     */
-    parameters?: Record<string, unknown | string>;
-    /**
-     * A literal value or {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#runtime-expressions {expression}} to use as a request body when calling the target operation.
-     */
-    requestBody?: unknown | string;
-    /**
-     * A server object to be used by the target operation.
-     */
-    server?: ServerObject;
+  /**
+   * A description of the link. {@link https://spec.commonmark.org/ CommonMark syntax} MAY be used for rich text representation.
+   */
+  description?: string;
+  /**
+   * The name of an _existing_, resolvable OAS operation, as defined with a unique `operationId`. This field is mutually exclusive of the `operationRef` field.
+   */
+  operationId?: string;
+  /**
+   * A relative or absolute URI reference to an OAS operation. This field is mutually exclusive of the `operationId` field, and MUST point to an {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#operation-object Operation Object}. Relative `operationRef` values MAY be used to locate an existing {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#operation-object Operation Object} in the OpenAPI definition. See the rules for resolving {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#relative-references-in-uris Relative References}.
+   */
+  operationRef?: string;
+  /**
+   * A map representing parameters to pass to an operation as specified with `operationId` or identified via `operationRef`. The key is the parameter name to be used, whereas the value can be a constant or an expression to be evaluated and passed to the linked operation. The parameter name can be qualified using the {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#parameterIn parameter location} `[{in}.]{name}` for operations that use the same parameter name in different locations (e.g. path.id).
+   */
+  parameters?: Record<string, unknown | string>;
+  /**
+   * A literal value or {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#runtime-expressions {expression}} to use as a request body when calling the target operation.
+   */
+  requestBody?: unknown | string;
+  /**
+   * A server object to be used by the target operation.
+   */
+  server?: ServerObject;
 }
+
 /**
  * Each Media Type Object provides schema and examples for the media type identified by its key.
  *
@@ -1563,24 +1322,25 @@ interface LinkObject {
  *       $ref: "#/components/examples/frog-example"
  * ```
  */
-interface MediaTypeObject {
-    /**
-     * A map between a property name and its encoding information. The key, being the property name, MUST exist in the schema as a property. The encoding object SHALL only apply to `requestBody` objects when the media type is `multipart` or `application/x-www-form-urlencoded`.
-     */
-    encoding?: Record<string, EncodingObject>;
-    /**
-     * Example of the media type. The example object SHOULD be in the correct format as specified by the media type. The `example` field is mutually exclusive of the `examples` field. Furthermore, if referencing a `schema` which contains an example, the `example` value SHALL _override_ the example provided by the schema.
-     */
-    example?: unknown;
-    /**
-     * Examples of the media type. Each example object SHOULD match the media type and specified schema if present. The `examples` field is mutually exclusive of the `example` field. Furthermore, if referencing a `schema` which contains an example, the `examples` value SHALL _override_ the example provided by the schema.
-     */
-    examples?: Record<string, ExampleObject | ReferenceObject>;
-    /**
-     * The schema defining the content of the request, response, or parameter.
-     */
-    schema?: SchemaObject;
+interface MediaTypeObject$1 {
+  /**
+   * A map between a property name and its encoding information. The key, being the property name, MUST exist in the schema as a property. The encoding object SHALL only apply to `requestBody` objects when the media type is `multipart` or `application/x-www-form-urlencoded`.
+   */
+  encoding?: Record<string, EncodingObject>;
+  /**
+   * Example of the media type. The example object SHOULD be in the correct format as specified by the media type. The `example` field is mutually exclusive of the `examples` field. Furthermore, if referencing a `schema` which contains an example, the `example` value SHALL _override_ the example provided by the schema.
+   */
+  example?: unknown;
+  /**
+   * Examples of the media type. Each example object SHOULD match the media type and specified schema if present. The `examples` field is mutually exclusive of the `example` field. Furthermore, if referencing a `schema` which contains an example, the `examples` value SHALL _override_ the example provided by the schema.
+   */
+  examples?: Record<string, ExampleObject | ReferenceObject>;
+  /**
+   * The schema defining the content of the request, response, or parameter.
+   */
+  schema?: SchemaObject;
 }
+
 /**
  * Configuration details for a supported OAuth Flow
  *
@@ -1605,46 +1365,48 @@ interface MediaTypeObject {
  * ```
  */
 interface OAuthFlowObject {
-    /**
-     * **REQUIRED**. The authorization URL to be used for this flow. This MUST be in the form of a URL. The OAuth2 standard requires the use of TLS.
-     */
-    authorizationUrl: string;
-    /**
-     * The URL to be used for obtaining refresh tokens. This MUST be in the form of a URL. The OAuth2 standard requires the use of TLS.
-     */
-    refreshUrl?: string;
-    /**
-     * **REQUIRED**. The available scopes for the OAuth2 security scheme. A map between the scope name and a short description for it. The map MAY be empty.
-     */
-    scopes: Record<string, string>;
-    /**
-     * **REQUIRED**. The token URL to be used for this flow. This MUST be in the form of a URL. The OAuth2 standard requires the use of TLS.
-     */
-    tokenUrl: string;
+  /**
+   * **REQUIRED**. The authorization URL to be used for this flow. This MUST be in the form of a URL. The OAuth2 standard requires the use of TLS.
+   */
+  authorizationUrl: string;
+  /**
+   * The URL to be used for obtaining refresh tokens. This MUST be in the form of a URL. The OAuth2 standard requires the use of TLS.
+   */
+  refreshUrl?: string;
+  /**
+   * **REQUIRED**. The available scopes for the OAuth2 security scheme. A map between the scope name and a short description for it. The map MAY be empty.
+   */
+  scopes: Record<string, string>;
+  /**
+   * **REQUIRED**. The token URL to be used for this flow. This MUST be in the form of a URL. The OAuth2 standard requires the use of TLS.
+   */
+  tokenUrl: string;
 }
+
 /**
  * Allows configuration of the supported OAuth Flows.
  *
  * This object MAY be extended with {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#specification-extensions Specification Extensions}.
  */
 interface OAuthFlowsObject {
-    /**
-     * Configuration for the OAuth Authorization Code flow. Previously called `accessCode` in OpenAPI 2.0.
-     */
-    authorizationCode?: OAuthFlowObject;
-    /**
-     * Configuration for the OAuth Client Credentials flow. Previously called `application` in OpenAPI 2.0.
-     */
-    clientCredentials?: OAuthFlowObject;
-    /**
-     * Configuration for the OAuth Implicit flow
-     */
-    implicit?: OAuthFlowObject;
-    /**
-     * Configuration for the OAuth Resource Owner Password flow
-     */
-    password?: OAuthFlowObject;
+  /**
+   * Configuration for the OAuth Authorization Code flow. Previously called `accessCode` in OpenAPI 2.0.
+   */
+  authorizationCode?: OAuthFlowObject;
+  /**
+   * Configuration for the OAuth Client Credentials flow. Previously called `application` in OpenAPI 2.0.
+   */
+  clientCredentials?: OAuthFlowObject;
+  /**
+   * Configuration for the OAuth Implicit flow
+   */
+  implicit?: OAuthFlowObject;
+  /**
+   * Configuration for the OAuth Resource Owner Password flow
+   */
+  password?: OAuthFlowObject;
 }
+
 /**
  * Describes a single API operation on a path.
  *
@@ -1695,55 +1457,56 @@ interface OAuthFlowsObject {
  * ```
  */
 interface OperationObject {
-    /**
-     * A map of possible out-of band callbacks related to the parent operation. The key is a unique identifier for the Callback Object. Each value in the map is a {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#callback-object Callback Object} that describes a request that may be initiated by the API provider and the expected responses.
-     */
-    callbacks?: Record<string, CallbackObject | ReferenceObject>;
-    /**
-     * Declares this operation to be deprecated. Consumers SHOULD refrain from usage of the declared operation. Default value is `false`.
-     */
-    deprecated?: boolean;
-    /**
-     * A verbose explanation of the operation behavior. {@link https://spec.commonmark.org/ CommonMark syntax} MAY be used for rich text representation.
-     */
-    description?: string;
-    /**
-     * Additional external documentation for this operation.
-     */
-    externalDocs?: ExternalDocumentationObject;
-    /**
-     * Unique string used to identify the operation. The id MUST be unique among all operations described in the API. The operationId value is **case-sensitive**. Tools and libraries MAY use the operationId to uniquely identify an operation, therefore, it is RECOMMENDED to follow common programming naming conventions.
-     */
-    operationId?: string;
-    /**
-     * A list of parameters that are applicable for this operation. If a parameter is already defined at the {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#pathItemParameters Path Item}, the new definition will override it but can never remove it. The list MUST NOT include duplicated parameters. A unique parameter is defined by a combination of a {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#parameterName name} and {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#parameterIn location}. The list can use the {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#reference-object Reference Object} to link to parameters that are defined at the {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#componentsParameters OpenAPI Object's components/parameters}.
-     */
-    parameters?: ReadonlyArray<ParameterObject | ReferenceObject>;
-    /**
-     * The request body applicable for this operation. The `requestBody` is fully supported in HTTP methods where the HTTP 1.1 specification {@link https://datatracker.ietf.org/doc/html/rfc7231#section-4.3.1 RFC7231} has explicitly defined semantics for request bodies. In other cases where the HTTP spec is vague (such as {@link https://datatracker.ietf.org/doc/html/rfc7231#section-4.3.1 GET}, {@link https://datatracker.ietf.org/doc/html/rfc7231#section-4.3.2 HEAD} and {@link https://datatracker.ietf.org/doc/html/rfc7231#section-4.3.5 DELETE}), `requestBody` is permitted but does not have well-defined semantics and SHOULD be avoided if possible.
-     */
-    requestBody?: RequestBodyObject | ReferenceObject;
-    /**
-     * The list of possible responses as they are returned from executing this operation.
-     */
-    responses?: ResponsesObject;
-    /**
-     * A declaration of which security mechanisms can be used for this operation. The list of values includes alternative security requirement objects that can be used. Only one of the security requirement objects need to be satisfied to authorize a request. To make security optional, an empty security requirement (`{}`) can be included in the array. This definition overrides any declared top-level {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#oasSecurity `security`}. To remove a top-level security declaration, an empty array can be used.
-     */
-    security?: ReadonlyArray<SecurityRequirementObject>;
-    /**
-     * An alternative `server` array to service this operation. If an alternative `server` object is specified at the Path Item Object or Root level, it will be overridden by this value.
-     */
-    servers?: ReadonlyArray<ServerObject>;
-    /**
-     * A short summary of what the operation does.
-     */
-    summary?: string;
-    /**
-     * A list of tags for API documentation control. Tags can be used for logical grouping of operations by resources or any other qualifier.
-     */
-    tags?: ReadonlyArray<string>;
+  /**
+   * A map of possible out-of band callbacks related to the parent operation. The key is a unique identifier for the Callback Object. Each value in the map is a {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#callback-object Callback Object} that describes a request that may be initiated by the API provider and the expected responses.
+   */
+  callbacks?: Record<string, CallbackObject | ReferenceObject>;
+  /**
+   * Declares this operation to be deprecated. Consumers SHOULD refrain from usage of the declared operation. Default value is `false`.
+   */
+  deprecated?: boolean;
+  /**
+   * A verbose explanation of the operation behavior. {@link https://spec.commonmark.org/ CommonMark syntax} MAY be used for rich text representation.
+   */
+  description?: string;
+  /**
+   * Additional external documentation for this operation.
+   */
+  externalDocs?: ExternalDocumentationObject;
+  /**
+   * Unique string used to identify the operation. The id MUST be unique among all operations described in the API. The operationId value is **case-sensitive**. Tools and libraries MAY use the operationId to uniquely identify an operation, therefore, it is RECOMMENDED to follow common programming naming conventions.
+   */
+  operationId?: string;
+  /**
+   * A list of parameters that are applicable for this operation. If a parameter is already defined at the {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#pathItemParameters Path Item}, the new definition will override it but can never remove it. The list MUST NOT include duplicated parameters. A unique parameter is defined by a combination of a {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#parameterName name} and {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#parameterIn location}. The list can use the {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#reference-object Reference Object} to link to parameters that are defined at the {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#componentsParameters OpenAPI Object's components/parameters}.
+   */
+  parameters?: ReadonlyArray<ParameterObject | ReferenceObject>;
+  /**
+   * The request body applicable for this operation. The `requestBody` is fully supported in HTTP methods where the HTTP 1.1 specification {@link https://datatracker.ietf.org/doc/html/rfc7231#section-4.3.1 RFC7231} has explicitly defined semantics for request bodies. In other cases where the HTTP spec is vague (such as {@link https://datatracker.ietf.org/doc/html/rfc7231#section-4.3.1 GET}, {@link https://datatracker.ietf.org/doc/html/rfc7231#section-4.3.2 HEAD} and {@link https://datatracker.ietf.org/doc/html/rfc7231#section-4.3.5 DELETE}), `requestBody` is permitted but does not have well-defined semantics and SHOULD be avoided if possible.
+   */
+  requestBody?: RequestBodyObject | ReferenceObject;
+  /**
+   * The list of possible responses as they are returned from executing this operation.
+   */
+  responses?: ResponsesObject;
+  /**
+   * A declaration of which security mechanisms can be used for this operation. The list of values includes alternative security requirement objects that can be used. Only one of the security requirement objects need to be satisfied to authorize a request. To make security optional, an empty security requirement (`{}`) can be included in the array. This definition overrides any declared top-level {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#oasSecurity `security`}. To remove a top-level security declaration, an empty array can be used.
+   */
+  security?: ReadonlyArray<SecurityRequirementObject>;
+  /**
+   * An alternative `server` array to service this operation. If an alternative `server` object is specified at the Path Item Object or Root level, it will be overridden by this value.
+   */
+  servers?: ReadonlyArray<ServerObject>;
+  /**
+   * A short summary of what the operation does.
+   */
+  summary?: string;
+  /**
+   * A list of tags for API documentation control. Tags can be used for logical grouping of operations by resources or any other qualifier.
+   */
+  tags?: ReadonlyArray<string>;
 }
+
 /**
  * Describes a single operation parameter.
  *
@@ -1842,62 +1605,70 @@ interface OperationObject {
  * ```
  */
 interface ParameterObject {
-    /**
-     * Sets the ability to pass empty-valued parameters. This is valid only for `query` parameters and allows sending a parameter with an empty value. Default value is `false`. If {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#parameterStyle `style`} is used, and if behavior is `n/a` (cannot be serialized), the value of `allowEmptyValue` SHALL be ignored. Use of this property is NOT RECOMMENDED, as it is likely to be removed in a later revision.
-     */
-    allowEmptyValue?: boolean;
-    /**
-     * Determines whether the parameter value SHOULD allow reserved characters, as defined by {@link https://datatracker.ietf.org/doc/html/rfc3986#section-2.2 RFC3986} `:/?#[]@!$&'()*+,;=` to be included without percent-encoding. This property only applies to parameters with an `in` value of `query`. The default value is `false`.
-     */
-    allowReserved?: boolean;
-    /**
-     * A map containing the representations for the parameter. The key is the media type and the value describes it. The map MUST only contain one entry.
-     */
-    content?: Record<string, MediaTypeObject>;
-    /**
-     * Specifies that a parameter is deprecated and SHOULD be transitioned out of usage. Default value is `false`.
-     */
-    deprecated?: boolean;
-    /**
-     * A brief description of the parameter. This could contain examples of use. {@link https://spec.commonmark.org/ CommonMark syntax} MAY be used for rich text representation.
-     */
-    description?: string;
-    /**
-     * Example of the parameter's potential value. The example SHOULD match the specified schema and encoding properties if present. The `example` field is mutually exclusive of the `examples` field. Furthermore, if referencing a `schema` that contains an example, the `example` value SHALL _override_ the example provided by the schema. To represent examples of media types that cannot naturally be represented in JSON or YAML, a string value can contain the example with escaping where necessary.
-     */
-    example?: unknown;
-    /**
-     * Examples of the parameter's potential value. Each example SHOULD contain a value in the correct format as specified in the parameter encoding. The `examples` field is mutually exclusive of the `example` field. Furthermore, if referencing a `schema` that contains an example, the `examples` value SHALL _override_ the example provided by the schema.
-     */
-    examples?: Record<string, ExampleObject | ReferenceObject>;
-    /**
-     * When this is true, parameter values of type `array` or `object` generate separate parameters for each value of the array or key-value pair of the map. For other types of parameters this property has no effect. When {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#parameterStyle `style`} is `form`, the default value is `true`. For all other styles, the default value is `false`.
-     */
-    explode?: boolean;
-    /**
-     * **REQUIRED**. The location of the parameter. Possible values are `"query"`, `"header"`, `"path"` or `"cookie"`.
-     */
-    in: 'cookie' | 'header' | 'path' | 'query';
-    /**
-     * **REQUIRED**. The name of the parameter. Parameter names are _case sensitive_.
-     * - If {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#parameterIn `in`} is `"path"`, the `name` field MUST correspond to a template expression occurring within the {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#pathsPath path} field in the {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#paths-object Paths Object}. See {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#path-templating Path Templating} for further information.
-     * - If {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#parameterIn `in`} is `"header"` and the `name` field is `"Accept"`, `"Content-Type"` or `"Authorization"`, the parameter definition SHALL be ignored.
-     * - For all other cases, the `name` corresponds to the parameter name used by the {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#parameterIn `in`} property.
-     */
-    name: string;
-    /**
-     * Determines whether this parameter is mandatory. If the {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#parameterIn parameter location} is `"path"`, this property is **REQUIRED** and its value MUST be `true`. Otherwise, the property MAY be included and its default value is `false`.
-     */
-    required?: boolean;
-    /**
-     * The schema defining the type used for the parameter.
-     */
-    schema?: SchemaObject;
-    /**
-     * Describes how the parameter value will be serialized depending on the type of the parameter value. Default values (based on value of `in`): for `query` - `form`; for `path` - `simple`; for `header` - `simple`; for `cookie` - `form`.
-     */
-    style?: 'deepObject' | 'form' | 'label' | 'matrix' | 'pipeDelimited' | 'simple' | 'spaceDelimited';
+  /**
+   * Sets the ability to pass empty-valued parameters. This is valid only for `query` parameters and allows sending a parameter with an empty value. Default value is `false`. If {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#parameterStyle `style`} is used, and if behavior is `n/a` (cannot be serialized), the value of `allowEmptyValue` SHALL be ignored. Use of this property is NOT RECOMMENDED, as it is likely to be removed in a later revision.
+   */
+  allowEmptyValue?: boolean;
+  /**
+   * Determines whether the parameter value SHOULD allow reserved characters, as defined by {@link https://datatracker.ietf.org/doc/html/rfc3986#section-2.2 RFC3986} `:/?#[]@!$&'()*+,;=` to be included without percent-encoding. This property only applies to parameters with an `in` value of `query`. The default value is `false`.
+   */
+  allowReserved?: boolean;
+  /**
+   * A map containing the representations for the parameter. The key is the media type and the value describes it. The map MUST only contain one entry.
+   */
+  content?: Record<string, MediaTypeObject$1>;
+  /**
+   * Specifies that a parameter is deprecated and SHOULD be transitioned out of usage. Default value is `false`.
+   */
+  deprecated?: boolean;
+  /**
+   * A brief description of the parameter. This could contain examples of use. {@link https://spec.commonmark.org/ CommonMark syntax} MAY be used for rich text representation.
+   */
+  description?: string;
+  /**
+   * Example of the parameter's potential value. The example SHOULD match the specified schema and encoding properties if present. The `example` field is mutually exclusive of the `examples` field. Furthermore, if referencing a `schema` that contains an example, the `example` value SHALL _override_ the example provided by the schema. To represent examples of media types that cannot naturally be represented in JSON or YAML, a string value can contain the example with escaping where necessary.
+   */
+  example?: unknown;
+  /**
+   * Examples of the parameter's potential value. Each example SHOULD contain a value in the correct format as specified in the parameter encoding. The `examples` field is mutually exclusive of the `example` field. Furthermore, if referencing a `schema` that contains an example, the `examples` value SHALL _override_ the example provided by the schema.
+   */
+  examples?: Record<string, ExampleObject | ReferenceObject>;
+  /**
+   * When this is true, parameter values of type `array` or `object` generate separate parameters for each value of the array or key-value pair of the map. For other types of parameters this property has no effect. When {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#parameterStyle `style`} is `form`, the default value is `true`. For all other styles, the default value is `false`.
+   */
+  explode?: boolean;
+  /**
+   * **REQUIRED**. The location of the parameter. Possible values are `"query"`, `"header"`, `"path"` or `"cookie"`.
+   */
+  in: 'cookie' | 'header' | 'path' | 'query';
+  /**
+   * **REQUIRED**. The name of the parameter. Parameter names are _case sensitive_.
+   * - If {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#parameterIn `in`} is `"path"`, the `name` field MUST correspond to a template expression occurring within the {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#pathsPath path} field in the {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#paths-object Paths Object}. See {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#path-templating Path Templating} for further information.
+   * - If {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#parameterIn `in`} is `"header"` and the `name` field is `"Accept"`, `"Content-Type"` or `"Authorization"`, the parameter definition SHALL be ignored.
+   * - For all other cases, the `name` corresponds to the parameter name used by the {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#parameterIn `in`} property.
+   */
+  name: string;
+  /**
+   * Determines whether this parameter is mandatory. If the {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#parameterIn parameter location} is `"path"`, this property is **REQUIRED** and its value MUST be `true`. Otherwise, the property MAY be included and its default value is `false`.
+   */
+  required?: boolean;
+  /**
+   * The schema defining the type used for the parameter.
+   */
+  schema?: SchemaObject;
+  /**
+   * Describes how the parameter value will be serialized depending on the type of the parameter value. Default values (based on value of `in`): for `query` - `form`; for `path` - `simple`; for `header` - `simple`; for `cookie` - `form`.
+   */
+  style?:
+    | 'deepObject'
+    | 'form'
+    | 'label'
+    | 'matrix'
+    | 'pipeDelimited'
+    | 'simple'
+    | 'spaceDelimited';
 }
+
 /**
  * Describes the operations available on a single path. A Path Item MAY be empty, due to {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#security-filtering ACL constraints}. The path itself is still exposed to the documentation viewer but they will not know which operations and parameters are available.
  *
@@ -1937,59 +1708,60 @@ interface ParameterObject {
  * ```
  */
 interface PathItemObject {
-    /**
-     * Allows for a referenced definition of this path item. The referenced structure MUST be in the form of a {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#path-item-object Path Item Object}. In case a Path Item Object field appears both in the defined object and the referenced object, the behavior is undefined. See the rules for resolving {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#relative-references-in-uris Relative References}.
-     */
-    $ref?: string;
-    /**
-     * A definition of a DELETE operation on this path.
-     */
-    delete?: OperationObject;
-    /**
-     * An optional, string description, intended to apply to all operations in this path. {@link https://spec.commonmark.org/ CommonMark syntax} MAY be used for rich text representation.
-     */
-    description?: string;
-    /**
-     * A definition of a GET operation on this path.
-     */
-    get?: OperationObject;
-    /**
-     * A definition of a HEAD operation on this path.
-     */
-    head?: OperationObject;
-    /**
-     * A definition of a OPTIONS operation on this path.
-     */
-    options?: OperationObject;
-    /**
-     * A list of parameters that are applicable for all the operations described under this path. These parameters can be overridden at the operation level, but cannot be removed there. The list MUST NOT include duplicated parameters. A unique parameter is defined by a combination of a {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#parameterName name} and {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#parameterIn location}. The list can use the {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#reference-object Reference Object} to link to parameters that are defined at the {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#componentsParameters OpenAPI Object's components/parameters}.
-     */
-    parameters?: ReadonlyArray<ParameterObject | ReferenceObject>;
-    /**
-     * A definition of a PATCH operation on this path.
-     */
-    patch?: OperationObject;
-    /**
-     * A definition of a POST operation on this path.
-     */
-    post?: OperationObject;
-    /**
-     * A definition of a PUT operation on this path.
-     */
-    put?: OperationObject;
-    /**
-     * An alternative `server` array to service all operations in this path.
-     */
-    servers?: ReadonlyArray<ServerObject>;
-    /**
-     * An optional, string summary, intended to apply to all operations in this path.
-     */
-    summary?: string;
-    /**
-     * A definition of a TRACE operation on this path.
-     */
-    trace?: OperationObject;
+  /**
+   * Allows for a referenced definition of this path item. The referenced structure MUST be in the form of a {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#path-item-object Path Item Object}. In case a Path Item Object field appears both in the defined object and the referenced object, the behavior is undefined. See the rules for resolving {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#relative-references-in-uris Relative References}.
+   */
+  $ref?: string;
+  /**
+   * A definition of a DELETE operation on this path.
+   */
+  delete?: OperationObject;
+  /**
+   * An optional, string description, intended to apply to all operations in this path. {@link https://spec.commonmark.org/ CommonMark syntax} MAY be used for rich text representation.
+   */
+  description?: string;
+  /**
+   * A definition of a GET operation on this path.
+   */
+  get?: OperationObject;
+  /**
+   * A definition of a HEAD operation on this path.
+   */
+  head?: OperationObject;
+  /**
+   * A definition of a OPTIONS operation on this path.
+   */
+  options?: OperationObject;
+  /**
+   * A list of parameters that are applicable for all the operations described under this path. These parameters can be overridden at the operation level, but cannot be removed there. The list MUST NOT include duplicated parameters. A unique parameter is defined by a combination of a {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#parameterName name} and {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#parameterIn location}. The list can use the {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#reference-object Reference Object} to link to parameters that are defined at the {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#componentsParameters OpenAPI Object's components/parameters}.
+   */
+  parameters?: ReadonlyArray<ParameterObject | ReferenceObject>;
+  /**
+   * A definition of a PATCH operation on this path.
+   */
+  patch?: OperationObject;
+  /**
+   * A definition of a POST operation on this path.
+   */
+  post?: OperationObject;
+  /**
+   * A definition of a PUT operation on this path.
+   */
+  put?: OperationObject;
+  /**
+   * An alternative `server` array to service all operations in this path.
+   */
+  servers?: ReadonlyArray<ServerObject>;
+  /**
+   * An optional, string summary, intended to apply to all operations in this path.
+   */
+  summary?: string;
+  /**
+   * A definition of a TRACE operation on this path.
+   */
+  trace?: OperationObject;
 }
+
 /**
  * Holds the relative paths to the individual endpoints and their operations. The path is appended to the URL from the {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#server-object `Server Object`} in order to construct the full URL. The Paths MAY be empty, due to {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#security-filtering Access Control List (ACL) constraints}.
  *
@@ -2036,11 +1808,12 @@ interface PathItemObject {
  * ```
  */
 interface PathsObject {
-    /**
-     * A relative path to an individual endpoint. The field name MUST begin with a forward slash (`/`). The path is **appended** (no relative URL resolution) to the expanded URL from the {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#server-object `Server Object`}'s `url` field in order to construct the full URL. {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#path-templating Path templating} is allowed. When matching URLs, concrete (non-templated) paths would be matched before their templated counterparts. Templated paths with the same hierarchy but different templated names MUST NOT exist as they are identical. In case of ambiguous matching, it's up to the tooling to decide which one to use.
-     */
-    [path: `/${string}`]: PathItemObject;
+  /**
+   * A relative path to an individual endpoint. The field name MUST begin with a forward slash (`/`). The path is **appended** (no relative URL resolution) to the expanded URL from the {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#server-object `Server Object`}'s `url` field in order to construct the full URL. {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#path-templating Path templating} is allowed. When matching URLs, concrete (non-templated) paths would be matched before their templated counterparts. Templated paths with the same hierarchy but different templated names MUST NOT exist as they are identical. In case of ambiguous matching, it's up to the tooling to decide which one to use.
+   */
+  [path: `/${string}`]: PathItemObject;
 }
+
 /**
  * A simple object to allow referencing other components in the OpenAPI document, internally and externally.
  *
@@ -2074,19 +1847,20 @@ interface PathsObject {
  * ```
  */
 interface ReferenceObject {
-    /**
-     * **REQUIRED**. The reference identifier. This MUST be in the form of a URI.
-     */
-    $ref: string;
-    /**
-     * A description which by default SHOULD override that of the referenced component. {@link https://spec.commonmark.org/ CommonMark syntax} MAY be used for rich text representation. If the referenced object-type does not allow a `description` field, then this field has no effect.
-     */
-    description?: string;
-    /**
-     * A short summary which by default SHOULD override that of the referenced component. If the referenced object-type does not allow a `summary` field, then this field has no effect.
-     */
-    summary?: string;
+  /**
+   * **REQUIRED**. The reference identifier. This MUST be in the form of a URI.
+   */
+  $ref: string;
+  /**
+   * A description which by default SHOULD override that of the referenced component. {@link https://spec.commonmark.org/ CommonMark syntax} MAY be used for rich text representation. If the referenced object-type does not allow a `description` field, then this field has no effect.
+   */
+  description?: string;
+  /**
+   * A short summary which by default SHOULD override that of the referenced component. If the referenced object-type does not allow a `summary` field, then this field has no effect.
+   */
+  summary?: string;
 }
+
 /**
  * Describes a single request body.
  *
@@ -2139,19 +1913,20 @@ interface ReferenceObject {
  * ```
  */
 interface RequestBodyObject {
-    /**
-     * **REQUIRED**. The content of the request body. The key is a media type or {@link https://tools.ietf.org/html/rfc7231#appendix-D media type range} and the value describes it. For requests that match multiple keys, only the most specific key is applicable. e.g. text/plain overrides text/*
-     */
-    content: Record<string, MediaTypeObject>;
-    /**
-     * A brief description of the request body. This could contain examples of use. {@link https://spec.commonmark.org/ CommonMark syntax} MAY be used for rich text representation.
-     */
-    description?: string;
-    /**
-     * Determines if the request body is required in the request. Defaults to `false`.
-     */
-    required?: boolean;
+  /**
+   * **REQUIRED**. The content of the request body. The key is a media type or {@link https://tools.ietf.org/html/rfc7231#appendix-D media type range} and the value describes it. For requests that match multiple keys, only the most specific key is applicable. e.g. text/plain overrides text/*
+   */
+  content: Record<string, MediaTypeObject$1>;
+  /**
+   * A brief description of the request body. This could contain examples of use. {@link https://spec.commonmark.org/ CommonMark syntax} MAY be used for rich text representation.
+   */
+  description?: string;
+  /**
+   * Determines if the request body is required in the request. Defaults to `false`.
+   */
+  required?: boolean;
 }
+
 /**
  * Describes a single response from an API Operation, including design-time, static `links` to operations based on the response.
  *
@@ -2213,24 +1988,25 @@ interface RequestBodyObject {
  * description: object created
  * ```
  */
-interface ResponseObject {
-    /**
-     * A map containing descriptions of potential response payloads. The key is a media type or {@link https://datatracker.ietf.org/doc/html/rfc7231#appendix-D media type range} and the value describes it. For responses that match multiple keys, only the most specific key is applicable. e.g. text/plain overrides text/*
-     */
-    content?: Record<string, MediaTypeObject>;
-    /**
-     * **REQUIRED**. A description of the response. {@link https://spec.commonmark.org/ CommonMark syntax} MAY be used for rich text representation.
-     */
-    description: string;
-    /**
-     * Maps a header name to its definition. {@link https://datatracker.ietf.org/doc/html/rfc7230#page-22 RFC7230} states header names are case insensitive. If a response header is defined with the name `"Content-Type"`, it SHALL be ignored.
-     */
-    headers?: Record<string, HeaderObject | ReferenceObject>;
-    /**
-     * A map of operations links that can be followed from the response. The key of the map is a short name for the link, following the naming constraints of the names for {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#components-object Component Objects}.
-     */
-    links?: Record<string, LinkObject | ReferenceObject>;
+interface ResponseObject {
+  /**
+   * A map containing descriptions of potential response payloads. The key is a media type or {@link https://datatracker.ietf.org/doc/html/rfc7231#appendix-D media type range} and the value describes it. For responses that match multiple keys, only the most specific key is applicable. e.g. text/plain overrides text/*
+   */
+  content?: Record<string, MediaTypeObject$1>;
+  /**
+   * **REQUIRED**. A description of the response. {@link https://spec.commonmark.org/ CommonMark syntax} MAY be used for rich text representation.
+   */
+  description: string;
+  /**
+   * Maps a header name to its definition. {@link https://datatracker.ietf.org/doc/html/rfc7230#page-22 RFC7230} states header names are case insensitive. If a response header is defined with the name `"Content-Type"`, it SHALL be ignored.
+   */
+  headers?: Record<string, HeaderObject | ReferenceObject>;
+  /**
+   * A map of operations links that can be followed from the response. The key of the map is a short name for the link, following the naming constraints of the names for {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#components-object Component Objects}.
+   */
+  links?: Record<string, LinkObject | ReferenceObject>;
 }
+
 /**
  * A container for the expected responses of an operation. The container maps a HTTP response code to the expected response.
  *
@@ -2261,15 +2037,16 @@ interface ResponseObject {
  * ```
  */
 interface ResponsesObject {
-    /**
-     * Any {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#http-status-codes HTTP status code} can be used as the property name, but only one property per code, to describe the expected response for that HTTP status code. This field MUST be enclosed in quotation marks (for example, "200") for compatibility between JSON and YAML. To define a range of response codes, this field MAY contain the uppercase wildcard character `X`. For example, `2XX` represents all response codes between `[200-299]`. Only the following range definitions are allowed: `1XX`, `2XX`, `3XX`, `4XX`, and `5XX`. If a response is defined using an explicit code, the explicit code definition takes precedence over the range definition for that code.
-     */
-    [statusCode: string]: ResponseObject | ReferenceObject | undefined;
-    /**
-     * The documentation of responses other than the ones declared for specific HTTP response codes. Use this field to cover undeclared responses.
-     */
-    default?: ResponseObject | ReferenceObject;
+  /**
+   * Any {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#http-status-codes HTTP status code} can be used as the property name, but only one property per code, to describe the expected response for that HTTP status code. This field MUST be enclosed in quotation marks (for example, "200") for compatibility between JSON and YAML. To define a range of response codes, this field MAY contain the uppercase wildcard character `X`. For example, `2XX` represents all response codes between `[200-299]`. Only the following range definitions are allowed: `1XX`, `2XX`, `3XX`, `4XX`, and `5XX`. If a response is defined using an explicit code, the explicit code definition takes precedence over the range definition for that code.
+   */
+  [statusCode: string]: ResponseObject | ReferenceObject | undefined;
+  /**
+   * The documentation of responses other than the ones declared for specific HTTP response codes. Use this field to cover undeclared responses.
+   */
+  default?: ResponseObject | ReferenceObject;
 }
+
 /**
  * The Schema Object allows the definition of input and output data types. These types can be objects, but also primitives and arrays. This object is a superset of the {@link https://tools.ietf.org/html/draft-bhutton-json-schema-00 JSON Schema Specification Draft 2020-12}.
  *
@@ -2294,26 +2071,8 @@ interface ResponsesObject {
  *
  * This object MAY be extended with {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#specification-extensions Specification Extensions}, though as noted, additional properties MAY omit the `x-` prefix within this object.
  */
-interface SchemaObject {
-    /**
-     * Adds support for polymorphism. The discriminator is an object name that is used to differentiate between other schemas which may satisfy the payload description. See {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#composition-and-inheritance-polymorphism Composition and Inheritance} for more details.
-     */
-    discriminator?: DiscriminatorObject;
-    /**
-     * A free-form property to include an example of an instance for this schema. To represent examples that cannot be naturally represented in JSON or YAML, a string value can be used to contain the example with escaping where necessary.
-     *
-     * **Deprecated**: The `example` property has been deprecated in favor of the JSON Schema `examples` keyword. Use of `example` is discouraged, and later versions of this specification may remove it.
-     */
-    example?: unknown;
-    /**
-     * Additional external documentation for this schema.
-     */
-    externalDocs?: ExternalDocumentationObject;
-    /**
-     * This MAY be used only on properties schemas. It has no effect on root schemas. Adds additional metadata to describe the XML representation of this property.
-     */
-    xml?: XMLObject;
-}
+interface SchemaObject extends JsonSchemaDraft2020_12 {}
+
 /**
  * Lists the required security schemes to execute this operation. The name used for each property MUST correspond to a security scheme declared in the {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#componentsSecuritySchemes Security Schemes} under the {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#components-object Components Object}.
  *
@@ -2349,11 +2108,12 @@ interface SchemaObject {
  * ```
  */
 interface SecurityRequirementObject {
-    /**
-     * Each name MUST correspond to a security scheme which is declared in the {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#componentsSecuritySchemes Security Schemes} under the {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#components-object Components Object}. If the security scheme is of type `"oauth2"` or `"openIdConnect"`, then the value is a list of scope names required for the execution, and the list MAY be empty if authorization does not require a specified scope. For other security scheme types, the array MAY contain a list of role names which are required for the execution, but are not otherwise defined or exchanged in-band.
-     */
-    [name: string]: ReadonlyArray<string>;
+  /**
+   * Each name MUST correspond to a security scheme which is declared in the {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#componentsSecuritySchemes Security Schemes} under the {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#components-object Components Object}. If the security scheme is of type `"oauth2"` or `"openIdConnect"`, then the value is a list of scope names required for the execution, and the list MAY be empty if authorization does not require a specified scope. For other security scheme types, the array MAY contain a list of role names which are required for the execution, but are not otherwise defined or exchanged in-band.
+   */
+  [name: string]: ReadonlyArray<string>;
 }
+
 /**
  * Defines a security scheme that can be used by the operations.
  *
@@ -2399,60 +2159,67 @@ interface SecurityRequirementObject {
  * ```
  */
 type SecuritySchemeObject = {
-    /**
-     * A description for security scheme. {@link https://spec.commonmark.org/ CommonMark syntax} MAY be used for rich text representation.
-     */
-    description?: string;
-} & ({
-    /**
-     * **REQUIRED**. The location of the API key. Valid values are "query", "header" or "cookie".
-     */
-    in: 'cookie' | 'header' | 'query';
-    /**
-     * **REQUIRED**. The name of the header, query or cookie parameter to be used.
-     */
-    name: string;
-    /**
-     * **REQUIRED**. The type of the security scheme. Valid values are `"apiKey"`, `"http"`, `"mutualTLS"`, `"oauth2"`, `"openIdConnect"`.
-     */
-    type: 'apiKey';
-} | {
-    /**
-     * A hint to the client to identify how the bearer token is formatted. Bearer tokens are usually generated by an authorization server, so this information is primarily for documentation purposes.
-     */
-    bearerFormat?: string;
-    /**
-     * **REQUIRED**. The name of the HTTP Authorization scheme to be used in the {@link https://tools.ietf.org/html/rfc7235#section-5.1 Authorization header as defined in RFC7235}. The values used SHOULD be registered in the {@link https://www.iana.org/assignments/http-authschemes/http-authschemes.xhtml IANA Authentication Scheme registry}.
-     */
-    scheme: string;
-    /**
-     * **REQUIRED**. The type of the security scheme. Valid values are `"apiKey"`, `"http"`, `"mutualTLS"`, `"oauth2"`, `"openIdConnect"`.
-     */
-    type: 'http';
-} | {
-    /**
-     * **REQUIRED**. The type of the security scheme. Valid values are `"apiKey"`, `"http"`, `"mutualTLS"`, `"oauth2"`, `"openIdConnect"`.
-     */
-    type: 'mutualTLS';
-} | {
-    /**
-     * **REQUIRED**. An object containing configuration information for the flow types supported.
-     */
-    flows: OAuthFlowsObject;
-    /**
-     * **REQUIRED**. The type of the security scheme. Valid values are `"apiKey"`, `"http"`, `"mutualTLS"`, `"oauth2"`, `"openIdConnect"`.
-     */
-    type: 'oauth2';
-} | {
-    /**
-     * **REQUIRED**. OpenId Connect URL to discover OAuth2 configuration values. This MUST be in the form of a URL. The OpenID Connect standard requires the use of TLS.
-     */
-    openIdConnectUrl: string;
-    /**
-     * **REQUIRED**. The type of the security scheme. Valid values are `"apiKey"`, `"http"`, `"mutualTLS"`, `"oauth2"`, `"openIdConnect"`.
-     */
-    type: 'openIdConnect';
-});
+  /**
+   * A description for security scheme. {@link https://spec.commonmark.org/ CommonMark syntax} MAY be used for rich text representation.
+   */
+  description?: string;
+} & (
+  | {
+      /**
+       * **REQUIRED**. The location of the API key. Valid values are "query", "header" or "cookie".
+       */
+      in: 'cookie' | 'header' | 'query';
+      /**
+       * **REQUIRED**. The name of the header, query or cookie parameter to be used.
+       */
+      name: string;
+      /**
+       * **REQUIRED**. The type of the security scheme. Valid values are `"apiKey"`, `"http"`, `"mutualTLS"`, `"oauth2"`, `"openIdConnect"`.
+       */
+      type: 'apiKey';
+    }
+  | {
+      /**
+       * A hint to the client to identify how the bearer token is formatted. Bearer tokens are usually generated by an authorization server, so this information is primarily for documentation purposes.
+       */
+      bearerFormat?: string;
+      /**
+       * **REQUIRED**. The name of the HTTP Authorization scheme to be used in the {@link https://tools.ietf.org/html/rfc7235#section-5.1 Authorization header as defined in RFC7235}. The values used SHOULD be registered in the {@link https://www.iana.org/assignments/http-authschemes/http-authschemes.xhtml IANA Authentication Scheme registry}.
+       */
+      scheme: string;
+      /**
+       * **REQUIRED**. The type of the security scheme. Valid values are `"apiKey"`, `"http"`, `"mutualTLS"`, `"oauth2"`, `"openIdConnect"`.
+       */
+      type: 'http';
+    }
+  | {
+      /**
+       * **REQUIRED**. The type of the security scheme. Valid values are `"apiKey"`, `"http"`, `"mutualTLS"`, `"oauth2"`, `"openIdConnect"`.
+       */
+      type: 'mutualTLS';
+    }
+  | {
+      /**
+       * **REQUIRED**. An object containing configuration information for the flow types supported.
+       */
+      flows: OAuthFlowsObject;
+      /**
+       * **REQUIRED**. The type of the security scheme. Valid values are `"apiKey"`, `"http"`, `"mutualTLS"`, `"oauth2"`, `"openIdConnect"`.
+       */
+      type: 'oauth2';
+    }
+  | {
+      /**
+       * **REQUIRED**. OpenId Connect URL to discover OAuth2 configuration values. This MUST be in the form of a URL. The OpenID Connect standard requires the use of TLS.
+       */
+      openIdConnectUrl: string;
+      /**
+       * **REQUIRED**. The type of the security scheme. Valid values are `"apiKey"`, `"http"`, `"mutualTLS"`, `"oauth2"`, `"openIdConnect"`.
+       */
+      type: 'openIdConnect';
+    }
+);
+
 /**
  * An object representing a Server.
  *
@@ -2465,38 +2232,40 @@ type SecuritySchemeObject = {
  * ```
  */
 interface ServerObject {
-    /**
-     * An optional string describing the host designated by the URL. {@link https://spec.commonmark.org/ CommonMark syntax} MAY be used for rich text representation.
-     */
-    description?: string;
-    /**
-     * **REQUIRED**. A URL to the target host. This URL supports Server Variables and MAY be relative, to indicate that the host location is relative to the location where the OpenAPI document is being served. Variable substitutions will be made when a variable is named in `{`brackets`}`.
-     */
-    url: string;
-    /**
-     * A map between a variable name and its value. The value is used for substitution in the server's URL template.
-     */
-    variables?: Record<string, ServerVariableObject>;
+  /**
+   * An optional string describing the host designated by the URL. {@link https://spec.commonmark.org/ CommonMark syntax} MAY be used for rich text representation.
+   */
+  description?: string;
+  /**
+   * **REQUIRED**. A URL to the target host. This URL supports Server Variables and MAY be relative, to indicate that the host location is relative to the location where the OpenAPI document is being served. Variable substitutions will be made when a variable is named in `{`brackets`}`.
+   */
+  url: string;
+  /**
+   * A map between a variable name and its value. The value is used for substitution in the server's URL template.
+   */
+  variables?: Record<string, ServerVariableObject>;
 }
+
 /**
  * An object representing a Server Variable for server URL template substitution.
  *
  * This object MAY be extended with {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#specification-extensions Specification Extensions}.
  */
 interface ServerVariableObject {
-    /**
-     * **REQUIRED**. The default value to use for substitution, which SHALL be sent if an alternate value is _not_ supplied. Note this behavior is different than the {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#schema-object Schema Object's} treatment of default values, because in those cases parameter values are optional. If the {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#serverVariableEnum `enum`} is defined, the value MUST exist in the enum's values.
-     */
-    default: string;
-    /**
-     * An optional description for the server variable. {@link https://spec.commonmark.org/ CommonMark syntax} MAY be used for rich text representation.
-     */
-    description?: string;
-    /**
-     * An enumeration of string values to be used if the substitution options are from a limited set. The array MUST NOT be empty.
-     */
-    enum?: ReadonlyArray<string>;
+  /**
+   * **REQUIRED**. The default value to use for substitution, which SHALL be sent if an alternate value is _not_ supplied. Note this behavior is different than the {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#schema-object Schema Object's} treatment of default values, because in those cases parameter values are optional. If the {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#serverVariableEnum `enum`} is defined, the value MUST exist in the enum's values.
+   */
+  default: string;
+  /**
+   * An optional description for the server variable. {@link https://spec.commonmark.org/ CommonMark syntax} MAY be used for rich text representation.
+   */
+  description?: string;
+  /**
+   * An enumeration of string values to be used if the substitution options are from a limited set. The array MUST NOT be empty.
+   */
+  enum?: ReadonlyArray<string>;
 }
+
 /**
  * Adds metadata to a single tag that is used by the {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#operation-object Operation Object}. It is not mandatory to have a Tag Object per tag defined in the Operation Object instances.
  *
@@ -2509,19 +2278,20 @@ interface ServerVariableObject {
  * ```
  */
 interface TagObject {
-    /**
-     * A description for the tag. {@link https://spec.commonmark.org/ CommonMark syntax} MAY be used for rich text representation.
-     */
-    description?: string;
-    /**
-     * Additional external documentation for this tag.
-     */
-    externalDocs?: ExternalDocumentationObject;
-    /**
-     * **REQUIRED**. The name of the tag.
-     */
-    name: string;
+  /**
+   * A description for the tag. {@link https://spec.commonmark.org/ CommonMark syntax} MAY be used for rich text representation.
+   */
+  description?: string;
+  /**
+   * Additional external documentation for this tag.
+   */
+  externalDocs?: ExternalDocumentationObject;
+  /**
+   * **REQUIRED**. The name of the tag.
+   */
+  name: string;
 }
+
 /**
  * A metadata object that allows for more fine-tuned XML model definitions.
  *
@@ -2714,36 +2484,812 @@ interface TagObject {
  * </aliens>
  * ```
  */
-interface XMLObject {
+interface XMLObject {
+  /**
+   * Declares whether the property definition translates to an attribute instead of an element. Default value is `false`.
+   */
+  attribute?: boolean;
+  /**
+   * Replaces the name of the element/attribute used for the described schema property. When defined within `items`, it will affect the name of the individual XML elements within the list. When defined alongside `type` being `array` (outside the `items`), it will affect the wrapping element and only if `wrapped` is `true`. If `wrapped` is `false`, it will be ignored.
+   */
+  name?: string;
+  /**
+   * The URI of the namespace definition. This MUST be in the form of an absolute URI.
+   */
+  namespace?: string;
+  /**
+   * The prefix to be used for the {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#xmlName name}.
+   */
+  prefix?: string;
+  /**
+   * MAY be used only for an array definition. Signifies whether the array is wrapped (for example, `<books><book/><book/></books>`) or unwrapped (`<book/><book/>`). Default value is `false`. The definition takes effect only when defined alongside `type` being `array` (outside the `items`).
+   */
+  wrapped?: boolean;
+}
+
+interface Config$7 extends PluginName<'@hey-api/schemas'> {
+  /**
+   * Customise the schema name. By default, `{{name}}Schema` is used. `name` is a
+   * valid JavaScript/TypeScript identifier, e.g. if your schema name is
+   * "Foo-Bar", `name` value would be "FooBar".
+   */
+  nameBuilder?: (
+    name: string,
+    schema: OpenApiSchema | OpenApiSchema$1 | SchemaObject,
+  ) => string;
+  /**
+   * Name of the generated file.
+   * @default 'schemas'
+   */
+  output?: string;
+  /**
+   * Choose schema type to generate. Select 'form' if you don't want
+   * descriptions to reduce bundle size and you plan to use schemas
+   * for form validation
+   * @default 'json'
+   */
+  type?: 'form' | 'json';
+}
+
+type IRMediaType = 'form-data' | 'json' | 'url-search-params';
+
+interface IROperationObject {
+  body?: IRBodyObject;
+  deprecated?: boolean;
+  description?: string;
+  id: string;
+  parameters?: IRParametersObject;
+  responses?: IRResponsesObject;
+  // TODO: parser - add more properties
+  // security?: ReadonlyArray<SecurityRequirementObject>;
+  // servers?: ReadonlyArray<ServerObject>;
+  summary?: string;
+  tags?: ReadonlyArray<string>;
+}
+
+interface IRBodyObject {
+  mediaType: string;
+  /**
+   * Does body control pagination? We handle only simple values
+   * for now, up to 1 nested field.
+   */
+  pagination?: boolean | string;
+  required?: boolean;
+  schema: IRSchemaObject;
+  type?: IRMediaType;
+}
+
+interface IRParametersObject {
+  cookie?: Record<string, IRParameterObject>;
+  header?: Record<string, IRParameterObject>;
+  path?: Record<string, IRParameterObject>;
+  query?: Record<string, IRParameterObject>;
+}
+
+interface IRParameterObject {
+  /**
+   * Endpoint parameters must specify their location.
+   */
+  location: 'cookie' | 'header' | 'path' | 'query';
+  name: string;
+  /**
+   * Does this parameter control pagination? We handle only simple values
+   * for now, up to 1 nested field.
+   */
+  pagination?: boolean | string;
+  required?: boolean;
+  schema: IRSchemaObject;
+}
+
+interface IRResponsesObject {
+  /**
+   * Any {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#http-status-codes HTTP status code} can be used as the property name, but only one property per code, to describe the expected response for that HTTP status code. This field MUST be enclosed in quotation marks (for example, "200") for compatibility between JSON and YAML. To define a range of response codes, this field MAY contain the uppercase wildcard character `X`. For example, `2XX` represents all response codes between `[200-299]`. Only the following range definitions are allowed: `1XX`, `2XX`, `3XX`, `4XX`, and `5XX`. If a response is defined using an explicit code, the explicit code definition takes precedence over the range definition for that code.
+   */
+  [statusCode: string]: IRResponseObject | undefined;
+  /**
+   * The documentation of responses other than the ones declared for specific HTTP response codes. Use this field to cover undeclared responses.
+   */
+  default?: IRResponseObject;
+}
+
+interface IRResponseObject {
+  // TODO: parser - handle headers, links, and possibly other media types?
+  schema: IRSchemaObject;
+}
+
+interface IRSchemaObject
+  extends Pick<
+    JsonSchemaDraft2020_12,
+    '$ref' | 'const' | 'deprecated' | 'description' | 'required' | 'title'
+  > {
+  /**
+   * If the schema is intended to be used as an object property, it can be
+   * marked as read-only or write-only.
+   */
+  accessScope?: 'read' | 'write';
+  /**
+   * If type is `object`, `additionalProperties` can be used to either define
+   * a schema for properties not included in `properties` or disallow such
+   * properties altogether.
+   */
+  additionalProperties?: IRSchemaObject | false;
+  /**
+   * Any string value is accepted as `format`.
+   */
+  format?: JsonSchemaDraft2020_12['format'] | 'binary' | 'integer';
+  /**
+   * If schema resolves into multiple items instead of a simple `type`, they
+   * will be included in `items` array.
+   */
+  items?: ReadonlyArray<IRSchemaObject>;
+  /**
+   * When resolving a list of items, we need to know the relationship between
+   * them. `logicalOperator` specifies this logical relationship.
+   * @default 'or'
+   */
+  logicalOperator?: 'and' | 'or';
+  /**
+   * When type is `object`, `properties` will contain a map of its properties.
+   */
+  properties?: Record<string, IRSchemaObject>;
+  /**
+   * Each schema eventually resolves into `type`.
+   */
+  type?:
+    | 'array'
+    | 'boolean'
+    | 'enum'
+    | 'null'
+    | 'number'
+    | 'object'
+    | 'string'
+    | 'tuple'
+    | 'unknown'
+    | 'void';
+}
+
+interface Config$6 extends PluginName<'@hey-api/services'> {
+  /**
+   * Group operation methods into service classes? When enabled, you can
+   * select which classes to export with `services.include` and/or
+   * transform their names with `services.name`.
+   *
+   * Note that by enabling this option, your services will **NOT**
+   * support {@link https://developer.mozilla.org/docs/Glossary/Tree_shaking tree-shaking}.
+   * For this reason, it is disabled by default.
+   * @default false
+   */
+  asClass?: boolean;
+  /**
+   * Filter endpoints to be included in the generated services.
+   * The provided string should be a regular expression where matched
+   * results will be included in the output. The input pattern this
+   * string will be tested against is `{method} {path}`. For example,
+   * you can match `POST /api/v1/foo` with `^POST /api/v1/foo$`.
+   */
+  filter?: string;
+  /**
+   * Include only service classes with names matching regular expression
+   *
+   * This option has no effect if `services.asClass` is `false`.
+   */
+  include?: string;
+  /**
+   * Customise the name of methods within the service. By default, {@link IROperationObject.id} or {@link Operation.name} is used.
+   */
+  methodNameBuilder?: (operation: IROperationObject | Operation) => string;
+  // TODO: parser - rename operationId option to something like inferId?: boolean
+  /**
+   * Use operation ID to generate operation names?
+   * @default true
+   */
+  operationId?: boolean;
+  /**
+   * Name of the generated file.
+   * @default 'services'
+   */
+  output?: string;
+  /**
+   * Define shape of returned value from service calls
+   * @default 'body'
+   * @deprecated
+   */
+  response?: 'body' | 'response';
+  /**
+   * Customize the generated service class names. The name variable is
+   * obtained from your OpenAPI specification tags.
+   *
+   * This option has no effect if `services.asClass` is `false`.
+   * @default '{{name}}Service'
+   */
+  serviceNameBuilder?: string;
+}
+
+interface Config$5 extends PluginName<'@hey-api/transformers'> {
+  /**
+   * Convert date strings into Date objects?
+   * @default false
+   */
+  dates?: boolean;
+  /**
+   * Name of the generated file.
+   * @default 'transformers'
+   */
+  output?: string;
+}
+
+interface Config$4 extends PluginName<'@hey-api/types'> {
+  /**
+   * Generate enum definitions?
+   * @default false
+   */
+  enums?: 'javascript' | 'typescript' | 'typescript+namespace' | false;
+  /**
+   * Include only types matching regular expression
+   */
+  include?: string;
+  /**
+   * Name of the generated file.
+   * @default 'types'
+   */
+  output?: string;
+  /**
+   * Use your preferred naming pattern
+   * @default 'preserve'
+   */
+  style?: 'PascalCase' | 'preserve';
+  /**
+   * Generate a tree of types containing all operations? It will be named
+   * $OpenApiTs.
+   * @default false
+   */
+  tree?: boolean;
+}
+
+interface Config$3 extends PluginName<'@tanstack/react-query'> {
+  /**
+   * Generate {@link https://tanstack.com/query/v5/docs/framework/react/reference/infiniteQueryOptions `infiniteQueryOptions()`} helpers? These will be generated from GET and POST requests where a pagination parameter is detected.
+   * @default true
+   */
+  infiniteQueryOptions?: boolean;
+  /**
+   * Generate {@link https://tanstack.com/query/v5/docs/framework/react/reference/useMutation `useMutation()`} helpers? These will be generated from DELETE, PATCH, POST, and PUT requests.
+   * @default true
+   */
+  mutationOptions?: boolean;
+  /**
+   * Name of the generated file.
+   * @default '@tanstack/react-query'
+   */
+  output?: string;
+  /**
+   * Generate {@link https://tanstack.com/query/v5/docs/framework/react/reference/queryOptions `queryOptions()`} helpers?
+   * These will be generated from all requests.
+   * @default true
+   */
+  queryOptions?: boolean;
+}
+
+interface Config$2 extends PluginName<'@tanstack/solid-query'> {
+  /**
+   * Generate `createInfiniteQuery()` helpers? These will be generated from GET and POST requests where a pagination parameter is detected.
+   * @default true
+   */
+  infiniteQueryOptions?: boolean;
+  /**
+   * Generate `createMutation()` helpers? These will be generated from DELETE, PATCH, POST, and PUT requests.
+   * @default true
+   */
+  mutationOptions?: boolean;
+  /**
+   * Name of the generated file.
+   * @default '@tanstack/solid-query'
+   */
+  output?: string;
+  /**
+   * Generate {@link https://tanstack.com/query/v5/docs/framework/solid/reference/createQuery `createQuery()`} helpers?
+   * These will be generated from all requests.
+   * @default true
+   */
+  queryOptions?: boolean;
+}
+
+interface Config$1 extends PluginName<'@tanstack/svelte-query'> {
+  /**
+   * Generate `createInfiniteQuery()` helpers? These will be generated from GET and POST requests where a pagination parameter is detected.
+   * @default true
+   */
+  infiniteQueryOptions?: boolean;
+  /**
+   * Generate {@link https://tanstack.com/query/v5/docs/framework/svelte/reference/functions/createmutation `createMutation()`} helpers? These will be generated from DELETE, PATCH, POST, and PUT requests.
+   * @default true
+   */
+  mutationOptions?: boolean;
+  /**
+   * Name of the generated file.
+   * @default '@tanstack/svelte-query'
+   */
+  output?: string;
+  /**
+   * Generate {@link https://tanstack.com/query/v5/docs/framework/svelte/reference/functions/createquery `createQuery()`} helpers?
+   * These will be generated from all requests.
+   * @default true
+   */
+  queryOptions?: boolean;
+}
+
+interface Config extends PluginName<'@tanstack/vue-query'> {
+  /**
+   * Generate {@link https://tanstack.com/query/v5/docs/framework/vue/reference/infiniteQueryOptions `infiniteQueryOptions()`} helpers? These will be generated from GET and POST requests where a pagination parameter is detected.
+   * @default true
+   */
+  infiniteQueryOptions?: boolean;
+  /**
+   * Generate {@link https://tanstack.com/query/v5/docs/framework/vue/reference/useMutation `useMutation()`} helpers? These will be generated from DELETE, PATCH, POST, and PUT requests.
+   * @default true
+   */
+  mutationOptions?: boolean;
+  /**
+   * Name of the generated file.
+   * @default '@tanstack/vue-query'
+   */
+  output?: string;
+  /**
+   * Generate {@link https://tanstack.com/query/v5/docs/framework/vue/guides/query-options `queryOptions()`} helpers?
+   * These will be generated from all requests.
+   * @default true
+   */
+  queryOptions?: boolean;
+}
+
+/**
+ * User-facing plugin types.
+ */
+type UserPlugins = UserConfig$1<Config$7> | UserConfig$1<Config$6> | UserConfig$1<Config$5> | UserConfig$1<Config$4> | UserConfig$1<Config$3> | UserConfig$1<Config$2> | UserConfig$1<Config$1> | UserConfig$1<Config>;
+
+declare const CLIENTS: readonly ["@hey-api/client-axios", "@hey-api/client-fetch", "legacy/angular", "legacy/axios", "legacy/fetch", "legacy/node", "legacy/xhr"];
+type Client$2 = (typeof CLIENTS)[number];
+interface ClientConfig {
+    /**
+     * Manually set base in OpenAPI config instead of inferring from server value
+     * @deprecated
+     */
+    base?: string;
+    /**
+     * HTTP client to generate
+     */
+    client?: Client$2 | false | {
+        /**
+         * Bundle the client module? Set this to true if you're using a client
+         * package and don't want to declare it as a separate dependency.
+         * When true, the client module will be generated from the client
+         * package and bundled with the rest of the generated output. This is
+         * useful if you're repackaging the output, publishing it to other users,
+         * and you don't want them to install any dependencies.
+         * @default false
+         */
+        bundle?: boolean;
+        /**
+         * HTTP client to generate
+         */
+        name: Client$2;
+    };
+    /**
+     * Path to the config file. Set this value if you don't use the default
+     * config file name, or it's not located in the project root.
+     */
+    configFile?: string;
+    /**
+     * Run in debug mode?
+     * @default false
+     */
+    debug?: boolean;
+    /**
+     * Skip writing files to disk?
+     * @default false
+     */
+    dryRun?: boolean;
+    /**
+     * Opt-in to the experimental parser?
+     * @default false
+     */
+    experimentalParser?: boolean;
+    /**
+     * Generate core client classes?
+     * @default true
+     */
+    exportCore?: boolean;
+    /**
+     * The relative location of the OpenAPI spec
+     */
+    input: string | Record<string, unknown>;
+    /**
+     * Custom client class name. Please note this option is deprecated and
+     * will be removed in favor of clients.
+     * @link https://heyapi.dev/openapi-ts/migrating.html#deprecated-name
+     * @deprecated
+     */
+    name?: string;
+    /**
+     * The relative location of the output folder
+     */
+    output: string | {
+        /**
+         * Process output folder with formatter?
+         * @default false
+         */
+        format?: 'biome' | 'prettier' | false;
+        /**
+         * Process output folder with linter?
+         * @default false
+         */
+        lint?: 'biome' | 'eslint' | false;
+        /**
+         * The relative location of the output folder
+         */
+        path: string;
+    };
+    /**
+     * Plugins are used to generate artifacts from provided input.
+     */
+    plugins?: ReadonlyArray<UserPlugins['name'] | UserPlugins>;
+    /**
+     * Path to custom request file. Please note this option is deprecated and
+     * will be removed in favor of clients.
+     * @link https://heyapi.dev/openapi-ts/migrating.html#deprecated-request
+     * @deprecated
+     */
+    request?: string;
+    /**
+     * Use options or arguments functions. Please note this option is deprecated and
+     * will be removed in favor of clients.
+     * @link https://heyapi.dev/openapi-ts/migrating.html#deprecated-useoptions
+     * @deprecated
+     * @default true
+     */
+    useOptions?: boolean;
+}
+interface UserConfig extends ClientConfig {
+}
+
+interface Dictionary<T = unknown> {
+    [key: string]: T;
+}
+
+/**
+ * {@link} https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#reference-object
+ */
+interface OpenApiReference$1 {
+    $ref?: string;
+}
+
+/**
+ * {@link} https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#example-object
+ */
+interface OpenApiExample extends OpenApiReference$1 {
+    description?: string;
+    externalValue?: string;
+    summary?: string;
+    value?: unknown;
+}
+
+interface WithEnumExtension {
+    'x-enum-descriptions'?: ReadonlyArray<string>;
+    'x-enum-varnames'?: ReadonlyArray<string>;
+    'x-enumNames'?: ReadonlyArray<string>;
+}
+
+/**
+ * {@link} https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#discriminator-object
+ */
+interface OpenApiDiscriminator {
+    mapping?: Dictionary<string>;
+    propertyName: string;
+}
+
+/**
+ * {@link} https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#external-documentation-object
+ */
+interface OpenApiExternalDocs$1 {
+    description?: string;
+    url: string;
+}
+
+/**
+ * {@link} https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#xml-object
+ */
+interface OpenApiXml$1 {
+    attribute?: boolean;
+    name?: string;
+    namespace?: string;
+    prefix?: string;
+    wrapped?: boolean;
+}
+
+/**
+ * {@link} https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#schema-object
+ */
+interface OpenApiSchema$1 extends OpenApiReference$1, WithEnumExtension {
+    additionalProperties?: boolean | OpenApiSchema$1;
+    allOf?: OpenApiSchema$1[];
+    anyOf?: OpenApiSchema$1[];
+    const?: string | number | boolean | null;
+    default?: unknown;
+    deprecated?: boolean;
+    description?: string;
+    discriminator?: OpenApiDiscriminator;
+    enum?: (string | number)[];
+    example?: unknown;
+    exclusiveMaximum?: boolean;
+    exclusiveMinimum?: boolean;
+    externalDocs?: OpenApiExternalDocs$1;
+    format?: 'binary' | 'boolean' | 'byte' | 'date-time' | 'date' | 'double' | 'float' | 'int32' | 'int64' | 'password' | 'string';
+    items?: OpenApiSchema$1;
+    maxItems?: number;
+    maxLength?: number;
+    maxProperties?: number;
+    maximum?: number;
+    minItems?: number;
+    minLength?: number;
+    minProperties?: number;
+    minimum?: number;
+    multipleOf?: number;
+    not?: OpenApiSchema$1[];
+    nullable?: boolean;
+    oneOf?: OpenApiSchema$1[];
+    pattern?: string;
+    prefixItems?: OpenApiSchema$1[];
+    properties?: Dictionary<OpenApiSchema$1>;
+    readOnly?: boolean;
+    required?: string[];
+    title?: string;
+    type?: string | string[];
+    uniqueItems?: boolean;
+    writeOnly?: boolean;
+    xml?: OpenApiXml$1;
+}
+
+/**
+ * add only one type for now as that's needed to resolve the reported issue,
+ * more types should be added though
+ * {@link https://github.com/hey-api/openapi-ts/issues/612}
+ */
+type MediaType = 'application/json';
+/**
+ * encoding interface should be added, not adding it for now as it's not needed
+ * to resolve the issue reported
+ * {@link https://github.com/hey-api/openapi-ts/issues/612}
+ */
+interface MediaTypeObject {
+    example?: unknown;
+    examples?: Dictionary<OpenApiExample>;
+    schema: OpenApiSchema$1;
+}
+/**
+ * {@link} https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#parameter-object
+ */
+interface OpenApiParameter extends OpenApiReference$1 {
+    allowEmptyValue?: boolean;
+    allowReserved?: boolean;
+    content?: Record<MediaType, MediaTypeObject>;
+    deprecated?: boolean;
+    description?: string;
+    example?: unknown;
+    examples?: Dictionary<OpenApiExample>;
+    explode?: boolean;
+    in: 'cookie' | 'formData' | 'header' | 'path' | 'query';
+    name: string;
+    nullable?: boolean;
+    required?: boolean;
+    schema?: OpenApiSchema$1;
+    style?: string;
+}
+
+interface Enum {
+    customDescription?: string;
+    customName?: string;
+    description?: string;
+    value: string | number;
+}
+interface OperationParameter extends Model {
+    in: 'body' | 'cookie' | 'formData' | 'header' | 'path' | 'query';
+    mediaType: string | null;
+    prop: string;
+}
+interface OperationParameters extends Pick<Model, '$refs' | 'imports'> {
+    parameters: OperationParameter[];
+    parametersBody: OperationParameter | null;
+    parametersCookie: OperationParameter[];
+    parametersForm: OperationParameter[];
+    parametersHeader: OperationParameter[];
+    parametersPath: OperationParameter[];
+    parametersQuery: OperationParameter[];
+}
+interface OperationResponse extends Model {
+    code: number | 'default' | '1XX' | '2XX' | '3XX' | '4XX' | '5XX';
+    in: 'header' | 'response';
+    responseTypes: Array<'error' | 'success'>;
+}
+type Method = 'CONNECT' | 'DELETE' | 'GET' | 'HEAD' | 'OPTIONS' | 'PATCH' | 'POST' | 'PUT' | 'TRACE';
+interface Operation$1 extends OperationParameters {
+    deprecated: boolean;
+    description: string | null;
     /**
-     * Declares whether the property definition translates to an attribute instead of an element. Default value is `false`.
+     * The operationId from OpenAPI specification.
      */
-    attribute?: boolean;
+    id: string | null;
+    method: Method;
+    name: string;
+    path: string;
+    responseHeader: string | null;
     /**
-     * Replaces the name of the element/attribute used for the described schema property. When defined within `items`, it will affect the name of the individual XML elements within the list. When defined alongside `type` being `array` (outside the `items`), it will affect the wrapping element and only if `wrapped` is `true`. If `wrapped` is `false`, it will be ignored.
+     * All operation responses defined in OpenAPI specification.
+     * Sorted by status code.
      */
-    name?: string;
+    responses: OperationResponse[];
+    summary: string | null;
+    tags: string[] | null;
+}
+interface Schema {
+    default?: unknown;
+    exclusiveMaximum?: boolean;
+    exclusiveMinimum?: boolean;
+    format?: 'binary' | 'boolean' | 'byte' | 'date-time' | 'date' | 'double' | 'float' | 'int32' | 'int64' | 'password' | 'string';
+    isDefinition: boolean;
+    isNullable: boolean;
+    isReadOnly: boolean;
+    isRequired: boolean;
+    maxItems?: number;
+    maxLength?: number;
+    maxProperties?: number;
+    maximum?: number;
+    minItems?: number;
+    minLength?: number;
+    minProperties?: number;
+    minimum?: number;
+    multipleOf?: number;
+    pattern?: string;
+    uniqueItems?: boolean;
+}
+interface ModelMeta {
     /**
-     * The URI of the namespace definition. This MUST be in the form of an absolute URI.
+     * Ref to the type in OpenAPI specification.
      */
-    namespace?: string;
+    $ref: string;
     /**
-     * The prefix to be used for the {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#xmlName name}.
+     * Name passed to the initial `getModel()` call.
      */
-    prefix?: string;
+    name: string;
+}
+interface Model extends Schema {
+    /**
+     * **Experimental.** Contains list of original refs so they can be used
+     * to access the schema from anywhere instead of relying on string name.
+     * This allows us to do things like detect type of ref.
+     */
+    $refs: string[];
+    base: string;
+    deprecated?: boolean;
+    description: string | null;
+    enum: Enum[];
+    enums: Model[];
+    export: 'all-of' | 'any-of' | 'array' | 'const' | 'dictionary' | 'enum' | 'generic' | 'interface' | 'one-of' | 'reference';
+    imports: string[];
+    in: OperationParameter['in'] | OpenApiParameter['in'] | OperationResponse['in'] | '';
+    link: Model | Model[] | null;
+    meta?: ModelMeta;
+    /**
+     * @deprecated use `meta.name` instead
+     */
+    name: string;
+    properties: Model[];
+    template: string | null;
+    type: string;
+}
+interface Client$1 {
+    models: Model[];
+    operations: Operation$1[];
+    server: string;
     /**
-     * MAY be used only for an array definition. Signifies whether the array is wrapped (for example, `<books><book/><book/></books>`) or unwrapped (`<book/><book/>`). Default value is `false`. The definition takes effect only when defined alongside `type` being `array` (outside the `items`).
+     * Map of generated types where type names are keys. This is used to track
+     * uniquely generated types as we may want to deduplicate if there are
+     * multiple definitions with the same name but different value, or if we
+     * want to transform names.
      */
+    types: Record<string, ModelMeta>;
+    version: string;
+}
+
+interface OpenApiV3_0_3 {
+  /**
+   * **REQUIRED**. This string MUST be the {@link https://semver.org/spec/v2.0.0.html semantic version number} of the {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.0.3.md#versions OpenAPI Specification version} that the OpenAPI document uses. The `openapi` field SHOULD be used by tooling specifications and clients to interpret the OpenAPI document. This is _not_ related to the API {@link https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.0.3.md#infoVersion `info.version`} string.
+   */
+  openapi: '3.0.3';
+  // TODO
+}
+
+/**
+ * {@link} https://github.com/OAI/OpenAPI-Specification/blob/main/versions/2.0.md#external-documentation-object
+ */
+interface OpenApiExternalDocs {
+    description?: string;
+    url: string;
+}
+
+interface WithNullableExtension {
+    'x-nullable'?: boolean;
+}
+
+/**
+ * {@link} https://github.com/OAI/OpenAPI-Specification/blob/main/versions/2.0.md#reference-object
+ */
+interface OpenApiReference {
+    $ref?: string;
+}
+
+/**
+ * {@link} https://github.com/OAI/OpenAPI-Specification/blob/main/versions/2.0.md#xml-object
+ */
+interface OpenApiXml {
+    attribute?: boolean;
+    name?: string;
+    namespace?: string;
+    prefix?: string;
     wrapped?: boolean;
 }
 
+/**
+ * {@link} https://github.com/OAI/OpenAPI-Specification/blob/main/versions/2.0.md#schema-object
+ */
+interface OpenApiSchema extends OpenApiReference, WithEnumExtension, WithNullableExtension {
+    additionalProperties?: boolean | OpenApiSchema;
+    allOf?: OpenApiSchema[];
+    default?: unknown;
+    description?: string;
+    discriminator?: string;
+    enum?: (string | number)[];
+    example?: unknown;
+    exclusiveMaximum?: boolean;
+    exclusiveMinimum?: boolean;
+    externalDocs?: OpenApiExternalDocs;
+    format?: 'int32' | 'int64' | 'float' | 'double' | 'string' | 'boolean' | 'byte' | 'binary' | 'date' | 'date-time' | 'password';
+    items?: OpenApiSchema;
+    maxItems?: number;
+    maxLength?: number;
+    maxProperties?: number;
+    maximum?: number;
+    minItems?: number;
+    minLength?: number;
+    minProperties?: number;
+    minimum?: number;
+    multipleOf?: number;
+    pattern?: string;
+    properties?: Dictionary<OpenApiSchema>;
+    readOnly?: boolean;
+    required?: string[];
+    title?: string;
+    type?: string;
+    uniqueItems?: boolean;
+    xml?: OpenApiXml;
+}
+
+interface Operation extends Omit<Operation$1, 'tags'> {
+    service: string;
+}
+interface Service extends Pick<Model, '$refs' | 'imports' | 'name'> {
+    operations: Operation[];
+}
+interface Client extends Omit<Client$1, 'operations'> {
+    services: Service[];
+}
+
 /**
  * Generate the OpenAPI client. This method will read the OpenAPI specification and based on the
  * given language it will generate the client, including the typed models, validation schemas,
  * service layer, etc.
  * @param userConfig {@link UserConfig} passed to the `createClient()` method
  */
-declare function createClient(userConfig: UserConfig): Promise<ReadonlyArray<Client$1>>;
+declare function createClient(userConfig: UserConfig): Promise<ReadonlyArray<Client>>;
 /**
  * Type helper for openapi-ts.config.ts, returns {@link UserConfig} object
  */
@@ -2753,4 +3299,4 @@ declare const _default: {
     defineConfig: (config: UserConfig) => UserConfig;
 };
 
-export { type OpenApiV3_0_3, type OpenApiV3_1, type UserConfig, createClient, _default as default, defineConfig };
+export { type OpenApiV3_0_3, type OpenApiV3_1_0, type UserConfig, createClient, _default as default, defineConfig };