Drew Powers
Drew Powers
As you know, openapi-typescript’s latest version (v6+) only supports OpenAPI 3.0 and 3.1. v5 doesn’t have any known security vulnerabilities, and it will still receive security updates if any are...
Good call—definitely worth adding to the docs short-term. I don’t want to do anything automated, because `swagger2openapi` doesn’t work for every schema. But giving people a hint that they can...
Going to close this issue as Swagger v2 support isn’t in the maintenance budget for this project, especially since OpenAPI 4.0 is on the horizon (which this library will support)...
This behavior was a decision made to improve type safety because most users don’t have [noUncheckedIndexAccess](https://www.typescriptlang.org/tsconfig#noUncheckedIndexedAccess) enabled, and this library can’t check that’s set. But when dealing with `additionalProperties`, their...
> My issue is that I'm actually only using the resulting object as an iterator, so of course noUncheckedIndexAccess is irrelevant because I'm not trying to access by index ever....
I don’t think we’d ever add a flag that disallows some part of your schema; IMO that gets into [linting](https://redocly.com/docs/cli/commands/lint/) and [the Redocly CLI](https://redocly.com/docs/cli/commands/lint/) is so good I’d probably just...
@RWOverdijk ah, I see. Yes this original issue was over `| undefined` being appended to `additionalProperties`. Optional properties may just be a missing `required: true` on your schema? Feel free...
The new release `v6.5.0` features the removal of `| undefined` in certain scenarios, but not all. I’m going to be revisiting the existing ones this week.
Is anyone able to provide a reproduction of this issue? We have [tests](https://github.com/openapi-ts/openapi-typescript/blob/ff93eac96d424f6f901535b1f3645187d56beb59/packages/openapi-typescript/test/transform/schema-object/object.test.ts#L341) for [both](https://github.com/openapi-ts/openapi-typescript/blob/ff93eac96d424f6f901535b1f3645187d56beb59/packages/openapi-typescript/test/transform/schema-object/object.test.ts#L134) that test they’re working that are both passing.
@borzaka That’s a good find! Maybe this would be a good addition to `examples/next` (since the React Query example is currently only client-side)? Or even a new `examples/next-react-query` would be...