Does validateSearch have to automatically set page url with that search params?

reacttypescript

I am using validateSearch with

zodValidator

zodValidator

as follows:

export const Route = createFileRoute("/app/jobs/")({
        ...
        validateSearch: zodValidator(jobsSearchParamsSchema)
})

export const jobsSearchParamsSchema = z.object({
    q: fallback(z.string(), "").default(""),
    sortBy: fallback(z.string(), "").default(""),
    sortOrder: fallback(z.enum(["asc", "desc", ""]), "").default(""),
})

export const Route = createFileRoute("/app/jobs/")({
        ...
        validateSearch: zodValidator(jobsSearchParamsSchema)
})

export const jobsSearchParamsSchema = z.object({
    q: fallback(z.string(), "").default(""),
    sortBy: fallback(z.string(), "").default(""),
    sortOrder: fallback(z.enum(["asc", "desc", ""]), "").default(""),
})

When I open

/app/jobs

/app/jobs

it automatically appends that default search params to url so in the web browser, I see

/app/jobs?q=&sortBy=&sortOrder=

/app/jobs?q=&sortBy=&sortOrder=

.

Can I change that behaviour so that it won't be appended to the URL? I would like to have some

null

null

instead to distinguish between an empty

and a not set

TanStack•3mo ago•

3 replies

hurt-tomato

Does validateSearch have to automatically set page url with that search params?

reacttypescript

I am using validateSearch with

zodValidator

zodValidator

as follows:

export const Route = createFileRoute("/app/jobs/")({
        ...
        validateSearch: zodValidator(jobsSearchParamsSchema)
})

export const jobsSearchParamsSchema = z.object({
    q: fallback(z.string(), "").default(""),
    sortBy: fallback(z.string(), "").default(""),
    sortOrder: fallback(z.enum(["asc", "desc", ""]), "").default(""),
})

export const Route = createFileRoute("/app/jobs/")({
        ...
        validateSearch: zodValidator(jobsSearchParamsSchema)
})

export const jobsSearchParamsSchema = z.object({
    q: fallback(z.string(), "").default(""),
    sortBy: fallback(z.string(), "").default(""),
    sortOrder: fallback(z.enum(["asc", "desc", ""]), "").default(""),
})

When I open

/app/jobs

/app/jobs

it automatically appends that default search params to url so in the web browser, I see

/app/jobs?q=&sortBy=&sortOrder=

/app/jobs?q=&sortBy=&sortOrder=

.

Can I change that behaviour so that it won't be appended to the URL? I would like to have some

null

null

instead to distinguish between an empty

and a not set

Does validateSearch have to automatically set page url with that search params?

Similar Threads

Does validateSearch have to automatically set page url with that search params?

Similar Threads

Similar Threads

Similar Threads