trpc-query-procedure-used-for-side-effecting-writes
tRPC query procedures must be idempotent reads; using a query for reminder notification dispatch (checkDueTomorrow writing notification rows) violates the GET/query contract and means reminders only fire when a client manually calls the endpoint. Side-effecting notification delivery must be placed in a mutation procedure with a dedicated server-side cron trigger — never inside a query.
Related
- trpc-query-writing-side-effects-breaks-idempotency
- trpc-query-procedure-must-not-perform-writes
- trpc-query-procedure-used-as-mutation-violates-contract
- trpc-query-procedures-must-be-idempotent-reads-only
- trpc-query-used-for-write-ops-breaks-reminder-delivery
- trpc-query-writing-data-breaks-cron-and-idempotency
- trpc-query-that-mutates-violates-idempotency-contract
- trpc-query-with-write-side-effects-breaks-idempotency
- trpc-query-used-for-write-violates-idempotency-contract
- trpc-query-used-for-write-violates-idempotency
- trpc-query-procedure-with-write-side-effects-breaks-reminder
- trpc-query-with-side-effects-breaks-idempotency
- trpc-query-that-writes-silent-reminder-anti-pattern
- trpc-query-used-for-writes-breaks-reminder-delivery
- trpc-query-used-for-write-operations-breaks-idempotency-cont
- trpc-query-that-mutates-state-antipattern