fix: Validation correctly even when the optional and nullish keys are not specified
#54
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
chimame
changed the title
optional and nullish keys are not specified
chimame
force-pushed
the
fix-correctly-even-when-optional-and-nullish-keys-are-not-specified
branch
from
c973f7b to
445b182
Compare
… are not specified
chimame
force-pushed
the
fix-correctly-even-when-optional-and-nullish-keys-are-not-specified
branch
from
445b182 to
ed159a7
Compare
chimame
deleted the
fix-correctly-even-when-optional-and-nullish-keys-are-not-specified
branch
|
🎉 This PR is included in version 1.14.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Close #53
One concern with this PR is that since
nullishandoptionalare imported, the bundle size is likely to increase slightly.