fix(react-router): Set correct transaction name when navigating with object argument#19590
Merged
nicohrubec merged 4 commits intodevelopfrom Mar 3, 2026
Merged
fix(react-router): Set correct transaction name when navigating with object argument#19590nicohrubec merged 4 commits intodevelopfrom
nicohrubec merged 4 commits intodevelopfrom
Conversation
Contributor
size-limit report 📦
|
andreiborza
approved these changes
Mar 3, 2026
Member
andreiborza
left a comment
There was a problem hiding this comment.
LGTM, thanks for taking care of this 🙏
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
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.
When navigate() or is called with an object
toprop (e.g. { pathname: '/items/123' }), the transaction name currently is set to[object Object]. This adds aresolveNavigateArghelper that extracts the pathname from object arguments:/Closes #19580