trpc mutations for searching data

Recently was told that using mutations to fetch list data is bad. I can agree with this on a high level from the naming convention, but I'm curious what the deeper reasons are. Are there specific "internal" or architecture related reasons why mutations shouldnt be used to search data at all?
Because queries can be driven by state innately and cache locally, they’re just the canonical way to do this
Canonical with respect to?
Not sure what that means
No description

Looking for more? Join the community!

Recommended Posts
The inferred type of 'trpc' cannot be named without a reference. A type annotation is necessary.Hello everybody... I have a nodejs + reactjs + yarn monorepo using turbo. I am getting this error whIs `inferSubscriptionOutput` missing in 10.x?I'm working on a vue 3 app with reactive state and need to infer the output of a subscription. It lis there a way to do client-side "middleware"?My app uses Firebase Auth for authentication. While the user is logged in, they get an ID token whicHow to refetch a call made on the server```js const section = await api.course.getCourseSection.query({ sectionId: parseInt(params.lessoHow to set cookies in trpc response?I have an app dir project that was created using [this t3-app PR](<https://github.com/t3-oss/create-Check if Role is ADMINHey guys I have a private procedure in `T3 Stack`. I need to check if the user thats doing the actioCan middleware be used on a router?Given a router where all procedures need to use the same middleware, can the middleware be somehow aHow can I use `onSettled` in the `experimental_createTRPCNextAppDirClient`?**Context** I want to migrate the following trpc/client hook to the experimental version ```ts consStop initial refetch when prefetched with SSG helpersAnyone else struggling with this, I want to maintain refetching when the tab is refocused but don't Accessing QueryFunctionContext within server queriesHello, I know that the field 'direction' is a new addition within react query v5 as part of the QueHTTP 431: Input too longHi, we're using a complex query (multiple filters etc) with tRPC and react query integration. It hFunction to release context post-batching?In our application every customer has their own schema, therefore we need a db client per request wh