T
tRPC
how can I globally set a "middleware" callback for all onErrors on my React Query calls?
how can I globally set a "middleware" callback for all onErrors on my React Query calls?
this is a little specific but Im struggling on it
Im using the TRPC server as a BFF for my backend and for every call on the client I'm sending a token so backend can authenticate it, when the token is not valid anymore api return status code 403 (forbidden).
what I want to do in my FE is that every onError call I check the status to see if it is forbidden and if it is I will redirect the user and do some stuff (like remove the token from storage and redirect)
since Im using ReactQuery I know that where I instantiate the QueryClient I can pass some default options and there's a callback for onError, but I cannot follow this way cause its on the top of the application and the rest "arent loaded" such as the router cause its bellow the QueryClient provider, so I can not access the Navigator from react router dom because it dont exist on that scope.
I think what I can do is maybe impossible, but Im asking that because I would like suggestion for what I can do instead
within the batch link i override the fetch and do custom things inside there. you can see the response codes and what not there. you also have access to the client as you can see i'm updating the local session in here
Looking for more? Join the community!
T
tRPC
how can I globally set a "middleware" callback for all onErrors on my React Query calls?
T
tRPC
how can I globally set a "middleware" callback for all onErrors on my React Query calls?
Recommended Posts
Upgrading from tRPC v9 and NextJS v12. Should I upgrade NextJS first or tRPC?I have an app built from the tRPC + NextJS + Prisma starter, and I'd like to upgrade from tRPC v9 anprefetchinfinite not working when inputs are differentIve been trying to figure out why prefetching doesnt work when the inputs are different between preftRPC + App directory + SSR - current state?What is the current state of the technologies working together with or without SSR?
It looks like soHydration failed because the initial UI does not match what was rendered on the server```Unhandled Runtime Error
Error: Hydration failed because the initial UI does not match what was reReact tsc starts checking server typesMy tsconfig files are different on the server and client. When I run "tsc" on react client, It is trNextJS 13 Build failingIssue also seen in this PR https://github.com/trpc/trpc/pull/4574 I found. None of the webpack workGoogle OAuth callbackany one help how to handle google oauth callbackurl using tRPCInfering query/mutation callback opts parameterHey 🙂
Thanks for your hard work on this awesome library.
I want to create tRPC router, but i want Type helpers to match available pathsGiven a router like this:
```typescript
const appRouter = t.router({
post: t.router({
list: t.Best way of handling recurring events through NextJs and tRPCHi, I'm working on a project that handles users' "bonuses" and I need to refill these bonuses every