Different staleTime for data from HydrationBoundary

[LightScrool]

Hello!
First of all, thank you for this beautiful library:)

About the problem
Data in my application updates quite often and it is important to provide fresh data
That is why i need to have staleTime = 0
But i have SSR in the application, and to prevent refetching immediately on the CSR, the documentation recommends to increase staleTime

So i have to either increase staleTime to avoid refetching immediately but that could worsen UX, or keep staleTime equals to zero, but there will be extra requests

I tried to fix it by setting staleTime=10*1000 on initializing QueryClient and then in useEffect (so after rehydration) changing it to zero (by queryClient.setDefaultOptions).
But changed staleTime is applying only to new queries. The ones that was called during rehydration continue to work with staleTime=10*1000.

It's seems to me like there should be different solution to the immediate refetch on CSR, than changing the staleTime.

[TkDodo]

You can set staleTime to 1000 which should be enough to avoid double fetching from SSR and still short enough to provide fresh data.

staleTime can also be a function so you can make it dynamic depending on whatever you want.