ObjectGraphDataAnnotationsValidator

[boukenka]

Hello,

Is there an update for the Blazor integration of ObjectGraphDataAnnotationsValidator in .NET 6.0 ?
I am currently using .NET 6.0 Preview 4 and it is not present 😄 (unless I am mistaken)
I know this is planned : Roadmap ASP.NET Core 6 - Missing issues
I don't see it in the ASP.NET Core Roadmap for .NET 6
Would it be possible to get an ETA please?

[javiercn]

@boukenka thanks for contacting us.

I believe @pranavkm was working towards getting this on the runtime itself, I'm not sure if that'll happen, though.

Thanks for contacting us.

We're moving this issue to the Next sprint 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.

[boukenka]

@javiercn Thank you for the answer. I hope it will be part of the .NET 6.0 release.

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.

[boukenka]

@mkArtakMSFT Hello. The current package is still in 3.2.-rc1. ASP.NET Core 3.2 RC was released on April 30, 2020. I assume it will not be part now of .NET 6 release. What is the hope that one day this issue will be resolved? Should I open in a few months the same issue?

[pranavkm]

@boukenka some of the same issues that we're trying to tackle as part of this package also need to be solved for minimal actions. Unfortunately we haven't found the time to figure out ways to productize a solution that works for either and hope to look at it in 7.0. In the meanwhile, the current package should continue to function.

[boukenka]

@pranavkm Thanks for the reply. I am keeping my fingers crossed that this problem will be solved in version 7.0, even if it will take more than a year to wait.

[boukenka]

@mkArtakMSFT Hello. Could this issue be added in the .NET 7 Planning ? Also, do you plan to ask people what issues/improvements they would like for .NET 7, as was done for .NET 6.0?