rule-api-routes

To enforce consistent API route patterns, apply standardized file structures like domain_blueprint.py, domain_routes.py, and domain_schema.py. This ensures route handlers follow mandated decorator stack order, authentication, error handling, and logging practices.

The mandated file structure for API domain routes requires three files per domain: domain_blueprint.py, domain_routes.py, and domain_schema.py. This convention enforces standardized routing patterns, schema validation, and shared utilities for logging and error handling.

Standardize decorator order and authentication by applying mandated decorator stack sequences to thin route handlers. This minimizes business logic in routes and enforces explicit doc and auth patterns across all endpoints for consistent security.

API route handlers should be thin to minimize business logic in routes, ensuring standardized processing. Thin handlers enforce explicit doc and auth patterns, consistent error handling, and shared logging utilities across all API endpoints.

Yes, this approach enforces soft delete practices in API routes by codifying routing patterns and security practices. It standardizes endpoint implementations through explicit decorator order, shared utilities, and consistent error handling across the codebase.

The best way to standardize error handling and logging in API endpoints is using shared utilities within a mandated domain file structure. This codifies routing patterns to ensure consistent, safe, and scalable endpoint implementations across the codebase.