{{ message }}
feat(react-router): Clean up bogus * http.route attribute on segment spans#20471
Open
nicohrubec wants to merge 2 commits intodevelopfrom
Open
feat(react-router): Clean up bogus * http.route attribute on segment spans#20471nicohrubec wants to merge 2 commits intodevelopfrom
* http.route attribute on segment spans#20471nicohrubec wants to merge 2 commits intodevelopfrom
Conversation
Contributor
nicohrubec
changed the title
* http.route attribute on segment spans
mydea
approved these changes
Apr 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In span-streaming mode, the existing
processEventcleanup of bogus*http.routeattributes doesn't run, so segment spans end up with the garbage route. Ports the same logic to theprocessSegmentSpanhook.Added unit tests for this (also for the event path), since the alternative would have been to add a separate streaming e2e test for react-router, which seems overkill to me.
Closes #20361