-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
ref(browser): Ensure fetch
transport has tracing suppressed
#16532
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
base: develop
Are you sure you want to change the base?
Conversation
size-limit report 📦
|
return suppressTracing(() => { | ||
return nativeFetch(options.url, requestOptions).then(response => { |
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.
wait this seems off. Why would we need to suppress tracing when using nativeFetch
? Shouldn't this be instrumentation-free in the first place?
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.
yeah, this seems to be true, this is not triggering anything anyhow. Maybe we can just remove the comment and call it a day 😅
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.
yeah I don't see us switching to browser OTel anytime soon 😅
0c4ba76
to
8acf5d1
Compare
Noticed that this was missing, should be fine to do that!