How to not send request in specific condition in useQuery()

Yyaviscoke

5/26/2023

  const { data: artists, isLoading } = api.findArtist.useQuery({
    name: search,
  });

  const { data: artists, isLoading } = api.findArtist.useQuery({
    name: search,
  });

I have this in my code so in beginning search is empty string and is it possible to write condition when it should run request and when not, when search is empty I dont want to run request

Solution:

enabled: !!search

Jump to solution

Solution

AKAlex / KATT 🐱

5/26/2023

enabled: !!search

Yyaviscoke

5/26/2023

thankss

Looking for more? Join the community!

tRPC

How to not send request in specific condition in useQuery()

Join Server

tRPC

How to not send request in specific condition in useQuery()

Join Server

Recommended Posts

TRPCClientError: fetch failedI get the below error when createTRPCProxyClient runs on BE of a Next.JS app hosted on Vercel: ```T inferRouterOutputs not inferringCould anyone point me in the right direction to why my types aren't being inferred here? (Using T3 b Modular Router ThoughtsHello, I hope I can convey clearly what I hope to accomplish. To start, I have a monorepo, with a fe Issue with trpc fetch when trying to pass Clerk auth to contextI'm currently trying to add Clerk auth to my trpc context, but I just keep getting this error: `Err BullMQ + TRPCCurious how to configure BullMQ with TRPC correctly. Currently I have the queue, queueevents, and th Trpc refetches all of the queries when i run a mutationIm running node 16.15.0 with Pnpm When i run a mutation for some reason all of the queries get refet tRPC Client on NodeJS server keeps complaining that no fetcher has been configuredHey, I want to create a tRPC setup where I have one server (works fine) and then a client which is c Best Practice to Fetch a Query OnDemandWhat's the best practice to fetch a query on demand? I don't have the context for the query's input