Handling error globally

MMugetsu

11/8/2022

According to the docs on errors https://trpc.io/docs/v10/error-handling I should get such error object on client side when its thrown from procedure If I understand correctly. But Im having a problem with it as it doesnt seem to be typed as TRPCError on the client and dont contain few props from described in docs.

        queryCache: new QueryCache({
          onError: async (error: any) => {
            console.log(error.id);
            console.log(error.message);
            console.log(error.code);
            console.log(error.data);
            console.log(error?.data?.httpStatus === 401);
            if (
              error?.data?.httpStatus === 401 ||
              error.message === "UNAUTHORIZED"
            ) {
              await signOut({ redirect: false });
            }
          },
        }),

        queryCache: new QueryCache({
          onError: async (error: any) => {
            console.log(error.id);
            console.log(error.message);
            console.log(error.code);
            console.log(error.data);
            console.log(error?.data?.httpStatus === 401);
            if (
              error?.data?.httpStatus === 401 ||
              error.message === "UNAUTHORIZED"
            ) {
              await signOut({ redirect: false });
            }
          },
        }),

UUUnknown User

11/8/2022

Message Not Public

MMugetsu

11/8/2022

>All errors that occur in a procedure go through the onError method before being sent to the client I care about the part which lands on the client. Does it mean I cant get proper typings and all information regarding the error on the client? Or Am I doing something worng

UUUnknown User

11/8/2022

Message Not Public

MMugetsu

11/9/2022

Its not in my desire to define onerror for every query/mutation I make. I want a global error handler of 401 but I wonder why some info is missing from onError in QueryCache(global handler)

Looking for more? Join the community!

tRPC

Handling error globally

Join Server

tRPC

Handling error globally

Join Server

Recommended Posts

cant access trpc endpoints via the browseri'm converting some express endpoints to trpc, and I cant figure out how to access my endpoints via tRPC without SSRWhen using tRPC with ssr it uses `getInitialProps`, which has kinda of a cool effect in terms how a trpc + expo react native issueDoes anyone know how to solve this? Im not familiar with webpack at all. I’m a junior frontend.Can you chain middlewares in v10?Would I be able to make a rate limit and isAuthed middleware, then put queries behind both middlewar Load data client-side via react-query while using tRPC with SSRIs there any way to load data client-side when using tRPC? I want my page to be rendered and load da Serving clients in another repository?Would it be possible for tRPC to act as a server for clients in another repository and if so how wou When not to use tRPC?Is there any scenario when building a mobile and/or a web app with backend that you would not recomm Bi directional infinite query example with prismaI'm working on a project that is using this pattern, but my `hasPreviousPages` gets blown away when Websockets not sending dataHi, I have a websocket route that doesn't seem to be sending any data I added a setInterval to tes Query keysHi! I'm super new to TRPC and based on my understanding, TRPC has a thin wrapper around react query.