Replies: 3 comments 5 replies
-
Is |
Beta Was this translation helpful? Give feedback.
1 reply
-
Could also set the global |
Beta Was this translation helpful? Give feedback.
1 reply
-
Just came looking for this, as well. Would love to see it in the pipeline! |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
In my use-case (mint page), I need somewhat fresh data (mint stats), but doesn't need to be always up-to-date with the latest block.
If I enable
watch
, it starts polling each 4s for the latest block, which burns through my alchemy quota pretty quickly.Exposing the useQuery parameters #882 would be a good way to solve this, but I get that there are probably some edge cases to handle before doing that.
I suggest exposing just the
refetchInterval
parameter, as a way to give users full control over how fresh the data needs to be, since this is a major factor in node quota usageBeta Was this translation helpful? Give feedback.
All reactions