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.

Sign up for GitHub

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

Jump to bottom

Migrate Blazor.DataAnnotations.Validation features in to CoreFx #16810

Closed
1 of 2 tasks
pranavkm opened this issue Nov 4, 2019 · 2 comments
Closed
1 of 2 tasks

Migrate Blazor.DataAnnotations.Validation features in to CoreFx #16810

pranavkm opened this issue Nov 4, 2019 · 2 comments
Labels
affected-medium This issue impacts approximately half of our customers area-blazor Includes: Blazor, Razor Components ✔️ Resolution: Won't Fix Resolved because we decided not to change the behavior reported in this issue. severity-major This label is used by an internal tool Status: Resolved
Milestone
Backlog

Comments

@pranavkm
Copy link
Contributor

pranavkm commented Nov 4, 2019 •
edited by mkArtakMSFT
Loading

The Microsoft.AspNetCore.Blazor.DataAnnotations.Validation package was added as an stop-gap for 3.1 until we move features further upstack i.e. CoreFx \ System.DataAnnotations.Validation. This issue is used to track work done in other repos and any follow up that needs to happen in Blazor once this is complete
@pranavkm pranavkm added area-blazor Includes: Blazor, Razor Components enhancement This issue represents an ask for new feature or an enhancement to an existing one labels Nov 4, 2019
@pranavkm pranavkm added this to the 5.0.0-preview1 milestone Nov 4, 2019
@mkArtakMSFT mkArtakMSFT added the Components Big Rock This issue tracks a big effort which can span multiple issues label Jan 10, 2020
@ghost
Copy link

ghost commented Jul 23, 2020

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.

@javiercn javiercn added affected-medium This issue impacts approximately half of our customers severity-major This label is used by an internal tool labels Oct 9, 2020 — with ASP.NET Core Issue Ranking
@pranavkm
Copy link
Contributor Author

Dropping this in favor of #28640

@pranavkm pranavkm added ✔️ Resolution: Won't Fix Resolved because we decided not to change the behavior reported in this issue. and removed Components Big Rock This issue tracks a big effort which can span multiple issues enhancement This issue represents an ask for new feature or an enhancement to an existing one labels Mar 30, 2021
@ghost ghost added the Status: Resolved label Mar 30, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Apr 29, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
affected-medium This issue impacts approximately half of our customers area-blazor Includes: Blazor, Razor Components ✔️ Resolution: Won't Fix Resolved because we decided not to change the behavior reported in this issue. severity-major This label is used by an internal tool Status: Resolved
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
3 participants
@pranavkm @javiercn @mkArtakMSFT