Skip to content

Conversation

@JobenM
Copy link

@JobenM JobenM commented Feb 15, 2021

I had an issue within our application which basically meant we were overwriting our ReactQueryClientContext with the default because of some unexpected rerendering. This meant even having set <QueryClientProvider> at basically root we were still getting the error No Query set... error. I think it would be great to supply a correct error message in this scenario as I'm sure I won't be the only one to come across this in the future.

First time contributing here, let me know if I need to change anything :)

@vercel
Copy link

vercel bot commented Feb 15, 2021

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/tannerlinsley/react-query/aqfh4ceuo
✅ Preview: https://react-query-git-fork-jobenm-validation-for-overwritin-bdce76.tannerlinsley.vercel.app

@TkDodo
Copy link
Collaborator

TkDodo commented Feb 15, 2021

Please have a look at this issue: #1764

i fear this PR might worsen the situation if you mount two independent microfrontends, since the second one will just get the Error :/

@tannerlinsley
Copy link
Member

tannerlinsley commented Feb 15, 2021 via email

@tannerlinsley
Copy link
Member

I've got a separate fix which also addresses a few other related concerns in #1805

@JobenM
Copy link
Author

JobenM commented Feb 15, 2021

Awesome. Cheers @tannerlinsley 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants