You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: Detect raw-to-parameterized route upgrades in cross-usage scenarios
- Add isParameterizedRoute() helper to detect if route has parameters (:id) or wildcards (*)
- Update shouldSkipNavigation() to detect raw path to parameterized route upgrades
- Enables proper updateName() calls in cross-usage scenarios
- Fixes 3 failing cross-usage navigation tests
In cross-usage scenarios (e.g., wrapCreateBrowserRouter + wrapUseRoutes), the first wrapper
may create a span with the raw URL path (e.g., /second-level/321/third-level/123) if nested
routes aren't fully resolved yet. The second wrapper should then upgrade it to the parameterized
form (e.g., /second-level/:id/third-level/:id).
Previously, this upgrade wasn't detected because we only checked for wildcard-to-parameterized
and length-based specificity. Now we also detect raw-to-parameterized upgrades.
0 commit comments