@hey-api/openapi-ts 0.84.1 → 0.84.2

package/dist/internal.d.cts

@@ -1,4 +1,4 @@
-import { l as Config, L as Logger, c as IR, U as UserConfig, W as WatchValues } from './types.d-DOXd97cA.cjs';
+import { l as Config, L as Logger, c as IR, U as UserConfig, W as WatchValues } from './types.d-fB2fiwrL.cjs';
 import { JSONSchema } from '@hey-api/json-schema-ref-parser';
 import 'semver';
 import '@hey-api/codegen-core';

package/dist/internal.d.ts

@@ -1,4 +1,4 @@
-import { l as Config, L as Logger, c as IR, U as UserConfig, W as WatchValues } from './types.d-DOXd97cA.js';
+import { l as Config, L as Logger, c as IR, U as UserConfig, W as WatchValues } from './types.d-fB2fiwrL.js';
 import { JSONSchema } from '@hey-api/json-schema-ref-parser';
 import 'semver';
 import '@hey-api/codegen-core';

package/dist/internal.js

@@ -1,2 +1,2 @@
-import {createRequire}from'module';export{L as getSpec,K as initConfigs,D as parseOpenApiSpec}from'./chunk-TA6X5D7W.js';createRequire(import.meta.url);//# sourceMappingURL=internal.js.map
+import {createRequire}from'module';export{L as getSpec,K as initConfigs,D as parseOpenApiSpec}from'./chunk-WF7D2BDN.js';createRequire(import.meta.url);//# sourceMappingURL=internal.js.map
 //# sourceMappingURL=internal.js.map

package/dist/{types.d-DOXd97cA.d.cts → types.d-fB2fiwrL.d.cts}

@@ -5990,7 +5990,7 @@ declare namespace OpenApiSchemaObject {
 
 type EnumsMode = 'inline' | 'root';
 
-type Parser = {
+type UserParser = {
   /**
    * Filters can be used to select a subset of your input before it's passed
    * to plugins.
@@ -6072,6 +6072,19 @@ type Parser = {
            */
           name?: StringName;
         };
+    /**
+     * By default, any object schema with a missing `required` keyword is
+     * interpreted as "no properties are required." This is the correct
+     * behavior according to the OpenAPI standard. However, some specifications
+     * interpret a missing `required` keyword as "all properties should be
+     * required."
+     *
+     * This option allows you to change the default behavior so that
+     * properties are required by default unless explicitly marked as optional.
+     *
+     * @default false
+     */
+    propertiesRequiredByDefault?: boolean;
     /**
      * Your schemas might contain read-only or write-only fields. Using such
      * schemas directly could mean asking the user to provide a read-only
@@ -6159,7 +6172,7 @@ type Parser = {
   validate_EXPERIMENTAL?: boolean | 'strict' | 'warn';
 };
 
-type ResolvedParser = {
+type Parser = {
   /**
    * Filters can be used to select a subset of your input before it's passed
    * to plugins.
@@ -6236,6 +6249,19 @@ type ResolvedParser = {
        */
       name: StringName;
     };
+    /**
+     * By default, any object schema with a missing `required` keyword is
+     * interpreted as "no properties are required." This is the correct
+     * behavior according to the OpenAPI standard. However, some specifications
+     * interpret a missing `required` keyword as "all properties should be
+     * required."
+     *
+     * This option allows you to change the default behavior so that
+     * properties are required by default unless explicitly marked as optional.
+     *
+     * @default false
+     */
+    propertiesRequiredByDefault: boolean;
     /**
      * Your schemas might contain read-only or write-only fields. Using such
      * schemas directly could mean asking the user to provide a read-only
@@ -6618,7 +6644,7 @@ interface UserConfig$p {
    * Customize how the input is parsed and transformed before it's passed to
    * plugins.
    */
-  parser?: Parser;
+  parser?: UserParser;
   /**
    * Plugins generate artifacts from `input`. By default, we generate SDK
    * functions and TypeScript interfaces. If you manually define `plugins`,
@@ -6710,7 +6736,7 @@ type Config$c = Omit<
      * Customize how the input is parsed and transformed before it's passed to
      * plugins.
      */
-    parser: ResolvedParser;
+    parser: Parser;
     pluginOrder: ReadonlyArray<keyof PluginConfigMap>;
     plugins: {
       [K in PluginNames]?: Plugin.ConfigWithName<PluginConfigMap[K]>;

package/dist/{types.d-DOXd97cA.d.ts → types.d-fB2fiwrL.d.ts}

@@ -5990,7 +5990,7 @@ declare namespace OpenApiSchemaObject {
 
 type EnumsMode = 'inline' | 'root';
 
-type Parser = {
+type UserParser = {
   /**
    * Filters can be used to select a subset of your input before it's passed
    * to plugins.
@@ -6072,6 +6072,19 @@ type Parser = {
            */
           name?: StringName;
         };
+    /**
+     * By default, any object schema with a missing `required` keyword is
+     * interpreted as "no properties are required." This is the correct
+     * behavior according to the OpenAPI standard. However, some specifications
+     * interpret a missing `required` keyword as "all properties should be
+     * required."
+     *
+     * This option allows you to change the default behavior so that
+     * properties are required by default unless explicitly marked as optional.
+     *
+     * @default false
+     */
+    propertiesRequiredByDefault?: boolean;
     /**
      * Your schemas might contain read-only or write-only fields. Using such
      * schemas directly could mean asking the user to provide a read-only
@@ -6159,7 +6172,7 @@ type Parser = {
   validate_EXPERIMENTAL?: boolean | 'strict' | 'warn';
 };
 
-type ResolvedParser = {
+type Parser = {
   /**
    * Filters can be used to select a subset of your input before it's passed
    * to plugins.
@@ -6236,6 +6249,19 @@ type ResolvedParser = {
        */
       name: StringName;
     };
+    /**
+     * By default, any object schema with a missing `required` keyword is
+     * interpreted as "no properties are required." This is the correct
+     * behavior according to the OpenAPI standard. However, some specifications
+     * interpret a missing `required` keyword as "all properties should be
+     * required."
+     *
+     * This option allows you to change the default behavior so that
+     * properties are required by default unless explicitly marked as optional.
+     *
+     * @default false
+     */
+    propertiesRequiredByDefault: boolean;
     /**
      * Your schemas might contain read-only or write-only fields. Using such
      * schemas directly could mean asking the user to provide a read-only
@@ -6618,7 +6644,7 @@ interface UserConfig$p {
    * Customize how the input is parsed and transformed before it's passed to
    * plugins.
    */
-  parser?: Parser;
+  parser?: UserParser;
   /**
    * Plugins generate artifacts from `input`. By default, we generate SDK
    * functions and TypeScript interfaces. If you manually define `plugins`,
@@ -6710,7 +6736,7 @@ type Config$c = Omit<
      * Customize how the input is parsed and transformed before it's passed to
      * plugins.
      */
-    parser: ResolvedParser;
+    parser: Parser;
     pluginOrder: ReadonlyArray<keyof PluginConfigMap>;
     plugins: {
       [K in PluginNames]?: Plugin.ConfigWithName<PluginConfigMap[K]>;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hey-api/openapi-ts",
-  "version": "0.84.1",
+  "version": "0.84.2",
   "description": "🚀 The OpenAPI to TypeScript codegen. Generate clients, SDKs, validators, and more.",
   "homepage": "https://heyapi.dev/",
   "repository": {