add-feature

To add a new API endpoint to an existing dotnet vertical slice module, you scaffold the contracts, handler, validator, and endpoint wiring. This ensures correct layering by placing command or query types in the Contracts project and runtime code in the Features area.

Structuring a Mediator command or query in vertical slice architecture involves defining ICommand or IQuery types in a Contracts project. The runtime handler injects the module DbContext directly without repositories, ensuring business operations remain decoupled and consistent.

Yes, a validator and idempotency configuration are required when creating an API operation in dotnet. The vertical slice feature requires a validator for production readiness, and the endpoint mapping must include permissions and idempotency conventions mapped to the correct route.

DbContext injection works by having the runtime feature handler directly inject the module DbContext. This approach eliminates the need for separate repositories, allowing the handler to perform data access directly while maintaining the vertical slice module conventions.

This scaffolding approach requires existing dotnet modules that already follow specific module conventions. It applies specifically to the FullStackHero architecture, ensuring the new feature integrates with the established permissions model and MapEndpoints group wiring.

Feature handlers fail to map correctly when they are not integrated into the module's MapEndpoints group. Correct endpoint wiring requires mapping the route with the appropriate permissions and idempotency settings to align with the module's established conventions.