2 replies

best strategy for handling global trpc errors on the client

I’m using trpc in my nextjs app. In one of my procedures, I check if a server is banned. If it is, I throw a

TRPCError

TRPCError

with code

FORBIDDEN

FORBIDDEN

and a custom message:

const guildIsBanned = await ctx.db.guildBotBans.findFirst({
  where: { guildId: input.guildId },
});

if (guildIsBanned) {
  throw new TRPCError({
    code: "FORBIDDEN",
    message: `Server is banned from using the bot for reason: \`${guildIsBanned.reason}\``,
  });
}

const guildIsBanned = await ctx.db.guildBotBans.findFirst({
  where: { guildId: input.guildId },
});

if (guildIsBanned) {
  throw new TRPCError({
    code: "FORBIDDEN",
    message: `Server is banned from using the bot for reason: \`${guildIsBanned.reason}\``,
  });
}

This works, but on the frontend it just results in empty pages being rendered whenever the error is thrown.

I have 20+ pages in my app, and I don’t want to manually add onError logic to every useQuery just to check if the error code is

FORBIDDEN

FORBIDDEN

and then render a

You are banned

You are banned

component.

Is there a neater way of handling this error globally?

TTC

Theo's Typesafe Cult•6mo ago•

2 replies

v28

best strategy for handling global trpc errors on the client

I’m using trpc in my nextjs app. In one of my procedures, I check if a server is banned. If it is, I throw a

TRPCError

TRPCError

with code

FORBIDDEN

FORBIDDEN

and a custom message:

const guildIsBanned = await ctx.db.guildBotBans.findFirst({
  where: { guildId: input.guildId },
});

if (guildIsBanned) {
  throw new TRPCError({
    code: "FORBIDDEN",
    message: `Server is banned from using the bot for reason: \`${guildIsBanned.reason}\``,
  });
}

const guildIsBanned = await ctx.db.guildBotBans.findFirst({
  where: { guildId: input.guildId },
});

if (guildIsBanned) {
  throw new TRPCError({
    code: "FORBIDDEN",
    message: `Server is banned from using the bot for reason: \`${guildIsBanned.reason}\``,
  });
}

FORBIDDEN

FORBIDDEN

and then render a

You are banned

You are banned

component.

Is there a neater way of handling this error globally?

best strategy for handling global trpc errors on the client

Similar Threads

best strategy for handling global trpc errors on the client

Similar Threads

Similar Threads

Similar Threads