Uh oh!
There was an error while loading. Please reload this page.
Add support to exactOptional properties - #138
Closed
danroc wants to merge 1 commit into
Closed
Conversation
danrocforce-pushed
the
feature/exact-optional
branch
5 times, most recently
from
September 5, 2023 14:37
471d715 to
c3eeecdComparedanrocforce-pushed
the
feature/exact-optional
branch
from
September 5, 2023 14:54
c3eeecd to
61999b3Comparelegobeat
commented
Sep 6, 2023
Contributor
Resolves #139 |
danroc
commented
Oct 10, 2023
ContributorAuthor
This was merged into the |
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
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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().