Skip to content

Package version for ObjectGraphDataAnnotationsValidator #23289

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

Closed
boukenka opened this issue Jun 24, 2020 · 5 comments
Closed

Package version for ObjectGraphDataAnnotationsValidator #23289

boukenka opened this issue Jun 24, 2020 · 5 comments
Labels
area-blazor Includes: Blazor, Razor Components feature-blazor-wasm This issue is related to and / or impacts Blazor WebAssembly ✔️ Resolution: Answered Resolved because the question asked by the original author has been answered. Status: Resolved

Comments

@boukenka
Copy link

boukenka commented Jun 24, 2020

Hello,

I was using the ObjectGraphDataAnnotationsValidator to validate some fields in an EditForm
in a Web Assembly ASP.NET Core project
I noticed that the current version of the NuGet package is 3.2.0-rc1.20223.4.
Is this normal? Or should I use another package? What is the status for this package?
This package is described in ASP.NET Core Blazor forms and validation

@javiercn javiercn added area-blazor Includes: Blazor, Razor Components feature-blazor-wasm This issue is related to and / or impacts Blazor WebAssembly labels Jun 24, 2020
@pranavkm
Copy link
Contributor

@boukenka that package experimental that we were hoping to replace with fixes in the BCL in 5.0. That said, it should be perfectly fine to continue using it.

@pranavkm pranavkm added the ✔️ Resolution: Answered Resolved because the question asked by the original author has been answered. label Jun 24, 2020
@ghost ghost added the Status: Resolved label Jun 24, 2020
@mrpmorris
Copy link

@pranavkm did anyone ever look at my suggested validation changes?

@captainsafia
Copy link
Member

@mrpmorris We did take a look at the suggested changes but it's not something that we intend on integrating into the framework. We think that this particular change would be better suited for a community project.

@mrpmorris
Copy link

They can't be done as a community project because changes were required to the Blazor classes, that's why I proposed something 100% backwards compatible.

@ghost
Copy link

ghost commented Jun 26, 2020

This issue has been resolved and has not had any activity for 1 day. It will be closed for housekeeping purposes.

See our Issue Management Policies for more information.

@ghost ghost closed this as completed Jun 26, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Jul 26, 2020
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-blazor Includes: Blazor, Razor Components feature-blazor-wasm This issue is related to and / or impacts Blazor WebAssembly ✔️ Resolution: Answered Resolved because the question asked by the original author has been answered. Status: Resolved
Projects
None yet
Development

No branches or pull requests

5 participants