Fix #706 - support exactOptionalPropertyTypes
option
#707
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.
When configured
exactOptionalPropertyTypes
property to betrue
intsconfig.json
file, predication logic of undefindable type from optional symbol (?
) becomes different. By the way, I haven't known that and it was the reasontypia
could not detect undefindable type when the optional symbol?
being used like below:From now on (
v4.1.4
),typia
can distinguish it.