You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In this type: https://github.com/kubb-labs/kubb/blob/main/packages/plugin-oas/src/types.ts#L108 it is encoded that there is only one success response schema. However, this is not true, multiple successful status codes can be defined on a swagger file, and thus multiple different response schemas. The first 2xx schema is grabbed here:
What is the feature you are proposing to solve the problem?
Spit out all the status codes and their responses here!
What alternatives have you considered?
Lucky for us, I think I can get around this with some type wizardry (we don't currently depend on this, but it will be tricky to work around). We certainly will need this later, though!
The text was updated successfully, but these errors were encountered:
What is the problem this feature would solve?
In this type: https://github.com/kubb-labs/kubb/blob/main/packages/plugin-oas/src/types.ts#L108 it is encoded that there is only one success response schema. However, this is not true, multiple successful status codes can be defined on a swagger file, and thus multiple different response schemas. The first 2xx schema is grabbed here:
kubb/packages/plugin-oas/src/OperationGenerator.ts
Line 142 in ae4e0e0
This manifests when we try to generate the zod schemas. The swagger file we have has multiple 2xx response codes, something like:
However, the equivalent operation mapping only includes the 201 (the many error codes are included correctly):
External documents/projects?
No response
What is the feature you are proposing to solve the problem?
Spit out all the status codes and their responses here!
What alternatives have you considered?
Lucky for us, I think I can get around this with some type wizardry (we don't currently depend on this, but it will be tricky to work around). We certainly will need this later, though!
The text was updated successfully, but these errors were encountered: