hey-api / openapi-ts

✨ Turn your OpenAPI specification into a beautiful TypeScript client

https://heyapi.vercel.app

hey-api/openapi-ts Issues

Default content-type of application/json applied to DELETE
Updated 9 days ago1
@hey-api/client-fetch does not really `throw` where it should
Updated 9 days ago2
CancelablePromise type does not work with react suspense
Updated 10 days ago5
Support microsoft office Content-Type as binary
Updated 11 days ago1
Add option to generate `*.mts` files
Closed 11 days ago5
Handle different http status like 200 or 204
Updated 11 days ago5
Proper Angular support
Updated 12 days ago2
client-fetch: array of string in body unsupported
Closed 12 days ago
How to create my own client?
Updated 12 days ago14
Why is accept hard coded? Can it be changed to */* until a better solution is created?
Updated 13 days ago5
External reference not resolved correctly
Updated 15 days ago1
Types for the methods conflict when the same operation name is defined in multiple routes
Updated 15 days ago15
Default export of the module has or is using private name 'ClientConfig'.
Updated 16 days ago2
Got client
Updated 16 days ago19
Wasn't able to send a correctly formatted payload using application/x-www-form-urlencoded
Updated 18 days ago1
Empty JSON request body spec is created as an "unknown" type
Updated 18 days ago1
OpenAPI parameters with the same name and different "in" types cause "Duplicate identifier" error in types.gen.ts
Closed 18 days ago2
Certain Path Styles break "Type Generation"
Closed 19 days ago2
Watch Mode
Updated 20 days ago
Compiling ClientApi.ts fails due to include of unavailalble class DefaultService
Updated 20 days ago4
Tanstack query
Updated 20 days ago
Invalid code generated when response description is a number
Updated 21 days ago3
Allow services to throw an error on non-2XX response
Updated 22 days ago4
Allow custom service names when using `asClass: false`
Updated 22 days ago3
Standalone package for your client
Closed 24 days ago2
Schema with a number-only name gets generated into uncompilable code
Updated 25 days ago1
Error types no longer strongly typed
Closed a month ago4
When generated the parameter of type "object" turns into type "unknown". Type "any" would be preferred.
Closed a month ago12
Error types are `unknown` with v0.46.3
Updated a month ago1
Type of body is widened by default without any provided known properties
Closed a month ago10
Return types are not unique across services. They conflict.
Updated a month ago11
Add link to migration page into changelog
Updated a month ago
Generated angular client produces compile error due to tree shaking in services
Updated a month ago3
Null type is ignored when generating object types
Closed a month ago4
Parameters with `in: header` cause incompatible types
Closed a month ago4
Add services and types to docs
Closed a month ago
Support for exactOptionalPropertyTypes in tsconfig.json
Closed a month ago3
Unused @ts-expect-error comment
Closed a month ago17
FormData date type casted with qutoes
Updated a month ago6
Add tsconfig tests
Updated a month ago
fetch client: snake_case path arguments get converted to camelCase in types, but not in template string
Closed a month ago3
Newly exported `DefaultService` does not exist
Closed a month ago14
Non-global clients/configs
Closed a month ago6
Export `FetchClient` interface
Closed a month ago
Export services as module instead of class to enable tree shaking.
Closed a month ago10
Improve support for `Accept` and `Content-Type` headers
Updated a month ago
can't generate a node16 moduleResolution compatible package
Closed a month ago8
[question] How does this package compare to `openapi-typescript`?
Closed a month ago2
Validate response against openapi schema
Updated a month ago1
export eslint.rules for external usage
Closed a month ago3