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
New Sample: Client-side data validation for user input #21
Comments
I need this demo too. I saw this feature on msdn, but there have not any documents. |
@h82258652 I looked more into it on VS 2015 RC, and the properties aren't even available. But, as you said, it's mentioned in What’s new for developers in Windows 10. |
@bricelam |
FYI, patterns & practices has some good guidance on implementing validation yourself, but it will sure be nice to have it built in. |
Emm, great article. But I think this:
can be more better. We write "FirstName" twice. The validation system should know what property we are binding. |
This topic is increasing in scope, I've reached out to the owners of this API to respond on this thread specifically about samples in this area. I recommend moving the more in-depth discussion to the Developing Universal Windows apps forum - https://social.msdn.microsoft.com/Forums/windowsapps/en-US/home?forum=wpdevelop |
@AdamBraden |
Thank you. |
Hi @bricelam thanks for this note. Unfortunately, yes these features for validation will not make it in the final release for Windows 10 right now. We had some good initial feedback from customers that we weren't delivering the expectations and we want more time to get this right before delivering something that wasn't going to meet customers needs primarily. This remains on our backlog for prioritizing against ongoing/new customer requests. |
@timheuer |
It would be great to see a sample demonstrating the new
ValidationErrors
property along with its companion propertiesValidationState
,ValidationIndicatorStyle
&IsValidationIndicatorEnabled
.It would also be good to see how it integrates with
ValidationAttribute
andIValidatableObject
.The text was updated successfully, but these errors were encountered: