Per-property opt out of implicit required validation.
Author: PleasantDCreated Sep 17, 2026Updated Sep 17, 2026
Labelsarea-mvc
Is there an existing issue for this?
- I have searched the existing issues
Is your feature request related to a problem? Please describe the problem.
There are cases where the model correctness is a non-null property but the model itself can provide a valid default and therefore is NOT required to be submitted.
My primary case is
public class VMExample
{
// An empty collection is _fine_ here
public List<Guid> Selections { get; set; } = [];
}When I bind this to something like a Telerik Kendo multi-select it winds up with the unobtrusive required validation which prevents the form from being submitted with 0 entries.
However, I do not want to disable the implicit required validation everywhere.
The current thing that we have to do is
public class VMExample
{
public List<Guid>? Selections { get; set; } = [];
}But this basically means that uses of vm.Selections result in nullable warnings because initialization is not considered.
Describe the solution you'd like
I would be happy with any of
[NotRequired][Required(AllowEmptyCollection=true)][SuppressImplicitRequired]- A range or min length validation of 0 overriding (excluding/removing) the required attribute
- Automatic bypass of the implicit required attribute for cases where the model has an initialized default value
Additional context
No response
Source: dotnet/aspnetcore