trpc-query-procedure-must-not-perform-writes

tRPC query procedures map to HTTP GET and must be idempotent reads. Using a query to write side-effects (e.g., a reminders.checkDueTomorrow query that creates notification rows) violates the GET contract, breaks caching assumptions, and means the write only fires when a client manually calls the endpoint. Background writes must be mutations triggered by cron jobs, not queries.

Related

• trpc-query-used-for-write-ops-breaks-reminder-delivery
• trpc-query-procedures-must-be-idempotent-reads-only
• trpc-query-must-not-write-side-effects
• trpc-query-used-for-writes-contract-violation
• trpc-query-must-not-write-data
• trpc-query-procedure-used-as-mutation-violates-contract
• trpc-query-writing-side-effects-breaks-idempotency
• trpc-query-used-for-side-effectful-reminder-writes
• trpc-query-used-for-side-effects-reminder-anti-pattern
• trpc-query-procedure-used-for-side-effecting-writes
• trpc-query-writing-data-breaks-cron-and-idempotency
• trpc-query-used-for-write-violates-idempotency-contract
• trpc-query-used-for-write-violates-idempotency
• trpc-query-that-writes-silent-reminder-anti-pattern
• trpc-query-used-for-write-operations-breaks-idempotency-cont
• trpc-query-that-mutates-state-antipattern