add-endpoint

To add an API endpoint without a new domain entity, extend the existing vertical slice by updating the Application, Contracts, Controller, Refit client, and ServiceClient layers. This approach modifies current features rather than introducing new database changes.

A test-first workflow for a dotnet API endpoint requires writing tests before implementation, running them through the failure and green cycle, and verifying end-to-end via the BFF or controller path to ensure the new route functions correctly.

Wiring dependency injection for a new GET or POST endpoint involves aligning with established DI patterns and repository interactions within the existing vertical slice to ensure services are correctly resolved and audit or logging conventions are met.

Yes, this approach supports adding both query endpoints like GET and command endpoints like POST, PUT, and DELETE. It spans the Application, Contracts, Controller, Refit client, and ServiceClient to maintain full vertical slice consistency.

You should avoid adding a new API endpoint to an existing feature if your requirements demand a new domain entity or database change, as this workflow is specifically designed to extend current features without altering the underlying domain schema.