Changing variables in watchQuery after polling started

Hi, so I’m creating an observable with the client.watchQuery method and watch on it. It works fine. But let’s say variables in my query changed.

How to properly handle that? Do I really have to kill the old observable and create a new one which includes the new query?

In other words: How to change variables of a polling ObservableQuery in runtime?

Idea: Pass in an optional callback that returns the current variables.

I ask, because doing that kill/respawn approach would require a lot of refactoring in my code.

Thanks!

[stubailo]

Or yeah, I guess there are also some extra things stored in Redux when you start/stop a query. So it could be less efficient, but we haven’t run into that as a source of problems in our production apps. It’s mostly React renders that are very costly.

[timsuchanek]

Hey guys, thanks for the fast answers. @Poincare your solution works like a charm. So do you want some unit tests or better later when there is a better api for this use case?