chore: Update react query version

[dyaa]

Closes #2352

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
next-prisma-starter	✅ Ready (Inspect)	Visit Preview	Aug 8, 2022 at 2:19PM (UTC)
www	✅ Ready (Inspect)	Visit Preview	Aug 8, 2022 at 2:19PM (UTC)

[dyaa]

So I've made some quick investigations, and I found out the following:

1. setLogger has been removed in the latest beta version, and instead, a custom logger can be passed to QueryClient's constructor.
2. There will be type mismatches with @trpc/react package since it's using an older version of react-query.

Next:

1. I'll make a full upgrade to the react-query package to their beta version and update all internal packages to use the beta version.
2. I'll remove the dependency on the env variable REACT_QUERY_VERSION.

Any other suggestions are welcome.

CC @KATT

[KATT]

1. setLogger has been removed in the latest beta version, and instead, a custom logger can be passed to QueryClient's constructor.

Feel free to remove our use of setLogger everywhere.

2. There will be type mismatches with @trpc/react package since it's using an older version of react-query.

What sort of stuff? Will it be impossible to support both?

Next:

1. I'll make a full upgrade to the react-query package to their beta version and update all internal packages to use the beta version.
2. I'll remove the dependency on the env variable REACT_QUERY_VERSION.

Will it be impossible to support both versions?

[dyaa]

I don't think that's possible without having @trpc/react using the same version for react-query.

[KATT]

cc @dyaa update to main which doesn't try to make this cross-compatible anymore. Will be a lot easier to fix the issues then.

[KATT]

also please get github sponsors working so I can send you money for it :) #1599

[KATT]

I'll send some more money if you fix it, just sent you a fiver for a beer or a coffee now 🍻

[kodiakhq]

This PR currently has a merge conflict. Please resolve this and then re-add the ['🚀 merge', '⬆️ dependencies'] label.

[KATT]

Oops, I closed the wrong PR!

[KATT]

I'm bumping the version now to see if it fixes it :)

[KATT]

Lovely, I just want to get some feedback from @trpc/trpc-core in regards to the requestContext property

[KATT]

Could you add a note of this in https://alpha.trpc.io/docs/migrate-from-v9-to-v10 anywhere? I'll clean it up later.

@sachinraja @jlalmes what do you think we should do here now that the context keyword is taken?

Some options:

• Put all trpc option under trpc - quite annoying for the 99% use-case but also nice to have a distinct place for "our" versus "theirs" in options
• Call it trpcContext? Potentially prefix all our vars with trpc?
• operationContext?
• opContext?
• callContext?

[KATT]

Moved to #2395.

Will merge this one and we can iterate as it's still alpha.

[KATT]

@all-contributors add @dyaa for code, test

[allcontributors]

@KATT

I've put up a pull request to add @dyaa! 🎉

[github-actions]

This pull request has been locked because it had no new activity for 30 days. If you think, this PR is still necessary, create a new one with the same branch. Thank you.