Need expanded coverage of endpointing routing changes to 3.0 - how they work, how they differ from 2.1 and previous routing.
currently have
An endpoint defines a delegate to process requests and a collection of arbitrary metadata. The metadata is used to implement cross-cutting concerns based on policies and configuration attached to each endpoint.
Add to that
For example, an Authorization Middleware can interrogate the endpoint's metadata collection for an [authorization policy](xref:security/authorization/policies#applying-policies-to-mvc-controllers).
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
Especially important as https://docs.microsoft.com/en-us/aspnet/core/migration/22-to-30?view=aspnetcore-3.0&tabs=visual-studio#routing-startup-code is pointing at this documentation for how to go from 2.2 to 3.0 :)
For someone who really only needs default routing, this was the most troublesome part of migrating my project from 2.2 to 3.0. It would be convenient if we had a more basic example starting from a default route and then adding in middleware/authorization for those out of the loop like myself.
Im not sure where the section ends> "Endpoint routing differences from earlier versions of routing"
From the standpoint of someone learning routing from scratch this section probably just confuses the subject. Do i skip this section?
well endpoint routing seems to be the new thing that should be used for all routing, but most examples are for 2.2 and earlier, mvc documentation still uses UsemVC etc etc. confusing