Allow replace method to bypass param validation?

[enguerranws]

Hi,

I'm wondering if there's any passthrough feature (like zod does)?

My use case is that we want to using tracking params on routes, but on some routes we have forms that are updating URL query params (using type-route replace() method), and are initially populated with query params values (so the user can share the url).

So, I'm taking original params in the URL, I'm merging them with my form key/values and give it all to the replace() method, which throws an error.

To make it work, I simply added the tracking params key to my route definitions, but I'll may have to change that if we need another tracking tool or whatever.

Is there a way to make type-route more compliant, so we could do something like:

userList: defineRoute(
    {
      page: param.query.optional.number,
    },
    () => "/user",
    {
      passthrough: true
    }
  )
 
 // then I could do
 
 routes.userList({page: 2, my_unknown_param: "whatever"}).replace() // without throwing an error

[bradenhs]

Thanks for opening this issue! Your use case makes sense. I'm undecided on the best way to go about making this easier. Something like your passthough parameter idea is a sensible suggestion but I want to give it more thought. Short-term you could have a base route which you .extend every other route from which should make adding the additional parameters less work. Are you already doing that?