-
-
Notifications
You must be signed in to change notification settings - Fork 890
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
Issues with additonal properties evaluation #140
Comments
This schema:
does not have You either need to move properties from Also, strictly speaking, the standard says that |
Thanks for the clarification. Since the definition is used in multiple places, Will talk to the team that owns the schema and move the additionalProperties: false and also the "required" section to the #/definition/interface section. I tested by moving and it works as expected. |
Thank you |
Also found out that even if you use allOf to apply both $ref and some other schema, additonalProperties: false doesn't work as expected as the JSON schema doesn't support inheritance. So the only way is to replicate the whole properties. |
Thanks. It helps. |
In the following code, in the interface section is referenced in the device section. Additional property is set to false and required is mode. But the validation fails even if we give the right properties of interface.
If the required mode or the right enumeration for mode is not given, it throws the right error.
Seems additional properties is not evaluated properly. Can you check.
Here is the error:
Invalid: data.configs.vid.desc.device.mgt0 should NOT have additional properties, data.configs.vid.desc.device.mgt0 should NOT have additional properties, data.configs.vid.desc.device.mgt0 should NOT have additional properties, data.configs.vid.desc.device.mgt0 should NOT have additional properties
The text was updated successfully, but these errors were encountered: