Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix #706 - support exactOptionalPropertyTypes option #707

Merged
merged 1 commit into from
Jul 7, 2023
Merged

Conversation

samchon
Copy link
Owner

@samchon samchon commented Jul 7, 2023

When configured exactOptionalPropertyTypes property to be true in tsconfig.json file, predication logic of undefindable type from optional symbol (?) becomes different. By the way, I haven't known that and it was the reason typia could not detect undefindable type when the optional symbol ? being used like below:

interface IMember {
    id: string;
    age?: number; // considered as required when `exactOptionalPropertyTypes` being used
}

From now on (v4.1.4), typia can distinguish it.

@samchon samchon added bug Something isn't working enhancement New feature or request labels Jul 7, 2023
@samchon samchon self-assigned this Jul 7, 2023
@samchon
Copy link
Owner Author

samchon commented Jul 7, 2023

Fix #702 too.

@samchon samchon merged commit 800c5fc into master Jul 7, 2023
@samchon samchon deleted the issues/706 branch July 15, 2023 16:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant