wasp-operations

Type-safe backend operations in Wasp require explicit type annotations for `context.entities` access and proper TypeScript setup in your operations.ts file. This prevents runtime errors and ensures the compiler catches type mismatches before deployment, making queries and actions reliable and predictable.

Authentication checks must be the first step in every backend operation. Wasp enforces this pattern through its operation structure, allowing you to validate user identity before accessing protected data or executing privileged operations, preventing unauthorized access at the entry point.

Wasp automatically refetches queries after actions complete, eliminating manual cache invalidation. When an action like `createTask` finishes, dependent queries such as `getTasks` are automatically re-executed on the client, keeping UI state synchronized without extra code.

Yes, Wasp operations support HttpError for structured error handling. This allows you to throw semantic HTTP errors from your backend code, which are automatically serialized and transmitted to the client, enabling consistent error workflows across your application.

Standardized CRUD patterns in Wasp include auth checks as the first step, type-annotated `context.entities` access, HttpError handling, and action-query wiring. These conventions ensure consistency across create, read, update, and delete operations while maintaining security and type safety.

No, Wasp automates the client-server wiring. Define your queries and actions in main.wasp with their corresponding TypeScript implementations, and Wasp generates the necessary API endpoints and client functions, reducing boilerplate and integration overhead.