Why might search be persisted through navigation?

I am wondering: why might search items be carried through an imperative call to

navigate({ to: '/some-place' })

navigate({ to: '/some-place' })

(from

useNavigate()

useNavigate()

)? I cannot for the life of me figure out why, since the default behavior seems to be to clear the search items when

navigate()

navigate()

is called even without explicit

search: {}

search: {}

. In my case, explicitly calling

navigate({ to: '/some-place', search: {} })

navigate({ to: '/some-place', search: {} })

does not work--the search string is carried through. I cannot unfortunately reproduce this in a sample project. I'm happy to provide my full project's code but it relies on a separate backend. I'm hopeful that someone who really understands the internals of this library might be able to help. Thank you!

TanStack•2y ago•

11 replies

then-purple

Why might search be persisted through navigation?

I am wondering: why might search items be carried through an imperative call to

navigate({ to: '/some-place' })

navigate({ to: '/some-place' })

(from

useNavigate()

useNavigate()

)? I cannot for the life of me figure out why, since the default behavior seems to be to clear the search items when

navigate()

navigate()

is called even without explicit

search: {}

search: {}

. In my case, explicitly calling

navigate({ to: '/some-place', search: {} })

navigate({ to: '/some-place', search: {} })

Why might search be persisted through navigation?

Similar Threads

Why might search be persisted through navigation?

Similar Threads

Similar Threads

Similar Threads