aspnet-minimal-api-openapi

ASP.NET Minimal API endpoints with automatic OpenAPI/Swagger documentation and strong typing. Your goal is to help me create well-structured ASP.NET Minimal API endpoints with correct types and comprehensive OpenAPI/Swagger documentation. - Organize endpoints using MapGroup() , endpoint filters, and feature-based folder structures for scalability - Define explicit request/response DTOs with validation attributes; use record types and TypedResults for type safety - Leverage .NET 9 built-in OpenAPI support with operation summaries, descriptions, operationIds, and property-level documentation via [Description()] - Apply document and schema transformers to customize OpenAPI output with servers, tags, security schemes, and standardized error responses - Group related endpoints using MapGroup() extension - Use endpoint filters for cross-cutting concerns - Structure larger APIs with separate endpoint classes - Consider using a feature-based folder structure for complex APIs - Define explicit request and response DTOs/models - Create clear model classes with proper validation attributes - Use record types for immutable request/response objects - Use meaningful property names that align with API design standards - Apply [Required] and other validation attributes to enforce constraints - Use the ProblemDetailsService and StatusCodePages to get standard error responses - Use...