Create an include (something like https://github.com/dotnet/AspNetCore.Docs/blob/master/aspnetcore/includes/reservedRouting.md

With the info from https://github.com/dotnet/aspnetcore/wiki/MVC-Reserved-Keywords on routing. Be stronger, something like

These keywords should not be used for link generations, as model bound parameters, or top level properties.

Add the include to the 3

I know it's not a course about RESTful principles but maybe you'll consider in the future extracting resource id from request body to path parameter ?

https://github.com/aspnetrun/run-aspnetcore-microservices/blob/c30712aa099bc335f5613a3b196ea1e943f800a5/src/Services/Catalog/Catalog.API/Controllers/CatalogController.cs#L85

We should have a test that validates each service can actually be resolved from the container (within a scope). See #339 for motivation. It would be fantastic if this could be done via reflection and not manually adding a new test every time you register a new service. I'm thinking we would define a static member that contained all the ServiceDescriptors. Then in the test we just get this member