@povio/openapi-codegen-cli 3.0.0-rc.9 → 3.0.1-rc.1

package/README.md

@@ -215,6 +215,16 @@ import { ErrorHandler, OpenApiQueryConfig } from "@povio/openapi-codegen-cli";
 </OpenApiQueryConfig.Provider>;
 ```
 
+### Runtime response validation
+
+Use `OpenApiQueryConfig.Provider` to allow generated GET query hooks to return invalid response data while still logging the response Zod error to the console. Non-GET requests still throw on invalid response data.
+
+```tsx
+<OpenApiQueryConfig.Provider allowInvalidResponseData={import.meta.env.DEV}>
+  <App />
+</OpenApiQueryConfig.Provider>
+```
+
 ### OpenApiWorkspaceContext (Path + ACL defaults)
 
 Set `workspaceContext` to a list of param names in codegen config (or pass `--workspaceContext officeId,projectId`) and wrap your app subtree with `OpenApiWorkspaceContext.Provider` if generated hooks frequently repeat workspace-scoped params.
@@ -277,6 +287,37 @@ export default defineConfig({
 The plugin runs on both `vite serve` and `vite build`, and watches local OpenAPI files in dev mode.
 If you provide `formatGeneratedFile`, the plugin formats each generated file in memory before comparing and writing it, which helps avoid unnecessary HMR when the formatted output is unchanged.
 
+### Metro Plugin
+
+You can run codegen directly from React Native Metro config:
+
+```ts
+import { fileURLToPath } from "url";
+import { getDefaultConfig } from "@react-native/metro-config";
+import { withOpenApiCodegen } from "@povio/openapi-codegen-cli/metro";
+
+const root = fileURLToPath(new URL("./", import.meta.url));
+const config = getDefaultConfig(root);
+
+export default withOpenApiCodegen(
+  config,
+  {
+    input: "./openapi.yaml",
+    output: "./src/data",
+    inlineEndpoints: true,
+    incremental: true,
+    formatGeneratedFile: async ({ fileName, content }) => {
+      void fileName;
+      return content;
+    },
+  },
+  { root },
+);
+```
+
+The Metro wrapper runs generation when the config is loaded, waits for it before Metro transforms or serves the first request, and watches local OpenAPI files while the dev server is running.
+If you provide `formatGeneratedFile`, it behaves the same way as the Vite plugin.
+
 ### Enums
 
 If you're using Enums in your backend DTOs with `@Expose()` and `@IsEnum`, they may still not appear correctly in the OpenAPI schema unless you also provide both `enum` **and** `enumName` to `@ApiProperty`.

package/dist/acl.d.mts

@@ -1,4 +1,4 @@
-import { a as ErrorHandler } from "./error-handling-B4aYKmyL.mjs";
+import { a as ErrorHandler } from "./error-handling-oM5YJYYH.mjs";
 import * as react from "react";
 import { PropsWithChildren } from "react";
 import * as react_jsx_runtime0 from "react/jsx-runtime";

package/dist/{config-C1ME3Ay4.d.mts → config-CrZa_Jbm.d.mts}

@@ -1,4 +1,4 @@
-import { t as GenerateOptions } from "./options-BPAjzilp.mjs";
+import { t as GenerateOptions } from "./options-BZOw7Hx4.mjs";
 
 //#region src/generators/types/config.d.ts
 type OpenAPICodegenConfig = Partial<GenerateOptions>;

package/dist/{generate.runner-DSZ2ivlU.mjs → generate.runner-DnUDkoAZ.mjs}

@@ -1,4 +1,4 @@
-import { S as Profiler, h as deepMerge, i as writeGenerateFileData, p as DEFAULT_GENERATE_OPTIONS, r as removeStaleGeneratedFiles, t as generateCodeFromOpenAPIDoc } from "./generateCodeFromOpenAPIDoc-NA2XZmIv.mjs";
+import { S as Profiler, h as deepMerge, i as writeGenerateFileData, p as DEFAULT_GENERATE_OPTIONS, r as removeStaleGeneratedFiles, t as generateCodeFromOpenAPIDoc } from "./generateCodeFromOpenAPIDoc-CbQ9gQss.mjs";
 import path from "path";
 import SwaggerParser from "@apidevtools/swagger-parser";