trpc mutations for fetching 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?
1 Reply
Josh
Josh8mo ago
I don't really agree with this especially in the world of trpc I have an infinite query on my site that requires a useMutation in order for it to work properly and it's fine It's just the difference of if you want to automatically fetch your data vs manually trigger it
Want results from more Discord servers?
Add your server
More Posts
Making all my components 'use client' while maintaining protectedProceduresHi. I'm using the full T3 stack with prisma, next auth, and nextjs with the app router. I want to siServer Component Data RevalidationHi all, searched and did not find a discussion on this yet but new here so apologies if I overlookedPrettier hangs when using with tailwind pluginFirst I've noticed it in VSCode, than tried via CLI - the same error. Without plugin everything worknext dont build in github ciHey guys I started building an app with the t3 stack a few days ago, and now I wanted to write a Gitcreate t3 app @ latest mutation result not mappableIve made sample t3 app with the latest build just to create a trpc router that helps me reach an extGraphQl and NextJS 13+ for multiple, concurrent/parallel DB queries?I know this could be a problem with architecture/design, but how would you most efficiently query (rLinks within one another (nextjs)Hey, having a problem with having link buttons within each other. When I try to give the bottom buttServer component rendered by client component as children prop throwing errori'm trying to fetch some data from a server component (`StatusImages`) that is being rendered as theEnhancing Performance with Pre-fetching Paginated Queries in tRPCHello, I'm currently focused on boosting the performance of a website that incorporates tRPC. Our sSession is null inside of a server action when calling it from the uploadthing router/api/uploadthing/core.ts ```ts articleCoverUploader: f({ image: { maxFileCount: 1, maxFileSize