-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
fix: correct handling of additionalProperties in object schemas #6939
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
Conversation
Co-authored-by: Adam Jones <domdomegg+git@gmail.com>
Thanks for the PR, @bradzacher! typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community. The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately. Thanks again! 🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint. |
✅ Deploy Preview for typescript-eslint ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## v6 #6939 +/- ##
==========================================
- Coverage 87.51% 87.50% -0.01%
==========================================
Files 376 376
Lines 12944 12936 -8
Branches 3821 3820 -1
==========================================
- Hits 11328 11320 -8
Misses 1231 1231
Partials 385 385
Flags with carried forward coverage won't be shown. Click here to find out more.
|
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.
good catch 👍
PR Checklist
Overview
@domdomegg's #6894 made me realise I'd incorrectly handled this case in the schema gen.
When it's missing/
undefined
it's the same as beingtrue
- but I treated it asfalse