Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ObjectGraphDataAnnotationsValidator #33247

Closed
boukenka opened this issue Jun 3, 2021 · 13 comments
Closed

ObjectGraphDataAnnotationsValidator #33247

boukenka opened this issue Jun 3, 2021 · 13 comments
Labels
area-blazor Includes: Blazor, Razor Components enhancement This issue represents an ask for new feature or an enhancement to an existing one feature-blazor-builtin-components Features related to the built in components we ship or could ship in the future
Milestone

Comments

@boukenka
Copy link

boukenka commented Jun 3, 2021

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 javiercn added area-blazor Includes: Blazor, Razor Components feature-blazor-builtin-components Features related to the built in components we ship or could ship in the future labels Jun 3, 2021
@javiercn
Copy link
Member

javiercn commented Jun 3, 2021

@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.

@mkArtakMSFT mkArtakMSFT added the enhancement This issue represents an ask for new feature or an enhancement to an existing one label Jun 3, 2021
@mkArtakMSFT mkArtakMSFT added this to the Next sprint planning milestone Jun 3, 2021
@ghost
Copy link

ghost commented Jun 3, 2021

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
Copy link
Author

boukenka commented Jun 3, 2021

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

@ghost
Copy link

ghost commented Jul 20, 2021

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
Copy link
Author

boukenka commented Jul 20, 2021

@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
Copy link
Contributor

@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
Copy link
Author

@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
Copy link
Author

boukenka commented Oct 5, 2021

@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?

@ghost
Copy link

ghost commented Nov 11, 2021

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
Copy link
Author

@mkArtakMSFT Hello. Why is it back to the Backlog milestone?

@boukenka
Copy link
Author

@LukasKubicek
Copy link

This should really be given some priority. Validating only top level object in real business applications is pretty much useless.

@danroth27
Copy link
Member

Closing as duplicate of #28640

@ghost ghost locked as resolved and limited conversation to collaborators Jul 7, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-blazor Includes: Blazor, Razor Components enhancement This issue represents an ask for new feature or an enhancement to an existing one feature-blazor-builtin-components Features related to the built in components we ship or could ship in the future
Projects
None yet
Development

No branches or pull requests

7 participants