❓-help

Handling Query Errors at Root of App (v9)

GgwaiLoFi

12/13/2022

I want to show an error toast on my NextJS frontend every time there is an error from useQuery in a functional component. Is there a way to add something at the root of my app that can watch for trpc errors or do I have to handle it at every use of useQuery? (note: i am on v9)

AKAlex / KATT 🐱

12/14/2022

Check links in the docs Or default react query options works too

Looking for more? Join the community!

❓-help

❓-help

Recommended Posts

tRPC Client webpack errorAs soon as I add the client part to my legacy app i get an error and Can't figure out what is wrong.cookies, headers and authenticationin express I can do something like `res.cookie("name", "value")` for example. alternatively I can d trpc hook pattern. This works, but I’m not convinced…I want to call my route when a button is clicked and have access to isLoading, onError etc… I have i Catch TRPCError, ZoddError on the front-endi am throwing a TRPCError in a mutation. i dont understand how to catch this error in the OnError me implicitly has type 'any' because it does not have a type annotation and is referenced directlyRunning into this error. I feel like it's some sort of infinite recursion issue, but not sure where Why do some examples create PrismaClient in context, and others don’tIs there a specific reason to do this or not to do this? I can imagine with the new Prisma extension