Fix samchon/nestia#628 - exactOptionalPropertyTypes's with Partial<T> and Required<T> types.
#829
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
…tial<T>` and `Required<T>` types. If user configured `tsconfig.json` to turn on `exactOptionalPropertyTypes` option, and use `Partial<T>` or `Required<T>` type, `typia` could not identify whether each property is optional or not. This PR fixes such bug, by enhancing analyzer of TypeScript types. Also, turned on the `exactOptionalPropertyTypes` option tor enhancing type safety for this case.
samchon
added a commit
to samchon/nestia
that referenced
this pull request
Sep 29, 2023
…rtial` type. Related with `typia`'s PR: - samchon/typia#829
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.
If user configured
tsconfig.jsonto turn onexactOptionalPropertyTypesoption, and usePartial<T>orRequired<T>type,typiacould not identify whether each property is optional or not.This PR fixes such bug, by enhancing analyzer of TypeScript types. Also, turned on the
exactOptionalPropertyTypesoption tor enhancing type safety for this case.