-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question: is the spec compatible with OpenAPI? #31
Comments
Hi, do you have additional details? |
@grace-figma Do you have any good client generators for kotlin? I tried this one: And online swagger: But they both generates invalid retrofit clients: |
That was also my issue. I will try the Swagger Codegen, because the Swagger UI is the only tool that returns valid for the current specification. |
Some new info. I tried manually change schema and build minor parts. And faced with parsing errors. That means that a lot of fields checked as required, but API don't return it: |
response:
|
🤔 thanks for the additional info, I'll look into it |
I get the following issue by using version 0.22.0 with swift-openapi-generator. |
Thanks for the report here...we admittedly haven't done a huge amount of testing this OpenAPI spec outside of TypeScript. For what it's worth, the spec seems to validate properly in a 3.1 validator, and the openapi-typescript generates what we think is a pretty high-fidelity schema (example). The schema does make heavy use of polymorphic types (e.g. I think @nfirex's example about re: a missing At any rate, we'll be looking into this, but in the mean time, we'd appreciate any advice from the community for tweaking the structure of the schema so it supports a wider range of tools. |
I figured out that the current openapi.yaml file hasn't a valid Open API spec. Is this correct? This will be hard to use some code generation tools to build a network layer based on your specs.
The text was updated successfully, but these errors were encountered: