dto-response

To generate DTOs and Response classes for a NestJS API, you define request data structures with class-validator and format structured output payloads using class-transformer's @Expose decorator. This approach ensures your API development adheres to established naming conventions like CreateEntityDto.

The best way to structure input validation for TypeScript request DTOs is using class-validator decorators within your Data Transfer Object classes. This method validates incoming request data structures systematically before processing, ensuring type safety and data integrity in your application.

To format API response payloads using class-transformer in TypeScript, you apply the @Expose decorator to define specific output properties within Response classes. This creates structured response formatting that strictly controls what data is serialized and returned to the client.

Yes, this DTO generation skill follows established naming conventions for API responses by generating classes with specific suffixes like FindEntityRes for output payloads and CreateEntityDto for inputs. These patterns ensure consistency across your NestJS application's file structure.

Yes, you can use this skill to create both input and output data structures for a new API endpoint. It generates request DTOs with validation rules using class-validator alongside structured response payloads with class-transformer, handling both sides of your API data transfer.