Add EditContext.IsValid(..) to determine if a field has any associated validation messages.

[pranavkm]

Background and Motivation

Proposed API

Add an API to query if a FieldIdentifier is valid without having to get validation messages. We have several places that get the messages only to determine this condition e.g. https://github.com/dotnet/aspnetcore/blob/main/src/Components/Web/src/Forms/InputBase.cs#L245

This has the sneaky benefit of removing yet another Linq call because we do something more optimized to determine this condition.

Usage Examples

// some lines of code here
var isValid = EditContext.IsValid(FieldIdentifier);
if (!isValid)
{
   // Do stuff
}

Alternative Designs

Risks

[ghost]

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

[TanayParikh]

@pranavkm is this something you envision for 7.0?

[ghost]

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

[ghost]

Thanks for contacting us.

We're moving this issue to the .NET 8 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[rasaconsulting-sandy]

This would be a great enhancement!

[ghost]

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.