Skip to content

Improve section order and possibly split the article #37249

Description

@guardrex

Description

Per discussion with Ondřej on #37113, we should at least work on section order. We probably should split this long article into two articles. Here's the feedback ...

... can we reorder the sections in the long Blazor forma validation article so that the docs flow from the most basic/standard/default scenarios to the more advanced/custom ones? For typical Blazor apps the order of complexity is roughly:

  1. Built-in validation rules using validation attributes and a DataAnnotationsValidator inside EditForm.
  2. Custom validation rules using custom validation attributes or IValidatableObject and a DataAnnotationsValidator inside EditForm.
  3. Information about AddValidation.
  4. Custom validation logic using the API of EditForm and EditContext.
  5. Only then something like this. [Referring to custom server-side validation and other advanced scenarios.]

Thinking about it more, it might help us to break up this long article into one that cover 1-3 and another covering 5-6.

Page URL

https://learn.microsoft.com/en-us/aspnet/core/blazor/forms/validation?view=aspnetcore-10.0

Content source URL

https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/blazor/forms/validation.md

Document ID

bcb470e1-c859-0549-b4ef-c6c9b7ef2c72

Platform Id

b4c1bad9-fc7a-21f5-2552-f0f3617f77db

Article author

@guardrex

Metadata

  • ID: bcb470e1-c859-0549-b4ef-c6c9b7ef2c72
  • PlatformId: b4c1bad9-fc7a-21f5-2552-f0f3617f77db
  • Service: aspnet-core
  • Sub-service: blazor

Related Issues

Metadata

Metadata

Assignees

Type

No type
No fields configured for issues without a type.

Projects

Status
P0/P1 - High Priority

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions