-
Notifications
You must be signed in to change notification settings - Fork 846
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
fix(instrumentation): Fix optional property types #4833
Conversation
@pichlermarc @dyladan Friendly ping 😉 |
@pichlermarc @dyladan @legendecas @blumamir Friendly ping! |
Would you mind updating the PR title and commit message according to the guide https://github.com/open-telemetry/opentelemetry-js/blob/main/CONTRIBUTING.md#conventional-commit ? thank you! |
TypeScript emits InstrumentationNodeModuleDefinition with " | undefined" for some reason, making it incompatible with InstrumentationModuleDefinition under exactOptionalPropertyTypes.
@legendecas Sure thing, done 😉 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
Thanks! 👍 |
Which problem is this PR solving?
Fix #4712, related to #3713.
TypeScript emits
InstrumentationNodeModuleDefinition
with| undefined
for some reason, making it incompatible withInstrumentationModuleDefinition
underexactOptionalPropertyTypes: true
.Type of change
Please delete options that are not relevant.
How Has This Been Tested?
I'm using OpenTelemetry indirectly via Sentry. I applied this patch locally to the latest version of
@opentelemetry/instrumentation
and it resolved the issue.Checklist: