openapi-typescript
openapi-typescript copied to clipboard
drwpow
Generate TypeScript types from OpenAPI 3 specs
**Description** The change in #1335 that makes the `parameters` property optional if all parameters are optional (thanks!) seems to not work with reusable header definitions in the `components` section. Trying...
**Description** If a payload has a required object field whose `additionalProperties` specifies a schema for the values, the generated type shouldn't allow `undefined` values. **OpenAPI** The real schema where I'm...
**Description** Error when generating schema from multiple `.yaml` files from another directory in the parent folder (see directory structure below). Thus, the yaml file is not in the same folder...
**Description** I'm seeing an issue where generated typescript types result in some impossible types: ``` Type error: Argument of type '{ params: { path: { id: string; }; }; }'...
**Description** Generated schema types with references to other types present an awkward IDE experience. ```typescript // generated "child type /** * BoardDTO * @description Deserialized board record with cover image...
**Description** Currently in order to handle errors the code usually looks something like this: ```typescript const { data, error } = get('url/which/fails/to/fetch') .catch(error => ({error, response: new Response()})) console.log(error) //=>...
type: object and additionalProperties: type: array causing is not assignable to 'string' index type
**Description** I'm seeing in our existing code we have a type object where we've defined additional properties as an array. When we run `openapi-typescript` the TypeScript produced doesn't compile. Should...
**Description** When making a query, everything's typed and working properly, but when I examine the `data` and `error` props, I get `undefined` even though the `200` value is clearly defined...
**Description** The `transform` hook introduced in 6.0 is really neat, but I feel like it would be even better if `ReferenceObject`s could be transformed as well. If this were the...
**Description** API entry points are associated to operationId in OpenAPI schema. Path Enum was a solution in `openapi-typescript@
