新增功能 API Skill

To scaffold a complete CRUD module with admin and API routes, use a guided workflow that generates controllers, services, conditions, DTOs, entities, and mappers for both routing paths. This ensures consistent separation of concerns across backend layers.

The best way to generate backend CRUD layers without using PageHelper is to apply a scaffolding process that enforces project-convention constraints. This generates standard controllers, services, and DTOs while strictly avoiding PageHelper for optional query conditions.

Yes, you can generate request and response DTOs for separate admin and api controllers. The scaffolding process provides clear separation of concerns by creating distinct admin and api controllers alongside their corresponding req/res DTOs and service interfaces.

Cross-layer consistency works by organizing generated components like controllers, services, conditions, and entities into a standard layered structure. This enforces consistent naming and optional query conditions across both admin and api paths during backend development.

The main limitation of scaffolding CRUD features is that it enforces strict project-convention constraints, such as avoiding PageHelper usage entirely. Additionally, the generated module structure is rigidly organized into standard layers, requiring adherence to the specific admin and api routing separation.

You do not need an existing schema to start scaffolding CRUD components and mappers. You can create a module from zero, which includes generating the DB schema, query conditions, and REST endpoints alongside the entity and mapper files.