You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We don't have a list, and telling readers to just look at the DA API (<xref:System.ComponentModel.DataAnnotations?displayProperty=fullName>) isn't sufficient to identify:
The ones that only pertain to validation.
The ones that will work with the DA Validator in Blazor.
The ones that will work with a little extra code applied for client-side validation and perhaps an example implementation of that code (e.g., [CreditCard] might be the only one if the MVC validation article is correct).
I think we'll need to provide a list of the effective attributes for the article.
We already mention custom data annotation validation attributes and cross-link to the MVC article on that. However, I really have no idea on the gotchas 😈 and dragons 🐉 of trying to follow that guidance in a Blazor app with an EditForm and DataAnnotationsValidator. Maybe it works, or maybe it 💥 in your face 😨.
Description
We don't have a list, and telling readers to just look at the DA API (
<xref:System.ComponentModel.DataAnnotations?displayProperty=fullName>
) isn't sufficient to identify:[CreditCard]
might be the only one if the MVC validation article is correct).I think we'll need to provide a list of the effective attributes for the article.
We already mention custom data annotation validation attributes and cross-link to the MVC article on that. However, I really have no idea on the gotchas 😈 and dragons 🐉 of trying to follow that guidance in a Blazor app with an
EditForm
andDataAnnotationsValidator
. Maybe it works, or maybe it 💥 in your face 😨.Page URL
https://learn.microsoft.com/en-us/aspnet/core/blazor/forms/validation?view=aspnetcore-8.0
Content source URL
https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/blazor/forms/validation.md
Document ID
bcb470e1-c859-0549-b4ef-c6c9b7ef2c72
Article author
@guardrex
The text was updated successfully, but these errors were encountered: