practical-api-guidelines
practical-api-guidelines copied to clipboard
Practical guidelines for building & designing APIs with .NET.
Secure the API access + Apikey + Ip Filtering + Certificate + OAuth token (from IDP) + MSI (managed identity) + ...
When building the project in release mode, the integration tests are failing because no connection could be made to the database.
Shouldn't we let ASP.NET handle the serialization of the error in the format that is specified by the accept header of the request instead of deciding for ourselves that it...
With respect to my comments in [issue 103](https://github.com/CoditEU/practical-api-guidelines/issues/103) We should add support for xml formatting by doing the following: -add the XML formatter (install the nuget package and add it...
You should have a repository per aggregate root, and not one global repository. I think in this domain model, we currently have only one aggregate root, which would be `Car`...
Provide support for PATCH application/merge-patch+json
Migrate exception handler to Arcus approach - https://github.com/arcus-azure/arcus.webapi/issues/14