router-core/search-params

You can validate TanStack Router search params using adapters for Zod, Valibot, or ArkType by defining a schema and applying it through the `validateSearch` method to ensure type-safe URL parameter parsing.

To preserve search params across navigations in nested routes, apply the `retainSearchParams` middleware, which ensures parent route parameters are inherited and kept intact during route transitions.

`loaderDeps` controls when and how search params affect route cache keys, allowing you to determine the specific URL parameters that trigger data fetching or cache invalidation during navigation.

Yes, you can customize URL serialization by defining custom `parseSearch` and `stringifySearch` rules, allowing you to control how search params are encoded and decoded in the browser URL.

You can remove specific search params during navigation by applying the `stripSearchParams` middleware, which prunes defined parameters from the URL when transitioning between routes.

Parent route search params inherit down to child routes by applying middlewares that manage parameter persistence, ensuring a consistent UX by sharing validated URL state across the nested route hierarchy.