Adding support for custom ValidationResult (derived class) in CustomV…#35584
Adding support for custom ValidationResult (derived class) in CustomV…#35584ajcvickers merged 4 commits intodotnet:masterfrom
Conversation
…alidationAttribute
|
/azp run corefx-ci (Windows NETFX_x86_Release) |
|
No pipelines are associated with this pull request. |
...nentModel.Annotations/src/System/ComponentModel/DataAnnotations/CustomValidationAttribute.cs
Outdated
Show resolved
Hide resolved
|
I don't think the CI failure is caused by your change. It's the usual failure to upload to helix on a single step but i don't see an actual test failure. relevant log items are: /cc @safern for confirmation that i'm reading that right. If if is a false failure then you need to copy in the area owners so they can review, @lajones, @divega, @ajcvickers |
|
This actually seems like a failure with this PR itself. If you look at the failure: It is failing directly here, on the added CustomValidator. It makes sense, since NETFX doesn't have this support: https://github.com/dotnet/corefx/pull/35584/files#diff-5fb1c2fa77569a06289a2ffca62c378aR246 So the test will need to be conditioned to only run on netcoreapp. To skip the test entirely for NETFX, we can add an attribute to https://github.com/dotnet/corefx/pull/35584/files#diff-80b5d2f008710e7c2a1b943f176c98dbR183: |
|
If you click on the I have a draft on the docs already. Should send a PR today 😄 |
|
Oh! ok, so you follow the links through all the fancy stuff to get a link that you have to copy paste out into a totally different app. That's not quite as obvious as it could perhaps be. Thanks for the info though, that'll stop me copying you into issues so you can read the log for me 😀 |
You can also do CTRL+Click and you don't have to copy the link from the logs. We're definitely working on improving that experience since it is painful, but we're limited now since we depend from azure devops fixes we requested, but it should improve on time 😄 |
|
I'm not sure I follow why it is failing in .NET Framework.. |
Because .NET Framework doesn't support custom ValidationResult, because the support you're adding here is for .NET Core only, bits for .NET Core and UAP from this repo. .NET Framework is another code base and most likely it will not get this back-ported. |
|
Ok, I will fix the tests. However, is there some article that explains how this works, how to test in on local machine etc? Some guidance for community. Or I'm left only with the readmes in this repo? |
|
Most of what you need it in the documentation folder in various places. There's also a doc just being added which covers some of the newer aspects #35672 (comment) |
|
Thanks! |

#33767