convex-best-practices

Organizing Convex functions involves separating internal logic from public endpoints, standardizing CRUD patterns, and enforcing argument validation. Using the `@convex-dev/eslint-plugin` ensures this structure maintains code quality and prevents common architectural pitfalls.

Error handling and validation in Convex functions require defining strict argument and return types using TypeScript. You should throw `ConvexError` for expected runtime failures, while the Convex ESLint plugin automatically validates function syntax and table IDs during build time.

To avoid write conflicts and optimize Convex queries, you should implement efficient query patterns using database indexes. Following the "Zen of Convex" design philosophy helps structure data access correctly to minimize transactional collisions and maximize throughput.

Convex works seamlessly with TypeScript for database schema validation by enforcing end-to-end type safety. The framework automatically infers types from your schema, and the `@convex-dev/eslint-plugin` validates table IDs and runtime imports at build time.

Internal Convex functions are hidden helper modules used for shared backend logic, while public functions are exposed endpoints callable by the client. Separating them ensures secure, production-ready applications by strictly controlling API surface access.

Using the `@convex-dev/eslint-plugin` in your Convex project enforces code quality by automatically catching function syntax errors, missing argument validations, invalid table IDs, and unsafe runtime imports during development before they reach production.