Prevent escaping special characters for URL search params

[Skurrr]

Hi,
Is it possible to disable encode for search query params (or disable encoding for special/reserved chars)? Even with custom search serialize/deserialize, params are escaped internally by router.

In our use case comma is used as search param delimiter for multi values and encoded comma is used for single value.

For example:
Search param filter=in(val1,val2) is automatically encoded to filter=in(val1%2Cval2).

As far as understand RFC specification filter=in(val1,val2) and filter=in(val1%2Cval2) are not equal.

[schiller-manuel]

cc @SeanCassiere

[SeanCassiere]

Sorry, I mistakenly cleared all of my GitHub notifications a short while back and this one got swallowed in.

We recently modified our patch of qss over to something using URLSearchParams. Is this still a problem for you @Skurrr?

[Skurrr]

Yes, it still not possible to skip percent encoding for reserved chars for search query params stringify function.
Tested on tanstack/react-router: 1.117.0.

To be honest RFC spec a little bit confusing, however i believe it should be possible tp use un-escaped comma as delimiter and encode comma only if it's used inside data fragment.

As nasty workaround we could double encode data fragments as part of custom stringify function but it looks and feel awful :(

Edit:
Actually it is possible to skip encoding for reserved chars if we use navigate function without search params object and add query params to URl, like this:

navigate({
       to: '/search?filter=in(val1,val2)',
})

but i quess it's not how navigate function should be used.

[Skurrr]

@SeanCassiere would it be possible to escape search params in the similar way as path params? See: https://tanstack.com/router/latest/docs/framework/react/api/router/RouterOptionsType#pathparamsallowedcharacters-property