backend-tech-stack

Troubleshoot GraphQL API requests by checking Apollo Server and Pothos schema definitions first. If the error involves data fetching, inspect TypeORM datasource configurations to see if the database query failed before reaching the GraphQL resolver layer.

Class-validator rejects API payloads when validation decorators are missing or mismatched with your TypeScript types. Ensure your input objects use class-transformer to properly instantiate the validation classes before the data hits your business logic.

Diagnose CASL permission issues by verifying your authorization rules match the user roles defined in your backend app. Check if the CASL ability definitions are correctly injected into the workflow execution context to enforce accurate access control.

Debug TypeORM database access errors by examining your entity mappings and datasource configuration. Review the generated SQL queries in your logging output to identify if the issue stems from an invalid schema relationship or a failed transaction.

Backend workflow execution can fail despite correct API inputs if DBOS workflow state is corrupted or if Winston logging configurations mask internal errors. Trace the workflow execution path to pinpoint where the transaction fails outside the API validation layer.

Set up Jest and Faker for testing GraphQL resolvers by mocking your TypeORM datasource and generating fake payload objects with Faker. Ensure your Jest configuration correctly compiles TypeScript and resolves Apollo Server context dependencies before executing tests.