create-usecase

Generating a new use case in a NestJS clean architecture project involves creating boilerplate for DTOs, a UseCase interface, and module scaffolding. This enforces input validation, dependency injection, and consistent structure across modules.

Clean architecture use case boilerplate requires DTOs for input validation, a UseCase interface, and a minimal module file. It enforces Result/Either error handling and constructor-based dependency injection for production-ready code.

Yes, you can use this scaffolding to expand an existing NestJS module. It applies to module expansion scenarios by generating new business workflow files under the module's application useCases directory, following the existing Order module pattern.

Dependency injection in a generated NestJS use case works via constructor-based injection. The boilerplate enforces proper dependency injection patterns, ensuring the new business workflow aligns with the existing module architecture.

Generated use case files are placed under src/modules/{module-name}/application/useCases/{usecase-name}/ directory. This standardized path ensures new business workflows align with the existing NestJS clean architecture module organization.