feat(core): Ensure url, http.query and http.fragment are directly added#22547
feat(core): Ensure url, http.query and http.fragment are directly added#22547mydea wants to merge 3 commits into
url, http.query and http.fragment are directly added#22547Conversation
url, http.query and http.fragment are directly added
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 2 potential issues.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit d6bc9b0. Configure here.
| } | ||
| if (parsedUrl.hash) { | ||
| attributes['http.fragment'] = parsedUrl.hash; | ||
| attributes[HTTP_FRAGMENT] = parsedUrl.hash.slice(1) || undefined; |
There was a problem hiding this comment.
Split HTTP query fragment formats
Medium Severity
This commit normalizes http.query and http.fragment by stripping leading ? and # in core fetch, HTTP breadcrumbs, URL span helpers, and Node server spans, but browser XHR and Node undici fetch breadcrumbs still emit the raw URL.search / URL.hash values with those prefixes. The same app can therefore report different query and fragment shapes on http.client spans and HTTP breadcrumbs depending on the API used.
Reviewed by Cursor Bugbot for commit d6bc9b0. Configure here.
size-limit report 📦
|


We rely on this in many tests, but only set this in span inferral often, so it depends on OTEL stuff.