TDT Dinivibe.hashnode.dev·18h ago · 6 min readFive Prisma Guard Mistakes That Still Return 200 OKErrors are easier to debug than successful requests with wrong semantics. A response can be 200 while the guard discarded client input, moved a condition, returned a wider mutation record, left a nest00
TDT Dinivibe.hashnode.dev·18h ago · 7 min readFix prisma-guard Errors by Finding the Failing StepSearching a long prisma-guard error verbatim often hides the useful clue: when did it fail? Router descriptors, shape construction, caller routing, request validation, scope policy, and HTTP transport00
TDT Dinivibe.hashnode.dev·18h ago · 6 min readBuild Safer Create, Update, and Bulk Routes with PrismaGenerated write routes save handler code, but they do not make every Prisma mutation safe to expose. Write safety comes from complete data shapes, constrained selectors, explicit bulk filters, control00
TDT Dinivibe.hashnode.dev·18h ago · 6 min readThree Ways to Return Large Prisma Results: Pages, POST Queries, and StreamingLarge read endpoints fail for different reasons. Some need stable page metadata. Some exceed practical URL limits. Some return a small root record quickly but need more time for relation-heavy fields.00
TDT Dinivibe.hashnode.dev·18h ago · 6 min readControl What Your Prisma API Returns with `select`A correct tenant filter answers which records may qualify. It does not answer which fields and related records may leave the server. In a generated Prisma API, projection needs its own contract becaus00
