-
Notifications
You must be signed in to change notification settings - Fork 50
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
Invalid OpenAPI spec being generated #178
Comments
Upon further investigation, it seems that the That and the |
Found several issues I had to monkeypatch in order for the generated OpenAPI JSON spec to be valid.
It seems that the generator has some issues generating 100% compliant docs. After all this was done, I could use If you're struggling with this, use the https://editor.swagger.io/ to load your JSON file and see what errors you're getting. The errors you get is what you have to remove/tweak. |
One last thing, the resulting |
Hi, it seems that the resulting OpenAPI spec being generated when using references as suggested here, generates an invalid OpenAPI spec definition.
This is my model:
I then add it to the app as a
.model
This is the resulting OpenAPI spec.
The relevant
Link
part is the following:Perhaps is because we added a manual
$id
that is leaking into the final OpenAPI spec?Is there an official way of referencing OpenAPI models in different schemas?
Thank you!
The text was updated successfully, but these errors were encountered: