Open mrlacey opened 6 years ago
I believe this is actually part of the WinUI toolkit
My understanding was that this won't be in the WinUI library as it's dependent upon OS specific functionality for some of the control functionality and won't be backported to earlier Win10 versions.
I guess we need to wait for the release of the controls/library before we'll know for sure.
we should be able to start mocking this out with the internal nuget for validating the page. I would use sample data for the page and add in a new item.
By working on this before it's public means we can't discuss/review or get feedback in public either. If this is going to be RS5 only then there's no rush to get started, is there?
It is in winUI. We are doing the same with menu bar
Have we got confirmation of it being in WinUI? At Build I was told it's not as some of the functionality is dependent upon OS level functionality in the controls. If running via WinUI with limited functionality it'd be good to know the differences in what's delivered.
We'll have a look at this
sadly this is going to be a bit further out than i was hoping
WinUI will gain Form validation. when it does, we can create a page. we still can mock something out maybe visually for what could work. Could we adapt the sample data class?
Our Mockup for WinUI in Desktop contains a FormPage using WinUI3 input validation. Input validation is still in preview and was removed for the Project Reunion 0.5 version, so you'll have to update the project reunion nuget to a 0.5-preview version to see validation errors on the UI. As Input validation is still in preview we will disable the Form Page on our nightly vsix.
The next version of WIn10 will bring (fingers crossed) built in validation functionality to common entry controls.
We think it would be beneficial to include a page that uses this but we'd need to establish a good set of content to include by default as we don't want it to just be a sample.
This functionality is expected to only be available in the next SDK version and forward with on backward support built-in. Adding this may require we do #2285 (for moving the min SDK version)