-
-
Notifications
You must be signed in to change notification settings - Fork 135
Fails to unmarshall free-form objects (additionalProperties) #153
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
Any hint on how to overcome this? |
Hi, While working on adding OpenAPI 3 support for I managed to fix it ugly by merging casted data into unmarshaled data, but I wonder maybe there are plans on support free-form objects in I understand that type: "object"
additionalProperties: true And even more. As additionalProperties is
maybe it is needed to redesign type: "object"
properties:
one:
type: "string"
two:
type: "string"
additionalProperties: false enforce current behavior? |
After rework of unmarshalling process I believe the issue finally can be fixed. Thank you all for your contribution. |
Current version can validate free-form objects but cannot unmarshall them.
A free-form object (arbitrary property/value pairs) is defined equivalently see reference as
or
or
PR #121 address a related issue that solves validation but still unable to unmarshall. For instance, the example proposed by @berend in the same pull request cannot be unmarshalled as demonstrated in a tests I did in my fork
Any hint on how to overcome/fix this?
The text was updated successfully, but these errors were encountered: