Repository navigation
Description
Summary
Disclaimer: this document is a joint effort by Safia and Copilot. 😄
This document outlines the design details of a framework-agnostic implementation of complex object validation built on top of the System.ComponentModel validation attributes and APIs.
Motivation and goals
Historically, whenever a framework wants to implement a data validation feature for its data models, it must implement the logic for discovering validatable types, walking the type graph, invoking the validation provider, gathering validation errors, and handling deeply nested or infinitely recursive type structures.
This exercise has been replicated in multiple implementations including MVC's model validation and Blazor's validation experiments. These implementations may have subtle differences in behavior and have to maintain their own implementations of model validation.
The goal of this proposal is to implement a generic layer for for the discovery of validatable types and the implementation of validation logic that can plug in to any consuming framework (minimal APIs, Blazor, etc.)
Proposed API
All APIs proposed below are net-new and reside in the Microsoft.AspNetCore.Http.Abstractions assembly.
Base interface for validation information
// Assembly: Microsoft.AspNetCore.Http.Abstractions
namespace Microsoft.AspNetCore.Http.Validation;
public interface IValidatableInfo
{
ValueTask ValidateAsync(object? value, ValidateContext context, CancellationToken cancellationToken);
}
public abstract class ValidatablePropertyInfo : IValidatableInfo
{
public ValidatablePropertyInfo(
Type declaringType,
Type propertyType,
string name,
string displayName)
protected abstract ValidationAttribute[] GetValidationAttributes();
public virtual ValueTask ValidateAsync(object? value, ValidateContext context, CancellationToken cancellationToken);
}
public abstract class ValidatableParameterInfo : IValidatableInfo
{
public ValidatableParameterInfo(
Type parameterType,
string name,
string displayName)
protected abstract ValidationAttribute[] GetValidationAttributes();
public virtual ValueTask ValidateAsync(object? value, ValidateContext context, CancellationToken cancellationToken);
}
public abstract class ValidatableTypeInfo : IValidatableInfo
{
public ValidatableTypeInfo(
Type type,
IEnumerable<ValidatablePropertyInfo> members)
protected abstract ValidationAttribute[] GetValidationAttributes();
public virtual ValueTask ValidateAsync(object? value, ValidateContext context, CancellationToken cancellationToken);
}Validator discovery and registration
// Assembly: Microsoft.AspNetCore.Http.Abstractions
namespace Microsoft.AspNetCore.Http.Validation;
public interface IValidatableInfoResolver
{
bool TryGetValidatableTypeInfo(Type type, [NotNullWhen(true)] out IValidatableInfo? validatableTypeInfo);
bool TryetValidatableParameterInfo(ParameterInfo parameterInfo, [NotNullWhen(true)] out IValidatableInfo? validatableParameterInfo);
}
public class ValidationOptions
{
public List<IValidatableInfoResolver> Resolvers { get; } = [];
public int MaxDepth { get; set; } = 32;
public bool TryGetValidatableTypeInfo(Type type, [NotNullWhen(true)] out IValidatableInfo? validatableTypeInfo);
public bool TryGetValidatableParameterInfo(ParameterInfo parameterInfo, [NotNullWhen(true)] out IValidatableInfo? validatableParameterInfo);
}
namespace Microsoft.Extensions.DependencyInjection;
public static class ValidationServiceCollectionExtensions
{
public static IServiceCollection AddValidation(this IServiceCollection services,
Action<ValidationOptions>? configureOptions);
}
[AttributeUsage(AttributeTargets.Class)]
public sealed class ValidatableTypeAttribute : Attribute { }Validate-specific Context Object
// Assembly: Microsoft.AspNetCore.Http.Abstractions
namespace Microsoft.AspNetCore.Http.Validation;
public abstract class ValidateContext { }
public sealed class DefaultValidateContext
{
public ValidationContext? ValidationContext { get; set; }
public string Prefix { get; set; }
public int CurrentDepth { get; set; }
public required ValidationOptions ValidationOptions { get; set; }
public Dictionary<string, string[]>? ValidationErrors { get; set; }
}Minimal API-specific Extension Methods
// Assembly: Microsoft.AspNetCore.Routing
namespace Microsoft.AspNetCore.Builder;
public static class ValidationEndpointConventionBuilderExtensions
{
public static TBuilder DisableValidation<TBuilder>(this TBuilder builder)
where TBuilder : IEndpointConventionBuilder
} // Assembly: Microsoft.AspNetCore.Http.Abstractions
namespace Microsoft.AspNetCore.Http.Metadata;
public interface IDisableValidationMetadata { }Usage Examples
The following demonstrates how the API can be consumed to support model validation in minimal APIs via an endpoint filter implementation.
internal static class ValidationEndpointFilterFactory
{
public static EndpointFilterDelegate Create(EndpointFilterFactoryContext context, EndpointFilterDelegate next)
{
var parameters = context.MethodInfo.GetParameters();
var options = context.ApplicationServices.GetService<IOptions<ValidationOptions>>()?.Value;
if (options is null)
{
return next;
}
var validatableParameters = parameters
.Select(p => options.TryGetValidatableParameterInfo(p, out var validatableParameter) ? validatableParameter : null);
var ValidateContext = new DefaultValidateContext { ValidationOptions = options };
return async (context) =>
{
ValidateContext.ValidationErrors?.Clear();
for (var i = 0; i < context.Arguments.Count; i++)
{
var validatableParameter = validatableParameters.ElementAt(i);
var argument = context.Arguments[i];
if (argument is null || validatableParameter is null)
{
continue;
}
var validationContext = new ValidationContext(argument, context.HttpContext.RequestServices, items: null);
ValidateContext.ValidationContext = validationContext;
await validatableParameter.Validate(argument, ValidateContext);
}
if (ValidateContext.ValidationErrors is { Count: > 0 })
{
context.HttpContext.Response.StatusCode = StatusCodes.Status400BadRequest;
context.HttpContext.Response.ContentType = "application/problem+json";
return await ValueTask.FromResult(new HttpValidationProblemDetails(ValidateContext.ValidationErrors));
}
return await next(context);
};
}
}The following demonstrates how the API can be used to enable validation, alongside the validations source generator for a minimal API and highlights the types of validatable arguments that are supported by the generator.
// Example of using validation with source generator in a minimal API
var builder = WebApplication.CreateBuilder(args);
builder.Services.AddValidation();
var app = builder.Build();
// ValidationEndpointFilterFactory is implicitly enabled on all endpoints
app.MapGet("/customers/{id}", ([Range(1, int.MaxValue)] int id) =>
$"Getting customer with ID: {id}");
app.MapPost("/customers", (Customer customer) =>
{
// Validation happens automatically before this code runs
return TypedResults.Created($"/customers/{customer.Name}", customer);
});
app.MapPost("/orders", (Order order) =>
{
// Both attribute validation and IValidatableObject.Validate are called automatically
return TypedResults.Created($"/orders/{order.OrderId}", order);
});
app.MapPost("/products", ([EvenNumberAttribute(ErrorMessage = "Product ID must be even")] int productId,
[Required] string name) =>
{
return TypedResults.Ok(new { productId, name });
})
.DisableValidation();
app.Run();
// Define validatable types with the ValidatableType attribute
[ValidatableType]
public class Customer
{
[Required]
public string Name { get; set; }
[EmailAddress]
public string Email { get; set; }
[Range(18, 120)]
[Display(Name = "Customer Age")]
public int Age { get; set; }
// Complex property with nested validation
public Address HomeAddress { get; set; } = new Address();
}
public class Address
{
[Required]
public string Street { get; set; }
[Required]
public string City { get; set; }
[StringLength(5)]
public string ZipCode { get; set; }
}
// Define a type implementing IValidatableObject for custom validation
[ValidatableType]
public class Order : IValidatableObject
{
[Range(1, int.MaxValue)]
public int OrderId { get; set; }
[Required]
public string ProductName { get; set; }
public int Quantity { get; set; }
// Custom validation logic using IValidatableObject
public IEnumerable<ValidationResult> Validate(ValidationContext validationContext)
{
if (Quantity <= 0)
{
yield return new ValidationResult(
"Quantity must be greater than zero",
[nameof(Quantity)]);
}
}
}
// Use a custom validation attribute
public class EvenNumberAttribute : ValidationAttribute
{
public override bool IsValid(object? value)
{
if (value is int number)
{
return number % 2 == 0;
}
return false;
}
}Implementation Details
Default Validation Behavior of Validatable Type Info
The ValidatableTypeInfo.Validate method follows these steps when validating an object:
-
Null check: If the value being validated is null, it immediately returns without validation unless the type is marked as required.
-
RequiredAttribute handling:
RequiredAttributes are validated before other attributes. If the requiredness check fails, remaining validation attributes are not applied. -
Depth limit check: Before processing nested objects, it checks if the current validation depth exceeds
MaxDepth(default 32) to prevent stack overflows from circular references or extremely deep object graphs. -
Property validation: Iterates through each property defined in
Memberscollection:- Gets the property value from the object
- Applies validation attributes defined on that property
- For nullable properties, skips validation if the value is null (unless marked required)
- Handles collections by validating each item in the collection if the property is enumerable
-
IValidatableObject support: If the type implements
IValidatableObject, it calls theValidatemethod after validating individual properties, collecting any additional validation results. -
Error aggregation: Validation errors are added to the
ValidationErrorsdictionary in the context with property names as keys (prefixed if nested) and error messages as values. -
Recursive validation: For properties with complex types that have their own validation requirements, it recursively validates those objects with an updated context prefix to maintain the property path.
Validation Error Handling
Validation errors are collected in a Dictionary<string, string[]> where:
- Keys are property names (including paths for nested properties like
Customer.HomeAddress.Street) - Values are arrays of error messages for each property
This format is compatible with ASP.NET Core's ValidationProblemDetails for consistent error responses.
Parameter Validation
The ValidatableParameterInfo class provides similar validation for method parameters:
- Validates attributes applied directly to parameters
- For complex types, delegates to the appropriate
ValidatableTypeInfo - Supports special handling for common parameter types (primitives, strings, collections)
The validation endpoint filter demonstrates integration with minimal APIs, automatically validating all parameters before the endpoint handler executes.
Source Generation
The validation system leverages a source generator to:
- Analyze types marked with
[ValidatableType]at build time - Analyze minimal API endpoints at build-time to automatically discover validatable types without an attribute
- Generate concrete implementations of
ValidatableTypeInfoandValidatablePropertyInfo - Intercept the
AddValidationcall in user code and add the generatedIValidatableInfoResolverto the list of resolvers available in theValidationOptions - Pre-compiles and caches instances of ValidationAttributes uniquely hashed by their type and initialization arguments
The source generator creates a specialized IValidatableInfoResolver implementation that can handle all your validatable types and parameters without runtime reflection overhead.
file class GeneratedValidatableInfoResolver : IValidatableInfoResolver
{
public ValidatableTypeInfo? GetValidatableTypeInfo(Type type)
{
// Fast type lookups with no reflection
if (type == typeof(Customer))
{
return CreateCustomerType();
}
if (type == typeof(Address))
{
return CreateAddressType();
}
// Other types...
return null;
}
public ValidatableParameterInfo? GetValidatableParameterInfo(ParameterInfo parameterInfo)
{
// ParameterInfo-based validations are resolved at runtime
return null;
}
// Pre-generated factory methods for each type
private ValidatableTypeInfo CreateCustomerType()
{
return new GeneratedValidatableTypeInfo(
type: typeof(Customer),
members: [
// Pre-compiled property validation info
new GeneratedValidatablePropertyInfo(
containingType: typeof(Customer),
propertyType: typeof(string),
name: "Name",
displayName: "Name",
isEnumerable: false,
isNullable: false,
isRequired: true,
hasValidatableType: false,
validationAttributes: [
// Pre-created validation attributes
ValidationAttributeCache.GetOrCreateValidationAttribute(
typeof(RequiredAttribute),
Array.Empty<string>(),
new Dictionary<string, string>())
]),
// Other properties...
],
implementsIValidatableObject: false);
}
// Other factory methods...
}The generator emits a ValidationAttributeCache to support compiling and caching ValidationAttributes by their type and arguments.
// Generated ValidationAttribute storage and creation
[GeneratedCode("Microsoft.AspNetCore.Http.ValidationsGenerator", "42.42.42.42")]
file static class ValidationAttributeCache
{
private static readonly ConcurrentDictionary<string, ValidationAttribute?> _cache = new();
public static ValidationAttribute? GetOrCreateValidationAttribute(
Type attributeType,
string[] arguments,
IReadOnlyDictionary<string, string> namedArguments)
{
// Creates validation attributes efficiently with arguments and properties
return _cache.GetOrAdd($"{attributeType.FullName}|{string.Join(",", arguments)}|{string.Join(",", namedArguments.Select(x => $"{x.Key}={x.Value}"))}", _ =>
{
var type = attributeType;
ValidationAttribute? attribute = null;
// Special handling for common attributes with optimization
if (arguments.Length == 0)
{
attribute = type switch
{
Type t when t == typeof(RequiredAttribute) => new RequiredAttribute(),
Type t when t == typeof(EmailAddressAttribute) => new EmailAddressAttribute(),
Type t when t == typeof(PhoneAttribute) => new PhoneAttribute(),
// Other attribute types...
_ => null
};
}
else if (type == typeof(StringLengthAttribute))
{
if (!int.TryParse(arguments[0], out var maxLength))
throw new ArgumentException($"Invalid maxLength value for StringLengthAttribute: {arguments[0]}");
attribute = new StringLengthAttribute(maxLength);
}
else if (type == typeof(RangeAttribute) && arguments.Length == 2)
{
if (int.TryParse(arguments[0], out var min) && int.TryParse(arguments[1], out var max))
attribute = new RangeAttribute(min, max);
else if (double.TryParse(arguments[0], out var dmin) && double.TryParse(arguments[1], out var dmax))
attribute = new RangeAttribute(dmin, dmax);
}
// Other attribute constructors...
// Apply named arguments as properties after construction
foreach (var namedArg in namedArguments)
{
var prop = type.GetProperty(namedArg.Key);
if (prop != null && prop.CanWrite)
{
prop.SetValue(attribute, Convert.ChangeType(namedArg.Value, prop.PropertyType));
}
}
return attribute;
});
}
}The generator also creates strongly-typed implementations of the abstract validation classes:
file sealed class GeneratedValidatablePropertyInfo : ValidatablePropertyInfo
{
private readonly ValidationAttribute[] _validationAttributes;
public GeneratedValidatablePropertyInfo(
Type containingType,
Type propertyType,
string name,
string displayName,
bool isEnumerable,
bool isNullable,
bool isRequired,
bool hasValidatableType,
ValidationAttribute[] validationAttributes)
: base(containingType, propertyType, name, displayName,
isEnumerable, isNullable, isRequired, hasValidatableType)
{
_validationAttributes = validationAttributes;
}
protected override ValidationAttribute[] GetValidationAttributes() => _validationAttributes;
}The generator emits an interceptor to the AddValidation method that injects the generated ITypeInfoResolver into the options object.
file static class GeneratedServiceCollectionExtensions
{
public static IServiceCollection AddValidation(
this IServiceCollection services,
Action<ValidationOptions>? configureOptions)
{
return ValidationServiceCollectionExtensions.AddValidation(services, options =>
{
options.Resolvers.Insert(0, new GeneratedValidatableInfoResolver());
if (configureOptions is not null)
{
configureOptions(options);
}
});
}
}Validation Extensibility
Similar to existing validation options solutions, users can customize the behavior of the validation system by:
- Custom
ValidationAttributeimplementations IValidatableObjectimplementations for complex validation logic
In addition to this, this implementation supports defining vustom validation behavior by defining custom IValidatableInfoResolver implementations and inserting them into the ValidationOptions.Resolvers property.
var builder = WebApplication.CreateBuilder(args);
builder.Services.AddValidation(options =>
{
// Add custom resolver before the generated one to give it higher priority
options.Resolvers.Insert(0, new CustomValidatableInfoResolver());
});
var app = builder.Build();
app.MapPost("/payments", (PaymentInfo payment, [FromQuery] decimal amount) =>
{
// Both payment and amount will be validated using the custom validators
return TypedResults.Ok(new { PaymentAccepted = true });
});
app.Run();
public class PaymentInfo
{
public string CreditCardNumber { get; set; } = string.Empty;
public string CardholderName { get; set; } = string.Empty;
public DateTime ExpirationDate { get; set; }
public string CVV { get; set; } = string.Empty;
}
public class CustomValidatableInfoResolver : IValidatableInfoResolver
{
// Provide validation info for specific types
public ValidatableTypeInfo? GetValidatableTypeInfo(Type type)
{
// Example: Special handling for a specific type
if (type == typeof(PaymentInfo))
{
// Create custom validation rules for PaymentInfo type
return new CustomPaymentInfoTypeInfo();
}
return null; // Return null to let other resolvers handle other types
}
// Provide validation info for parameters
public ValidatableParameterInfo? GetValidatableParameterInfo(ParameterInfo parameterInfo)
{
// Example: Special validation for payment amount parameters
if (parameterInfo.Name == "amount" && parameterInfo.ParameterType == typeof(decimal))
{
return new CustomAmountParameterInfo();
}
return null; // Return null to let other resolvers handle other parameters
}
// Example of custom ValidatableTypeInfo implementation
private class CustomPaymentInfoTypeInfo : ValidatableTypeInfo
{
public CustomPaymentInfoTypeInfo()
: base(typeof(PaymentInfo), CreateValidatableProperties(), implementsIValidatableObject: false)
{
}
private static IEnumerable<ValidatablePropertyInfo> CreateValidatableProperties()
{
// Define custom validation logic for properties
yield return new CustomPropertyInfo(
typeof(PaymentInfo),
typeof(string),
"CreditCardNumber",
"Credit Card Number",
isEnumerable: false,
isNullable: false,
isRequired: true,
hasValidatableType: false);
// Add more properties as needed
}
}
// Example of custom ValidatableParameterInfo implementation
private class CustomAmountParameterInfo : ValidatableParameterInfo
{
private static readonly ValidationAttribute[] _attributes = new ValidationAttribute[]
{
new RangeAttribute(0.01, 10000.00) { ErrorMessage = "Amount must be between $0.01 and $10,000.00" }
};
public CustomAmountParameterInfo()
: base("amount", "Payment Amount", isNullable: false, isRequired: true,
hasValidatableType: false, isEnumerable: false)
{
}
protected override ValidationAttribute[] GetValidationAttributes() => _attributes;
}
// Example of custom property info implementation
private class CustomPropertyInfo : ValidatablePropertyInfo
{
private static readonly ValidationAttribute[] _ccAttributes = new ValidationAttribute[]
{
new CreditCardAttribute(),
new RequiredAttribute(),
new StringLengthAttribute(19) { MinimumLength = 13, ErrorMessage = "Credit card number must be between 13 and 19 digits" }
};
public CustomPropertyInfo(
Type containingType, Type propertyType, string name, string displayName,
bool isEnumerable, bool isNullable, bool isRequired, bool hasValidatableType)
: base(containingType, propertyType, name, displayName,
isEnumerable, isNullable, isRequired, hasValidatableType)
{
}
protected override ValidationAttribute[] GetValidationAttributes() => _ccAttributes;
}
}Open Questions and Future Considerations
- How should this validation system plugin to other validation systems like Blazor? This implementation has been applied to non-minimal APIs scenarios in practice.
- Does the implementation account for all trimming and native AoT compat scenarios? The existing Options validation generator applies custom implementations of built-in ValidationAttributes to support native AoT compt that haven't been accounted for here.
- Should a more robust validation result type be considered? The implementation currently relies on a lazily-initialized Dictionary for this but we can consider something more robust.
Metadata
Metadata
Assignees
Labels
Type
Projects
- StatusShow more project fieldsNo status
Activity
captainsafia commentedon Jun 18, 2024
Hi all --
We originally intended to ship this feature in .NET 9. However, due to shifting priorities and some additional requirements associated with this feature, this work is being punted to a future release.
For the time being, we recommend using packages, like MiniValidation, to add validation support to your minimal APIs. While we work through all the technical details to ship a high-quality feature in a future release, we'd still appreciate your feedback to scope out the shape of the API as needed.
31 remaining items
mrpmorris commentedon Mar 21, 2025
For anything like this.
Would it be possible to use an interface that requires static methods? Otherwise, without the strong typing of the interface, the signature acts like a magic string that could easily be broken by a coder in future so that it doesn't match the required signature and the app will then behave differently without warning.
Having static methods on an interface will also make it easier to use code completion to create the method stub.
jscarle commentedon Mar 23, 2025
This issue touches on a long standing frustration I have with Minimal API custom binding and I'm optimistically hoping that this validation initiative could help improve on that.
To help understand the issue, I'd like to first provide some more context. One of the long standing challenges in software development of any application is ensuring data within your application is validated. This has led to things that we now know as industry standard knowledge, like Domain Drive Design which is at the root of certain architectures like Clean Architecture. These patterns tend to create multiple layers of abstractions that are, in part, a result of limitations at outer layers forcing the use of primitives instead of domain objects. This happens just as much on the external facing layers (such as API requests and responses) as it does on internal layers (such as into and out of databases).
In the .NET ecosystem, this has led to complex DTO mappings and created entire communities around projects such as AutoMapper and Mapperly. Validation has also sprouted the same sort of situation and resulted in such projects as FluentValidation. At the end of the day, there is no good way to strongly type data on Minimal APIs without a large amount of complexity and custom implementation work to support objects that represent strongly typed primitives.
I've put together a very basic working example (the logic makes absolutely no sense, nor is it meant to) of the challenge when trying to use a type to strongly represent a primitive value.
As it stands, if I supply a valid email address, this will return
true. However, and invalid email address will throwMicrosoft.AspNetCore.Http.BadHttpRequestException: Failed to bind parameter "EmailAddress emailAddress" from "john.doe"..There is no way for me to intercept the binding to call TryParse to return a validation failure. I must using
stringas a request parameter, which does not allow me to describe it automatically as per the type, expose validation outside of the strongly typed object, and do the validation post binding.Although this proposal would eventually allow me to do validation during the binding process of Minimal API, it still would not allow me to use my strong type in the Minimal API parameters themselves.
jscarle commentedon Mar 23, 2025
This issue also highlights related Minimal API binding and validation challenges #35501
davidfowl commentedon Mar 23, 2025
@jscarle are you aware of https://learn.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.http.asparametersattribute?view=aspnetcore-9.0?
jscarle commentedon Mar 23, 2025
@davidfowl Yes, I use
[AsParameters]extensively. In my projects, I will typically have a request object and describe it like this:But this simply transfers the problem from the delegate parameters to the properties of the request as the processing is the same on properties as it is on the parameters. My read of the Minimal APIs code base (from what I was able to follow along with) is that the
AsParametersattribute simply loops through the properties as if they were the delegate parameters but the binding in itself is identical.Kumima commentedon Mar 24, 2025
Yes, 35501 first please.
captainsafia commentedon Mar 25, 2025
The issue you referenced covers errors that surface from minimal API's binding layer itself. For example,
TryParseon a Guid failing to parse a invalid query. The validation APIs introduced here execute after binding happens since they operate on the bound values. IfTryParsefails, validation never runs and we instead exit early with the binding error.So, unfortunately, the validation work here doesn't solve the problem of customizing binding error messages in minimal APIs. Middleware was mentioned as a solution to this. BindAsync can also help here.
For requiredness, we can consider taking a breaking behavior change that favors using the validation logic for verifying
Requiredattributes instead of the existing binding-layer logic. This would let you customize the error message for require values via the ErrorMessage on the RequiredAttribute.I think
BindAsyncmight be the right tool for the job here. You can continue to implement anIParsablefor EmailAddress but the minimal API handler would take a parameter that implementsBindAsync. InsideBindAsyncyou can call the parsing logic and handle custom validation there.jscarle commentedon Mar 25, 2025
Nor middleware, nor BindAsync, in their current iteration would allow us to take advantage of this validation API for values against strongly typed primitives.
The middleware would have to react to an exception which is problematic from a performance perspective and would allow the validation API to react to the binding failure.
The signatures for BindAsync would, at most allow to return a null, but then the context as to why the T is null is lost and would be difficult to surface to the validation API.
captainsafia commentedon Mar 25, 2025
@jscarle What types of validations are you talking about? Are you referring specifically to requiredness/null-checks or other types of validations (ValidationAttribute, IValidatableObject implementors, etc). If it's the later, you should be able to take advantage of this API.
For the former, see this note:
captainsafia commentedon Mar 28, 2025
Marking this issue as closed for .NET 10 Preview 3.
Sample app of current functionality is available at https://github.com/captainsafia/minapi-validation-support.
Docs issue: dotnet/AspNetCore.Docs#35090
I've created a new
feature-validationlabel to track follow-ups and am working on adding all of them there: https://github.com/dotnet/aspnetcore/issues?q=is%3Aissue%20state%3Aopen%20label%3Aarea-minimal%20label%3Afeature-validationjscarle commentedon Mar 28, 2025
@captainsafia I haven't been able to follow up to your question, been a whirlwind of a week here. I'll look for that tag and see if I can expand on my comments. Thanks!
kimbell commentedon Apr 27, 2025
@captainsafia
I work for a client that has a large legacy codebase that is based on MVC. It's not uncommon for them to have to validate something using information from a database, introducing an async call. Since the MVC validation is sync, libraries such as FluentValidation are commonly used.
Reading through this description, I notice that the validation method is async. Will this allow us to make async calls during validation, or is that reserved for the ASP.NET infrastructure only? Your sample app only shows attribute based validation. I haven't seen any sample showing async validation. Since this is a .NET10 feature, that might be coming?
The title of this issue contains "unified", but there doesn't seem to be much talk about MVC, so is that excluded from unified? Should we start pushing teams to move from MVC to Minimal API's?
captainsafia commentedon Apr 28, 2025
The validation methods are asynchronous to eventually support a more asynchronous validation pipeline in the end-to-end.
Unified here refers to the fact that these APIs can be plugged into various consuming frameworks (SignalR, Blazor, minimal APIs) and extended upon as a middleman of the navigation system. There's no plan to rewrite MVC's validation APIs to use these new abstractions.
Use validation source generator