If not using subscriptions and instead either say ...
# apollo-kotlin
j
If not using subscriptions and instead either say polling or providing some kind of "pull to refresh" etc UI, what's best way of coordinating this when
watch
is being used to drive UI.....I think someone mentioned before that separately calling say
execute
on a query will cause cache to be updated and any UI observing the flow from
watch
will get the update?
b
yes,
watch
observes the cache, so if it's updated with fresh data thanks to a query from another part of the app, it will notify
👍 1
1