-
Notifications
You must be signed in to change notification settings - Fork 821
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
Set the exactOptionalPropertyTypes tsconfig option #3713
Comments
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days. |
please consider this change |
Seeing this same issue in my projects |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days. |
Bumping to keep this alive. This is still desired |
We talked about this in the SIG meeting and we are generally in favor of this, assuming it doesn't cause issues. I'm going to mark this as up for grabs and PRs will be welcome. |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days. |
Since typescript 4.4 this new tsconfig option has been available, to clarify the difference between
{ foo: string | undefined }
and{ foo?: string }
. This would be a beneficial option for me to enable in my project, but I cannot as the opentelemetry typings don't typecheck correctly with option.Affected files that I'm seeing:
Link to documentation: https://www.typescriptlang.org/tsconfig#exactOptionalPropertyTypes
The text was updated successfully, but these errors were encountered: