Add support to exactOptional properties
#138
Closed
Conversation
This file contains hidden or 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
danroc
force-pushed
the
feature/exact-optional
branch
5 times, most recently
from
471d715 to
c3eeecd
Compare
danroc
force-pushed
the
feature/exact-optional
branch
from
c3eeecd to
61999b3
Compare
Contributor
|
Resolves #139 |
Contributor
Author
|
This was merged into the |
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.
Similar to #136, this was I had working for a patch I would like to submit to superstruct.
Please note that if
exactOptionalPropertyTypesif disabled,exactOptional()will behave as a no-op. For example,exactOptional(string())will be identical tostring().