Repository navigation
React Router - Support Lazy-Loaded Routes #15040
Description
Problem Statement
Ref: #15027
In the current version, lazy-loaded routes in the React Router are not parameterized correctly in the SDK.
We are able to parameterize up to the deepest non-lazily loaded route, and no further as we are not able to reach the full routes tree.
Solution Brainstorm
We can investigate whether we can implement a solution using the currently-unstable "Fog of War" on React Router 7 to get the full routes tree and whether we can traverse it and create parameterized transactions.
Activity
peteragarclover commentedon Jan 17, 2025
As a simple escape hatch solution which could be helpful in the short term (or possibly generally), how about exposing a configuration option to allow people to provide a custom implementation of
getNormalizedName()that doesn't rely on the entire routes collection to be populated?E.g. A naive implementation could be similar to the documented javascript browser tracing integration: https://docs.sentry.io/platforms/javascript/tracing/instrumentation/automatic-instrumentation/#beforestartspan
I believe that at least for our use case this should be sufficient to normalize all our routes, so it might be generally useful 🤷
andreiborza commentedon Jan 20, 2025
@peteragarclover thanks for sharing that, we'll look into that.
onurtemizkan commentedon Jan 23, 2025
@peteragarclover, @andreiborza - This issue should be resolved by #15039
@peteragarclover, please let us know if there are any further issues after trying the next release.