orval-labs/orval

Description The Orval Playground only supports YAML schemas. It would be nice if JSON support was added since a lot of API frameworks like FastAPI generate a /openapi.json route by default. It would be nice to be able to take that JSON and dump it in the playground unmodified, to prove it can handle your schema. Current behavior The schema only supports YAML. Proposed behavior The schema should also support JSON. Proposed solution We could either After the "Choose an Example" select we could add another select to choose the schema language. Keep a single select but duplicate each example, one for YAML and one for JSON. Each would have a different input target in the orval.config.js panel.

Description When runtimeValidation: true is enabled, primitive response schemas such as number and integer do not generate corresponding Zod schemas or runtime validation. Additionally, the generated Zod output types for error responses are not imported or used by the generated client. Output client zod Configuration (orval.config) export default defineConfig({ example: { input: `../docs/source/openapi/example_openapi.yml`, output: { target: `${outputDir}/example/client.ts`, packageJson: "package.json5", mode: "single", client: "react-query", httpClient: "fetch", formatter: "oxfmt", clean: true, schemas: { path: `${outputDir}/example/schemas`, type: "zod", mode: "single", }, override: { fetch: { runtimeValidation: true, } }, },

Description The Response model filenames contains a suffix ("Response" by default), but that suffix is not applied in the imports of the generated queries. Output client angular-query Configuration (orval.config) import { defineConfig } from 'orval'; export default defineConfig({ myProject: { input: { target: './contract.yaml' }, output: { mode: 'tags-split', target: './src/app/core/generated/queries', schemas: './src/app/core/generated/model', client: 'angular-query', httpClient: 'angular', mock: false, clean: true, baseUrl: 'http://localhost:8080/', indexFiles: false, tagsSplitDeduplication: true, commonTypesFileName: 'shared' }, }, }); Environment System: OS: macOS 26.6.2 CPU: (18) arm64 Apple M5 Max Memory: 53.51 GB / 128.00 GB Shell: 5.9 - /bin/zsh npmPackages: @angular/common: 21.2.20 => 21.2.20 @angular/core: 21.2.20 => 21.2.20 @tanstack/angular-query-experimental: 5.102.8 => 5.102.8 Exp

Description I noticed there is effect schema support, I tried it out but realized it uses v3 functions. I would just like to request a v4 version even though it is still not fully a released version. Current behavior uses older v3 functions Proposed behavior update or add a v4 version Proposed solution update or add a v4 version

Description I think we should improve performance. Config like this: import { defineConfig } from 'orval'; import { execSync } from 'child_process'; const header = ({ title, description, version }) => [ 'Generated by orval 🍺', 'Do not edit manually.', ...(title ? [title] : []), ...(description ? [description] : []), ...(version ? [`OpenAPI spec version: ${version}`] : []), ]; export default defineConfig({ main: { input: 'https://.../schema/openapi.json', output: { schemas: 'projects/api/src/lib/main/schemas', target: 'projects/api/src/lib/main/target', client: 'angular-query', httpClient: 'angular', mode: 'tags', clean: true, override: { header, useTypeOverInterfaces: false, }, }, hooks: { afterAllFilesWrite: (paths) => { console.log('Running lint fix and patching generated files...'); execSync(`bun scripts/fix-orval-params.ts ${paths.join(' ')}`); execSync(`bu