-
Notifications
You must be signed in to change notification settings - Fork 27
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
Unsupported jsonSchemaDialect #588
Comments
hmm... what version of swagger UI are you using, and what dialect do they expect? |
I'm using the version Kompendium imports: Judging by the code, it looks like the default is to pull the latest version:
The dialect it expects is shown in the error message:
|
Oh yea I forgot kompendium allows this again haha... swagger support for various openapi options always seems to be changing :/ Swagger UI is still on 5.x and previous 5.x versions worked w/ Kompendium but the swagger team doesn't really follow semver in my experience Defaulting to latest is probably not the smartest move, from a compatibility perspective. Would be a very easy fix if we could publish the lib lol |
I've got to figure out all the new Sonatype stuff for a library I publish so if I manage to get that working, maybe I can help you out with getting the publishing updated for Kompendium. |
Oh cool that would be great! That lib looks neat, I took a take a while back on a different aspect of the spring ecosystem, which was to start with a domain definition and try to code gen basically the entire backend out of it. The lib is in a super half baked state but does some pretty neat stuff with kotlin symbol processors :) https://github.com/bkbnio/lerasium |
Are there any go to workarounds for this error for the time being? I can't see that it actually ruins anything, but its always a nice comfort having no errors on your swagger UI :) |
As mentioned in the OP just set the jsonSchemaDialect property to the value shown in the error. It hasn't caused any issues for me so far. |
Describe the bug
When using the Swagger UI, I see the following error:
Explicitly setting
jsonSchemaDialect
to the value shown works around the error, but I don't know whether that will break things.Screenshots
The text was updated successfully, but these errors were encountered: