Docs for Nested models, collection types, and complex types - is it outdated?

[LukasKubicek]

Hello,
the section for Nested models, collection types, and complex types instructs to install package Microsoft.AspNetCore.Components.DataAnnotations.Validation which is marked as experimental and latest release is 3.2.0-rc1.20223.4 from April 2020.

Is this still relevant for .NET 6?

How do we validate nested, complex and collection items in Blazor now?

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: eef47457-c8cf-74a4-b884-c1fe5c2ef52d
• Version Independent ID: 09a02d10-2834-467d-d8c2-3fd19ceb3863
• Content: ASP.NET Core Blazor forms and validation
• Content Source: aspnetcore/blazor/forms-validation.md
• Product: aspnet-core
• Technology: aspnetcore-blazor
• GitHub Login: @guardrex
• Microsoft Alias: riande

[guardrex]

🍂 OOF for the holidays 🍂

This issue has been marked for triage on the Blazor.Docs project, and I'll respond as soon as I return in 2022. I'll be back working on issues around Wednesday, Jan. 5. It will take a little while to dig out ⛰️⛏️ from holiday issues. I'll get back to you ASAP 🏃.

We only work on documentation on this repo. If you need product support, close this issue and seek assistance through one or more of the following support channels:

• Stack Overflow (tagged: blazor)
• General ASP.NET Core Slack Team
• Blazor Gitter

If you think that you found a potential bug in the framework or have product feedback, close this issue and open a new issue for the ASP.NET Core product unit at dotnet/aspnetcore issues. Bug reports require a clear explanation of the problem, usually including a minimal repro project placed on GitHub for the product unit engineers to download and run. If you determine with the product unit that it isn't a bug but merely requires documentation, please re-open this docs issue and place a cross-link to your engineering issue discussion. I'll take it up with you when I return from vacation.

For problems or feedback on Visual Studio or Visual Studio for Mac, close this issue and use the Report a Problem or Suggest a Feature processes from within VS, which open internal issues for VS teams. For more information, see Visual Studio Feedback or How to report a problem in Visual Studio for Mac.

For problems with Visual Studio Code, close this issue and ask for support on community support forums. For bug reports and product feedback, open an issue on the microsoft/vscode GitHub repo.

💃🕺🥳 Happy New Year! 🎈🎆🍾🥂🎉 See you in 2022!

[guardrex]

Hello @LukasKubicek ... I'm finally back and digging out ⛏️⛰️ on holiday issues. Thanks for waiting.

Yes, it's still experimental, it should still work for .NET 6, and they still haven't quite reached it a final decision to include the API OOB and fully supported in the framework/runtime. They're considering it for .NET 7. See ...

• ObjectGraphDataAnnotationsValidator aspnetcore#33247
• Consider shipping ObjectGraphDataAnnotationsValidator / ValidateComplexTypeAttribute aspnetcore#28640

PLEASE THO just add a 👍 to comments if you can and don't leave "I want this, too"-type comments. You know ... such "Me, too!" GH comments generate pings to already crazy-busy product unit engineers 😵 lol. If you just 👍, they'll see that when they assess potential issues for .NET 7, and they can gauge from them how much the community wants the feature rolled in. It's probably best to 👍 the opening comment of each one. However ... if you do truly have an important ask for the feature ... something perhaps that the current bits in the experimental package can't do or doesn't do the way that you'd like ... indeed, Yes! ... go ahead and remark to them on it. They use that feedback for the feature design. They do answer questions there if you need to know something.

Ok ... well ... this is hopefully 🤞 an actionable item for .NET 7. We keep track of the new features on the docs repo starting in Q3 on a tracking issue that we'll open later. No worries on closing this issue at this time. We'll set up tracking for it later. Thanks for commenting on the guidance.