What would be the right way to use RQ in a UI component library? #10100
Unanswered
dil-atelegdi
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone! I just can't seem to find the right answer in the docs, maybe someone can help me out here. I'm building a UI component library which uses RQ to fetch data on its own (it's kind of a separate page meant to be shared across apps) and will be used in larger applications also using RQ. Here's the question:
Should my lib initialize and isolate its own queryClient with its provider together or should it accept it from the host app and use theirs? The versions of RQ used by the app and my lib are very likely to be out of sync eventually (or practically always), I have little control over that. My current approach is isolating the libs RQ.
What is your advice on this? Your help is much appreciated!
Beta Was this translation helpful? Give feedback.
All reactions