Wolverine.HTTP: [AsParameters] query binder silently ignores unparseable values instead of returning 400 #3372

What happens

When an [AsParameters] query model has a non-nullable enum (or any value-typed) property with a default initializer, Wolverine's generated query-string binder silently ignores an unparseable value and leaves the property at its initializer. The request then succeeds with the default semantics instead of being rejected.

ASP.NET Core's own minimal-API [AsParameters] binder returns 400 Bad Request for the same input, so the behaviour differs from the framework the attribute is borrowed from.

The practical consequence is that a typo'd query value is indistinguishable from an absent one, so there is no way to reject it — not even downstream. A FluentValidation IsInEnum() rule can't catch it either: the binder never writes an out-of-range value (such as 0) that the validator could see, it just doesn't assign at all.

Repro

using Wolverine;
using Wolverine.Http;

var builder = WebApplication.CreateBuilder(args);
builder.Host.UseWolverine();
var app = builder.Build();
app.MapWolverineEndpoints();
await app.RunAsync();

public enum SortField { Name = 1, Date = 2 }

public sealed record SearchQuery
{
    [FromQuery(Name = "sort-by")]
    public SortField SortBy { get; set; } = SortField.Date;
}

public static class SearchEndpoint
{
    [WolverineGet("/search")]
    public static string Get([AsParameters] SearchQuery query) => query.SortBy.ToString();
}

The same holds for int / long / Guid properties: ?page-size=abc binds to the initializer rather than failing.

Expected

An unparseable value for a bound query parameter should be reportable. Any of these would resolve it:

1. return 400 on a failed parse, matching ASP.NET Core's [AsParameters] binder;
2. make it opt-in (e.g. a WolverineHttpOptions flag) so existing lenient behaviour is preserved by default;
3. at minimum, record the failure somewhere an endpoint or middleware can observe (e.g. as a binding-problem collection on the HttpContext), so a policy can turn it into a 400.

Environment

• WolverineFx.Http 6.17.0
• .NET 10