-
-
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
feat: introduce flag noAdditionalProperties #97
feat: introduce flag noAdditionalProperties #97
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #97 +/- ##
==========================================
+ Coverage 99.06% 99.08% +0.02%
==========================================
Files 6 6
Lines 639 653 +14
==========================================
+ Hits 633 647 +14
Misses 4 4
Partials 2 2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
9cfee26
to
5239364
Compare
I'll add a testcase that increases the coverage of |
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.
5239364
to
b7c3e74
Compare
Coverage should be fine now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
awesome
This will default
additionalProperties
tofalse
for all objects in the schema if set totrue
. TheadditionalProperties
annotation,schemaRoot.additionalProperties
and additionalProperties set via other ways (nested initemProperties
,patternProperties
or similar) will take precedence over this setting, so it's fully backwards compatible.Closes #95.