Replies: 2 comments
-
Since it's expected behavior, maybe the option should be renamed to something like |
Beta Was this translation helpful? Give feedback.
0 replies
-
I have added a note about this in the docs in the meantime. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The docs say:
To me that means as long as skip is true, the query is not fired. That much is true.
However when "skip" changes from
true
tofalse
, the query is executed. This is imo totally unexpected and not the meaning of skip.Conside the following use case:
I have a query that polls every 10 seconds. However, sometimes I want to skip this query. I set skip to true, and that stops the polling. Later I set skip to false again, and when it's time to poll, then I want the query to fire. Not immediately after I set it to false.
At the moment skip behaves more like enabled / disabled. But skip to me means "a query that was planned should not happen". The skip option itself should never trigger a query.
Beta Was this translation helpful? Give feedback.
All reactions