-
Notifications
You must be signed in to change notification settings - Fork 2.2k
additionalProperties does not have to be "either a Boolean or a Schema instance" #3850
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
Comments
The enforced behaviour/structure does not seem contradictory to me:
is implemented/deserialized in |
Thanks, @frantuma . Perhaps you are right but when I try to load a valid openapi.json.txt into a We are reading the json into OpenAPI in order to test and validate the auto generated openapi.json. Running with a debugger, we can see that the
|
I am not sure how you are deserializing and in which scenario, but from your logs it looks like you're using some possibly not configured
Please close ticket if this answers your question |
@frantuma Perfect. Thank you. I was using a default ObjectMapper. Using |
good |
Works |
nice |
working |
Currently, the code enforces that "additionalProperties must be either a Boolean or a Schema instance".
According to https://swagger.io/docs/specification/data-models/dictionaries/ and OAI/OpenAPI-Specification#668 (comment), the following structure is also valid:
This is the openapi that represents (and is generated) when the model is a Map of string and string (
Map<String, String>
).The text was updated successfully, but these errors were encountered: