Skip to content

fix(react): Match routes with parseSearch option in TanStack Router instrumentation #14328

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Merged
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion packages/react/src/tanstackrouter.ts
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,7 @@ export function tanstackRouterBrowserTracingIntegration(
if (instrumentPageLoad && initialWindowLocation) {
const matchedRoutes = castRouterInstance.matchRoutes(
initialWindowLocation.pathname,
initialWindowLocation.search,
castRouterInstance.options.parseSearch(initialWindowLocation.search),
{ preload: false, throwOnError: false },
);

Expand Down
4 changes: 4 additions & 0 deletions packages/react/src/vendor/tanstackrouter-types.ts
Original file line number Diff line number Diff line change
Expand Up @@ -29,6 +29,10 @@ SOFTWARE.
export interface VendoredTanstackRouter {
history: VendoredTanstackRouterHistory;
state: VendoredTanstackRouterState;
options: {
// eslint-disable-next-line @typescript-eslint/no-explicit-any
parseSearch: (search: string) => Record<string, any>;
};
matchRoutes: (
pathname: string,
// eslint-disable-next-line @typescript-eslint/ban-types
Expand Down
Loading