-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Parameterized paths not picked up when using react-router-v6
with basename
#9061
Comments
This fix was released with https://github.com/getsentry/sentry-javascript/releases/tag/7.71.0. Thanks for reporting @rottbers! |
I've tested the fix but unfortunately the parameter values path (e.g.
|
@onurtemizkan mind taking a look? |
@rottbers, could you provide us a reproduction? The patch is tested with the new case, so we need to see the specifics to get the root of it. |
This issue has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you remove the label "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/react
SDK Version
7.69.0
Framework Version
React 18
Link to Sentry event
No response
SDK Setup
No response
Steps to Reproduce
Hope another test case is sufficient as reproduction, it's based on the existing ones in
reactrouterv6.4.test.tsx
:Expected Result
Expect name to contain parameter names (i.e.
/admin/:orgId/users/:id
)Actual Result
Name contains the parameter values (e.g.
/admin/some-org-id/users/some-user-id
)The text was updated successfully, but these errors were encountered: