You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* - seperate lifetime configuration setting for endpoints and route group configurators
* - **breaking change** major overhaul of configuration and registration
* - continue configuration overhaul
* - add set accessor to ConfigurationPropertyBag
* - refactor service provider name in configuration context
* - code cleanup
* - rename various classes because naming things is hard
* - move configuration override func parameters out of settings
* - configurator interfaces no longer implement corresponding configuration setting interfaces
- remove configuratoion setting interfaces and replace with configuration parameter classes
* - prune unused code
* - prune unused code
* - replace abstract override configuration properties with methods in both endpoint and route group configurators
* - update docs
* - update docs
* - rename OverrideConfiguration methods to PostConfigure
* - bump version
Copy file name to clipboardExpand all lines: README.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,7 +53,7 @@
53
53
54
54
Each endpoint must implement two virtual methods:
55
55
56
-
1.**Configure**: Invoked during application startup to define the route and HTTP method for an endpoint. It begins with methods like `MapGet`, `MapPost`, etc., to specify the route pattern. The returned `RouteHandlerBuilder` from the Map[HttpVerb] method can then be used for further endpoint customization.
56
+
1.**Configure**: Invoked during application startup to define the route and HTTP method for an endpoint. It begins with calling input parameter `builder`'s methods like `MapGet`, `MapPost`, etc., to specify the route pattern. The returned `RouteHandlerBuilder` from the Map[HttpVerb] method can then be used for further endpoint customization.
57
57
58
58
2.**HandleAsync**: Contains the logic to handle incoming requests. Called after the request is validated (if applicable).
Copy file name to clipboardExpand all lines: docs/RouteGroups.md
+12-12Lines changed: 12 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@
3
3
By default, all endpoints are mapped under root route group. It is possible to define route groups similar to using 'MapGroup' extension method used to map Minimal APIs under a group. Since endpoints are configured by endpoint basis in the 'Configure' method of each endpoint, the approach is a little different than configuring a Minimal API. But route group configuration still utilize Minimal API route groups and can be decorated by any extension method of RouteGroupBuilder. Route groups are also subject to auto discovery and registration, similar to endpoints.
4
4
5
5
-[Create a route group implementation](../samples/ShowcaseWebApi/Features/FeaturesRouteGroup.cs) by inheriting RouteGroupConfigurator and implementing 'Configure' method,
6
-
- Configuration of each route group implementation starts with calling MapGroup method with a route pattern prefix. The return of 'MapGroup' method, a RouteGroupBuilder instance, can be used to further customize the route group like any Minimal API route group.
6
+
- Configuration of each route group implementation starts with calling input parameter `builder`'s MapGroup method with a route pattern prefix. The return of 'MapGroup' method, a RouteGroupBuilder instance, can be used to further customize the route group like any Minimal API route group.
7
7
- Apply MapToGroup attribute to either other [route group](../samples/ShowcaseWebApi/Features/Books/Configuration/BooksV1RouteGroup.cs) or [endpoint](../samples/ShowcaseWebApi/Features/Books/CreateBook.cs) classes that will be mapped under created route group. Use type of the new route group implementation as GroupType parameter to the attribute.
8
8
9
9
Following sample creates a parent route group (FeaturesRouteGroup), a child route group under it (BooksV1RouteGroup) and maps an endpoint (CreateBook) to child route group. Group configuration methods used for this particular sample are all part of Minimal APIs ecosystem and are under [Asp.Versioning](https://github.com/dotnet/aspnet-api-versioning).
@@ -12,27 +12,27 @@ Following sample creates a parent route group (FeaturesRouteGroup), a child rout
0 commit comments