-
Notifications
You must be signed in to change notification settings - Fork 5
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
Additional properties don't support Json Array type #22
Comments
For Model : components/schemas/Device List of missing params:
For Model : components/schemas/Plan (which is used in model Device)
For Model : components/schemas/Event (which is used in model Device)
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently OAS 3.0 spec is not in sync with server response structure and might be providing more params than mentioned in spec. To fix this issue we allowed additional properties to be created if not present as mentioned in issue #16 and committed fix in PR #18.
But when additional params are provided in form of Array rather Object or primitive type deserialisation of structure faces following exception:
Solution: At bare minimum we need to get Equinix OAS 3.0 closer to server response at least for array type params and in long run make sure that all the params returned by Equinix env are present in spec then we can change generated code behaviour to be strict on additional properties.
This issue will also track, list of models in Equinix OAS 3.0 which are incomplete relative to their server response as we find them.
The text was updated successfully, but these errors were encountered: