Clojurians Log v2

this is a missing piece i've been looking for! here's a question: if I have a polling query that polls at times T0, and will poll again at T1. if T0 query stalls and T1 passes, will it requery? or will it wait for the first query to return and then start the poll timer from T0.1, when the T0 query returns. I have a frequent polling endpoint that sometimes stalls, and I don't want to requery the same query that's already in progress. does that make sense?

Thank you for the kind words 😄 That is an interesting usecase and likely common when you have shorter polling intervals. The current behavior is that the query at T1 will be dispatched regardless if the query at T0 finished or not. Thinking more about it, this is not ideal because if T1 query finishes faster (somehow) than T0, the :query-success event of T0 will overwrite the data from T1 which is bad I'll fix this by making the behavior as you mentioned and adding an option to force refetch on tick if previous poll request is still in flight

Also note that polling happens on an interval, not from the last successful query result. If you have :polling-interval-ms 5000 (every 5 seconds) a poll dispatch will be attempted every 5 seconds not 5 seconds after last successful result. If at T5 you have a request in flight, none will be triggered, then the previous poll request finishes at T7 (no new request or timer is started here), T10 (interval tick 5 seconds from T5) polling dispatches a new request.

Fixed and released along with other semi related changes in 0.5.0 see https://github.com/shipclojure/re-frame-query/blob/main/CHANGELOG.md