@hey-api/openapi-ts 0.71.1 → 0.72.1

package/dist/internal.d.cts

@@ -1,6 +1,6 @@
 import { JSONSchema } from '@hey-api/json-schema-ref-parser';
-import { e as Config, I as IR, W as WatchValues } from './types.d-1-e85tL8.cjs';
-export { i as initConfigs } from './types.d-1-e85tL8.cjs';
+import { e as Config, I as IR, W as WatchValues } from './types.d-DMy4lDbN.cjs';
+export { i as initConfigs } from './types.d-DMy4lDbN.cjs';
 import 'node:fs';
 import 'typescript';
 

package/dist/internal.d.ts

@@ -1,6 +1,6 @@
 import { JSONSchema } from '@hey-api/json-schema-ref-parser';
-import { e as Config, I as IR, W as WatchValues } from './types.d-1-e85tL8.js';
-export { i as initConfigs } from './types.d-1-e85tL8.js';
+import { e as Config, I as IR, W as WatchValues } from './types.d-DMy4lDbN.js';
+export { i as initConfigs } from './types.d-DMy4lDbN.js';
 import 'node:fs';
 import 'typescript';
 

package/dist/internal.js

@@ -1,2 +1,2 @@
-import {createRequire}from'module';export{p as getSpec,z as initConfigs,u as parseOpenApiSpec}from'./chunk-EZKCBI4J.js';createRequire(import.meta.url);//# sourceMappingURL=internal.js.map
+import {createRequire}from'module';export{r as getSpec,F as initConfigs,A as parseOpenApiSpec}from'./chunk-LGCLNROS.js';createRequire(import.meta.url);//# sourceMappingURL=internal.js.map
 //# sourceMappingURL=internal.js.map

package/dist/{types.d-1-e85tL8.d.cts → types.d-DMy4lDbN.d.cts}

@@ -6783,6 +6783,14 @@ interface Config$b extends Plugin.Name<'@hey-api/sdk'> {
    * This option has no effect if `sdk.asClass` is `false`.
    */
   classNameBuilder?: string | ((name: string) => string);
+  /**
+   * How should we structure your SDK? By default, we try to infer the ideal
+   * structure using `operationId` keywords. If you prefer a flatter structure,
+   * you can set `classStructure` to `off` to disable this behavior.
+   *
+   * @default 'auto'
+   */
+  classStructure?: 'auto' | 'off';
   /**
    * Use an internal client instance to send HTTP requests? This is useful if
    * you don't want to manually pass the client to each SDK function.
@@ -6817,7 +6825,8 @@ interface Config$b extends Plugin.Name<'@hey-api/sdk'> {
    */
   instance?: string | boolean;
   /**
-   * Customise the name of methods within the service. By default, {@link IR.OperationObject.id} or {@link Operation.name} is used.
+   * Customise the name of methods within the service. By default,
+   * {@link IR.OperationObject.id} or {@link Operation.name} is used.
    */
   methodNameBuilder?: (operation: IR.OperationObject | Operation) => string;
   // TODO: parser - rename operationId option to something like inferId?: boolean
@@ -8070,7 +8079,7 @@ declare class IRContext<Spec extends Record<string, any> = any> {
     /**
      * Register a new `event` listener.
      */
-    subscribe<T extends keyof Events>(event: T, callbackFn: Events[T]): void;
+    subscribe<T extends keyof Events>(event: T, callbackFn: Events[T], pluginName?: string): void;
 }
 
 type IRMediaType = 'form-data' | 'json' | 'text' | 'url-search-params' | 'octet-stream';
@@ -8099,6 +8108,7 @@ interface IROperationObject {
   description?: string;
   id: string;
   method: keyof IRPathItemObject;
+  operationId?: string;
   parameters?: IRParametersObject;
   path: keyof IRPathsObject;
   responses?: IRResponsesObject;
@@ -8245,6 +8255,13 @@ interface IRSchemaObject
    * When type is `object`, `properties` will contain a map of its properties.
    */
   properties?: Record<string, IRSchemaObject>;
+  /**
+   * 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.
+   */
+  propertyNames?: IRSchemaObject;
   /**
    * Each schema eventually resolves into `type`.
    */

package/dist/{types.d-1-e85tL8.d.ts → types.d-DMy4lDbN.d.ts}

@@ -6783,6 +6783,14 @@ interface Config$b extends Plugin.Name<'@hey-api/sdk'> {
    * This option has no effect if `sdk.asClass` is `false`.
    */
   classNameBuilder?: string | ((name: string) => string);
+  /**
+   * How should we structure your SDK? By default, we try to infer the ideal
+   * structure using `operationId` keywords. If you prefer a flatter structure,
+   * you can set `classStructure` to `off` to disable this behavior.
+   *
+   * @default 'auto'
+   */
+  classStructure?: 'auto' | 'off';
   /**
    * Use an internal client instance to send HTTP requests? This is useful if
    * you don't want to manually pass the client to each SDK function.
@@ -6817,7 +6825,8 @@ interface Config$b extends Plugin.Name<'@hey-api/sdk'> {
    */
   instance?: string | boolean;
   /**
-   * Customise the name of methods within the service. By default, {@link IR.OperationObject.id} or {@link Operation.name} is used.
+   * Customise the name of methods within the service. By default,
+   * {@link IR.OperationObject.id} or {@link Operation.name} is used.
    */
   methodNameBuilder?: (operation: IR.OperationObject | Operation) => string;
   // TODO: parser - rename operationId option to something like inferId?: boolean
@@ -8070,7 +8079,7 @@ declare class IRContext<Spec extends Record<string, any> = any> {
     /**
      * Register a new `event` listener.
      */
-    subscribe<T extends keyof Events>(event: T, callbackFn: Events[T]): void;
+    subscribe<T extends keyof Events>(event: T, callbackFn: Events[T], pluginName?: string): void;
 }
 
 type IRMediaType = 'form-data' | 'json' | 'text' | 'url-search-params' | 'octet-stream';
@@ -8099,6 +8108,7 @@ interface IROperationObject {
   description?: string;
   id: string;
   method: keyof IRPathItemObject;
+  operationId?: string;
   parameters?: IRParametersObject;
   path: keyof IRPathsObject;
   responses?: IRResponsesObject;
@@ -8245,6 +8255,13 @@ interface IRSchemaObject
    * When type is `object`, `properties` will contain a map of its properties.
    */
   properties?: Record<string, IRSchemaObject>;
+  /**
+   * 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.
+   */
+  propertyNames?: IRSchemaObject;
   /**
    * Each schema eventually resolves into `type`.
    */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hey-api/openapi-ts",
-  "version": "0.71.1",
+  "version": "0.72.1",
   "description": "🚀 The OpenAPI to TypeScript codegen. Generate clients, SDKs, validators, and more.",
   "homepage": "https://heyapi.dev/",
   "repository": {
@@ -81,7 +81,8 @@
     "c12": "2.0.1",
     "color-support": "1.1.3",
     "commander": "13.0.0",
-    "handlebars": "4.7.8"
+    "handlebars": "4.7.8",
+    "open": "10.1.2"
   },
   "peerDependencies": {
     "typescript": "^5.5.3"
@@ -101,7 +102,7 @@
     "typescript": "5.8.3",
     "yaml": "2.8.0",
     "@config/vite-base": "0.0.1",
-    "@hey-api/client-core": "0.1.4"
+    "@hey-api/client-core": "0.2.0"
   },
   "scripts": {
     "build": "tsup && pnpm check-exports",