We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
There are a few valid ways to define additionalProperties.
additionalProperties
To define a dictionary, use type: object and use the additionalProperties keyword to specify the type of values in key/value pairs.
type: object
Instead of using an inline schema, additionalProperties can $ref another schema
If the dictionary values can be of any type (aka free-form object), use additionalProperties: true
https://swagger.io/docs/specification/data-models/dictionaries/
But might be best for the implementation to follow the OpenAPI/Swagger spec, and only allow for valid dictionary types.
Could maybe also handle some of these other invalid cases.
Originally posted by @scottc in #63 (comment)
The text was updated successfully, but these errors were encountered:
@scottc FYI
Sorry, something went wrong.
No branches or pull requests
There are a few valid ways to define
additionalProperties
.https://swagger.io/docs/specification/data-models/dictionaries/
But might be best for the implementation to follow the OpenAPI/Swagger spec, and only allow for valid dictionary types.
Could maybe also handle some of these other invalid cases.
Originally posted by @scottc in #63 (comment)
The text was updated successfully, but these errors were encountered: