DKNet.AspCore.Extensions 10.1.19

DKNet.AspCore.Extensions

The minimal-API glue for DKNet-based ASP.NET Core web APIs: claim-backed request binding, versioned endpoint-group discovery, one-line SlimMessageBus mapping helpers, a shared paging envelope, and FluentResults-to-IResult/ProblemDetails conversion.

Installation

dotnet add package DKNet.AspCore.Extensions

Features

• Contextual request binding — [FromClaim] (and any custom IContextualSource) populates a request property from the authenticated caller before validation and before the handler runs, so it can never be forged through the request body or querystring; automatically excluded from the published OpenAPI description.
• Endpoint group discovery — implement IEndpointConfig per feature area and let UseEndpointConfigs() discover, version, tag, and authorize every group across your assemblies.
• Fluent minimal-API mappers — MapPost/MapPut/MapPatch/MapDelete/MapGet/MapGetPage wire a verb straight onto a SlimMessageBus fluent command/query, plus generic MapGetById/ MapGetList/MapDeleteById backed by DKNet.EfCore.Specifications.
• PagedResponse<T> — a shared paging envelope (PageNumber, PageSize, PageCount, TotalItemCount, Items, HasNextPage, HasPreviousPage) used by every paged endpoint.
• Result/ProblemDetails conversion — Response()/Response<T>() turn a FluentResults outcome into the right minimal-API IResult; ToProblemDetails() does the same for a ModelStateDictionary.

Quick Start

Register the pieces you need and let UseEndpointConfigs do the mapping:

var builder = WebApplication.CreateBuilder(args);

builder.Services.AddAuthorization();
builder.Services.AddApiVersioning();
builder.Services.AddContextualRequestPopulation(); // powers [FromClaim] and friends

var app = builder.Build();
app.UseEndpointConfigs(); // discovers every IEndpointConfig across the loaded assemblies
app.Run();

using System.Security.Claims;
using DKNet.AspCore.Extensions;
using DKNet.AspCore.Extensions.ModelBinding;
using DKNet.SlimBus.Extensions;

public sealed record CreateProductCommand : Fluents.Requests.IWitResponse<ProductModel>
{
    public string Name { get; init; } = string.Empty;

    [FromClaim(ClaimTypes.NameIdentifier)]
    public string? CreatedBy { get; set; } // always resolved from the caller's claim, never from the body
}

public sealed class ProductsEndpointConfig : IEndpointConfig
{
    public string GroupEndpoint => "/products";

    public void Map(RouteGroupBuilder group) =>
        group.MapPost<CreateProductCommand, ProductModel>("/");
}

POST /v1/products now dispatches CreateProductCommand through IMessageBus, resolves CreatedBy from the caller's claim before the handler runs, and returns 201 Created (the mapper infers "Created" from the command's type name) with a FluentResults-derived ProblemDetails body on failure.

MapDeleteById<TEntity> hard-deletes an IEntity<Guid> by id without a command or handler:

group.MapDeleteById<ProductEntity>("/{id}");

DELETE /v1/products/{id} loads the entity via IRepositorySpec, removes it through Delete/SaveChangesAsync (so audit-log and domain-event hooks fire as usual), and returns 204 No Content, 404 when no entity matches, or 409 when a referencing row blocks the removal. Authorization is inherited from the route group the endpoint is registered into — the handler performs no ownership or tenancy check of its own.

Migration — namespace changes in this release

Root types were grouped into concern folders; the namespace of each moved type now ends with its folder name. This is an import-only source break: no type was renamed, removed, resignatured, or had its behaviour changed — update the using line and you're done.

IEndpointConfig — the package's entry surface — stays at DKNet.AspCore.Extensions.

Customisation reference

Two options types, plus the type parameters and attributes that make up the rest of the public surface. Defaults are the ones the code applies when you pass nothing.

ContextualPopulationOptions — AddContextualRequestPopulation(Action<ContextualPopulationOptions>?):

EndpointRegistrationOptions — app.UseEndpointConfigs(Action<EndpointRegistrationOptions>?, params Assembly[]):

IEndpointConfig — what each implementation supplies:

ListQueryRequest — the query string every MapGetList endpoint accepts:

Only fields the returned model declares can be filtered, searched or sorted; anything else is rejected with 400 rather than silently ignored.

Attributes and other extension points:

Full Documentation

See the full feature guide for contextual-source resolvers, EndpointRegistrationOptions, all fluent mappers, paging details, and gotchas.

License

MIT — see LICENSE.

About

Developed by Steven Hoang.