-
Notifications
You must be signed in to change notification settings - Fork 257
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
[Bug] Can't generate swagger with var references #669
Comments
This is interesting! I started testing and thought reitit + malli vars is completely broken, but it seems to actually mostly works. I'll try to narrow down what exactly goes wrong in the example. |
Ok, so the example ring-malli-swagger is broken in
|
opqdonut
added a commit
that referenced
this issue
Apr 19, 2024
If we don't remove them, :responses :content gets passed out verbatim in the swagger.json, breaking stuff. In particular, fixes the swagger.json in examples/reitit-malli-swagger. Reported broken in #669.
opqdonut
added a commit
that referenced
this issue
Apr 19, 2024
If we don't remove them, :responses :content gets passed out verbatim in the swagger.json, breaking stuff. In particular, fixes the swagger.json in examples/reitit-malli-swagger. Reported broken in #669.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I encountered two different problems when schemas use var refs - no schema for GET and bad resolution for POST
Steps to reproduce:
Go to
examples/ring-malli-swagger
Explicitly bump reitit to 15:
[metosin/malli "0.15.0"]
Add
Change parameters in get and post to use schema reference:
:parameters {:query #'Plus}
Start server and navigate to openapi page
Get error:
Observe the generated openapi.json
"#/definitions/example.server~1Plus"
See schema opbject:
The text was updated successfully, but these errors were encountered: