refetchInterval function returning 0 treated as false

[filipw01]

I'm using this option in my query

        refetchInterval: ({ state: { data } }) => {
          if (data?.lookUpState.type === 'Completed') {
            return false
          }
          return 0
        },

I'm expecting 0 to mean 0ms so instantly refetch, but it doesn't work probably because 0 is treated as falsy, same as false.

Is that expected? I'm not sure if I should open an issue to improve docs or an issue to treat 0 as 0ms

[TkDodo]

an interval of 0ms makes no sense in practice.

[filipw01]

In my case I want to chunk a request to return intermediate results. Kind of like streaming, but spread across multiple fetches
So I want to start the next request as soon as the previous one finishes. I'm currently returning 1 to achieve this and it seems to be working quite well

I know 0ms setTimeout isn't really different from 1ms as there's a minimum, so this is more of a nitpicking for correctness.

If you don't think it should be explicitly handled, do you think mentioning it's handled like this when it's falsy in the docs is the way to go?

[TkDodo]

In my case I want to chunk a request to return intermediate results. Kind of like streaming

please try our streamedQuery for this.

https://tanstack.com/query/v5/docs/reference/streamedQuery

[filipw01]

OMG, thanks. That looks like what I want

[filipw01]

I tried using it, but I don't think it's correct for my case. BE does the accumulation so the last chunk returns the full result. I tried using reducer but it didn't work and there were some TS issues too.

I'll stick to my workaround. Let me know if I should update the docs or code to address this or if it should be left in the gray area for now