Unnecessary re-render with enabled false about react-query

[TkDodo]

I think when both are enabled, the parent initiates the fetching. Now, the child initiates the fetching and it kinda depends on our batching if there is going to be another re-render or not. You can adapt batching functionality here:

https://tanstack.com/query/v5/docs/reference/notifyManager#notifymanagersetscheduler

[burakgormek]

Thanks for the fast response. I see, for enabled scenario, that makes sense but...

Doesn't the parent have to do nothing if it's not enabled? Although nothing is changed in destructed values. (isError just an example)

[TkDodo]

yeah there's something "off" here since isError didn't change, there shouldn't be a re-render for this observer. Would you like to look into it ?

[burakgormek]

I did a little look to find what cause a re-render but not found anything yet. Its not easy to understand the internals for the first look (for me).

I want to look deeper into it, but our project deadline does not allow it :/

[Mrityunjay-Palled]

Try to pass enabled prop to the child component,

1. In Parent Component
   pass the enabled prop down to the child component enabled={isError}

2)In Child Component
enabled: enabled, // Set enabled based on the parent's status

ensuring that the child's useQuery hook represents the parent's enabled status