- Sponsor
-
Notifications
You must be signed in to change notification settings - Fork 11
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
setting additionalProperties recursive #95
Comments
I'm afraid no. At least not at this point. There was PR for that but seemed too strict. See #39 |
I looked over the PR, and the discussion here #38. |
Hi, I agree with @MrFreezeDZ and think there should be an option to enable @losisin Would you accept a PR that adds this feature? Cheers |
@MrFreezeDZ thanks for the feedback and the suggestion. Sounds reasonable to me and obviously there is interest for that. |
This will default `additionalProperties` to `false` for all objects in the schema if set to `true`. The `additionalProperties` annotation, `schemaRoot.additionalProperties` and additionalProperties set via other ways (nested in `itemProperties`, `patternProperties` or similar) will take precedence over this setting, so it's fully backwards compatible. Closes losisin#95.
This will default `additionalProperties` to `false` for all objects in the schema if set to `true`. The `additionalProperties` annotation, `schemaRoot.additionalProperties` and additionalProperties set via other ways (nested in `itemProperties`, `patternProperties` or similar) will take precedence over this setting, so it's fully backwards compatible. Closes losisin#95.
This will default `additionalProperties` to `false` for all objects in the schema if set to `true`. The `additionalProperties` annotation, `schemaRoot.additionalProperties` and additionalProperties set via other ways (nested in `itemProperties`, `patternProperties` or similar) will take precedence over this setting, so it's fully backwards compatible. Closes losisin#95.
When running the schema-executable, the additionalProperties: false is not set for all properties. The only way I saw to set this is by the parameter
-schemaRoot.additionalProperties false
. This sets it only on the root properties. Is there any way to be able to let the schema-executable set additionalProperties: false for all nested properties without setting an annotation on each property?The text was updated successfully, but these errors were encountered: