Endpoint name metadata should be set automatically to the method name when Map
overload is called passing a MethodGroup
#34540
Labels
area-minimal
Includes minimal APIs, endpoint filters, parameter binding, request delegate generator etc
feature-minimal-actions
Controller-like actions for endpoint routing
old-area-web-frameworks-do-not-use
*DEPRECATED* This label is deprecated in favor of the area-mvc and area-minimal labels
Priority:1
Work that is critical for the release, but we could probably ship without
Milestone
Endpoint names are used to lookup endpoints when generating links using
LinkGenerator
, and as their unique per application are a good candidate for using as theoperationId
for an endpoint in OpenAPI (Swagger) documents.(domaindrivendev/Swashbuckle.AspNetCore#2165 is tracking setting the operationId from endpoint name by default in Swashbuckle.)
Endpoint names are set using the Microsoft.AspNetCore.Routing.IEndpointNameMetadata interface. In the framework today this can be set imperatively by adding an instance of Microsoft.AspNetCore.Routing.EndpointNameMetadata to the endpoint's metadata, e.g. builder.WithMetadata(new EndpointNameMetadata("GetTodoById")). Issues #34538 and #34539 are tracking providing further ways to define endpoint names manually.
In minimal APIs we should automatically set the endpoint name to the value of
MethodInfo.Name
when the endpoint is defined using aMethodGroup
rather than a lambda or anonymous delegate, e.g.:The text was updated successfully, but these errors were encountered: