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?
4 Replies
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
