HandlerCategory renamed to HandlerEndpointGroup

Author: ejsmith

docs/guide/clean-architecture.md

@@ -66,7 +66,7 @@ The mediator pattern is the perfect complement to Clean Architecture because it
 With Foundatio Mediator's source generator, you can **eliminate the presentation layer boilerplate entirely**. HTTP endpoints are automatically generated from your handlers:
 
 ```csharp
-[HandlerCategory("Orders", RoutePrefix = "/api/orders")]
+[HandlerEndpointGroup("Orders", RoutePrefix = "/api/orders")]
 public class OrderHandler
 {
     /// <summary>
@@ -388,7 +388,7 @@ public class OrdersController : ControllerBase
 }
 
 // Foundatio Mediator - handlers ARE the API
-[HandlerCategory("Orders", RoutePrefix = "/api/orders")]
+[HandlerEndpointGroup("Orders", RoutePrefix = "/api/orders")]
 public class OrderHandler
 {
     public async Task<Result<Order>> HandleAsync(CreateOrder cmd, IOrderRepository repo, CancellationToken ct)

docs/guide/configuration.md

@@ -170,14 +170,14 @@ The following properties on `MediatorConfigurationAttribute` control endpoint ge
 - **Default:** `All`
 - **Effect:** Controls which handlers generate API endpoints
   - `All`: All handlers with endpoint-compatible message types generate endpoints (default). Use `[HandlerEndpoint(Exclude = true)]` to opt out individual handlers.
-  - `Explicit`: Only handlers with `[HandlerEndpoint]` or `[HandlerCategory]` attribute generate endpoints
+  - `Explicit`: Only handlers with `[HandlerEndpoint]` or `[HandlerEndpointGroup]` attribute generate endpoints
   - `None`: No endpoints generated
 - **See:** [Endpoints Guide](/guide/endpoints) for full documentation
 
 **`EndpointRoutePrefix`** (`string?`)
 
 - **Default:** `"api"`
-- **Effect:** Sets a global route prefix that all category groups nest under. Categories auto-derive their route from their name (e.g., `[HandlerCategory("Products")]` → `products`), composing with the global prefix to produce `/api/products`.
+- **Effect:** Sets a global route prefix that all category groups nest under. Categories auto-derive their route from their name (e.g., `[HandlerEndpointGroup("Products")]` → `products`), composing with the global prefix to produce `/api/products`.
 - **Important:** Category-level `RoutePrefix` values without a leading `/` are **relative** to this global prefix. Don't include `api` in your category prefixes when using the default global prefix, or you'll get `/api/api/...`. Use a leading `/` on a category prefix to make it absolute (bypasses the global prefix).
 - **To disable:** Set `EndpointRoutePrefix = ""` to remove the global prefix entirely, then use full paths in category prefixes.
 

docs/guide/endpoints.md

@@ -370,7 +370,7 @@ public class LoggingMiddleware
 | `FMED011` | Error | Multiple Execute methods in a middleware class. Only one Execute/ExecuteAsync method is allowed per middleware class. |
 | `FMED012` | Warning | Circular ordering dependency detected between middleware or handlers using `OrderBefore`/`OrderAfter`. Falls back to numeric `Order`. |
 | `FMED014` | Warning | GET/DELETE endpoint message type has no parameterless constructor and no route/query parameters. |
-| `FMED015` | Warning | `HandlerCategory` `RoutePrefix` starts with the global `EndpointRoutePrefix`, producing a doubled path (e.g. `/api/api/...`). |
+| `FMED015` | Warning | `HandlerEndpointGroup` `RoutePrefix` starts with the global `EndpointRoutePrefix`, producing a doubled path (e.g. `/api/api/...`). |
 
 ## Getting Help
 

docs/guide/troubleshooting.md

@@ -17,7 +17,7 @@ namespace Common.Module.Filters;
 /// Wire this filter at any level of the three-tier hierarchy:
 /// <list type="bullet">
 ///   <item><description>Global: <c>[assembly: MediatorConfiguration(EndpointFilters = [typeof(SetRequestedByFilter)])]</c></description></item>
-///   <item><description>Category: <c>[HandlerCategory("Orders", EndpointFilters = [typeof(SetRequestedByFilter)])]</c></description></item>
+///   <item><description>Group: <c>[HandlerEndpointGroup("Orders", EndpointFilters = [typeof(SetRequestedByFilter)])]</c></description></item>
 ///   <item><description>Endpoint: <c>[HandlerEndpoint(EndpointFilters = [typeof(SetRequestedByFilter)])]</c></description></item>
 /// </list>
 /// </summary>

samples/CleanArchitectureSample/src/Common.Module/Filters/SetRequestedByFilter.cs

@@ -12,7 +12,7 @@ namespace Common.Module.Handlers;
 /// monitors, and readiness probes.
 /// </summary>
 [HandlerAllowAnonymous]
-[HandlerCategory("Health")]
+[HandlerEndpointGroup("Health")]
 public class HealthHandler
 {
     public HealthStatusResponse Handle(GetHealthStatus query) =>

samples/CleanArchitectureSample/src/Common.Module/Handlers/HealthHandler.cs

@@ -15,7 +15,7 @@ namespace Orders.Module.Handlers;
 /// Following Clean Architecture, this handler orchestrates use cases
 /// and delegates persistence to the IOrderRepository abstraction.
 /// </summary>
-[HandlerCategory("Orders", EndpointFilters = [typeof(SetRequestedByFilter)])]
+[HandlerEndpointGroup("Orders", EndpointFilters = [typeof(SetRequestedByFilter)])]
 public class OrderHandler(IOrderRepository repository)
 {
     /// <summary>

samples/CleanArchitectureSample/src/Orders.Module/Handlers/OrderHandler.cs

@@ -14,7 +14,7 @@ namespace Products.Module.Handlers;
 /// Following Clean Architecture, this handler orchestrates use cases
 /// and delegates persistence to the IProductRepository abstraction.
 /// </summary>
-[HandlerCategory("Products")]
+[HandlerEndpointGroup("Products")]
 public class ProductHandler(IProductRepository repository)
 {
     /// <summary>

samples/CleanArchitectureSample/src/Products.Module/Handlers/ProductHandler.cs

@@ -14,7 +14,7 @@ namespace Reports.Module.Handlers;
 /// - All data is fetched via published queries through the mediator
 /// - Loose coupling enables independent module evolution
 /// </summary>
-[HandlerCategory("Reports")]
+[HandlerEndpointGroup("Reports")]
 public class ReportHandler(IMediator mediator, ILogger<ReportHandler> logger)
 {
     private const int LowStockThreshold = 10;

samples/CleanArchitectureSample/src/Reports.Module/Handlers/ReportHandler.cs

@@ -0,0 +1,38 @@
+namespace Foundatio.Mediator;
+
+/// <summary>
+/// Specifies the HTTP method for a generated endpoint.
+/// </summary>
+public enum EndpointHttpMethod
+{
+    /// <summary>
+    /// The HTTP method is inferred from the message type name prefix
+    /// (e.g., Get* → GET, Create* → POST, Update* → PUT, Delete* → DELETE, Patch* → PATCH).
+    /// </summary>
+    Default = 0,
+
+    /// <summary>
+    /// HTTP GET — used for queries and read operations.
+    /// </summary>
+    Get = 1,
+
+    /// <summary>
+    /// HTTP POST — used for commands that create resources or trigger actions.
+    /// </summary>
+    Post = 2,
+
+    /// <summary>
+    /// HTTP PUT — used for commands that replace or fully update a resource.
+    /// </summary>
+    Put = 3,
+
+    /// <summary>
+    /// HTTP DELETE — used for commands that remove a resource.
+    /// </summary>
+    Delete = 4,
+
+    /// <summary>
+    /// HTTP PATCH — used for commands that partially update a resource.
+    /// </summary>
+    Patch = 5
+}