Phillip Lanclos
Phillip Lanclos
It looks like `no-unsafe-declaration-merging` would require an upgrade. Should that be done in a different PR?
`@typescript-eslint/parser` would need to be upgraded to include the newer `no-unsafe-declaration-merging` rule.
> Ran into the same issue today when setting up `nx` for the first time > > My changes to the Nx config would never work driving me insane as...
If `onCompleted` was "fixed" by not allowing other same queries to be notified, I think that is still a very useful use-case. Should there be a different callback to support...
I agree. I want a `onDataUpdated` hook so I don't have to use a `useEffect`, which is how we are using `onCompleted`.
I do like `onRefetch`, makes sense. I'm just not updating for now lol. But it seems like you would have to use a `useEffect`, which feels bad.
In make example from above, where one query is polling and the other is not. I want the non-polling query to be notified if it's data gets updated by the...
@jerelmiller That's basically it. We are wanting to reset state in another component that when the data changes. Our specific example if for notifications. The notification bubble in the header...
@jerelmiller I think I'm on the same lines of thinking as @dylanwulf in that we try to stay away from using `useEffect` where we can, and the old `onCompleted` helped...