-
Notifications
You must be signed in to change notification settings - Fork 742
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
chore: Add missing DateTimeFormatter formats #18948
Conversation
🤖 Your Docs stage site is ready! Visit it here: https://unodocsprstaging.z13.web.core.windows.net/pr-18948/index.html |
🤖 Your WebAssembly Sample App stage site is ready! Visit it here: https://unowasmprstaging.z20.web.core.windows.net/pr-18948/index.html |
is there a way this can be tested via a runtime test? |
The build 148790 found UI Test snapshots differences: Details
|
@MartinZikmund As mentioned internally, my idea is to add more tests for DateTimeFormatter features, since we know the proper results from WinUI. I will add this in a separate PR. |
🤖 Your WebAssembly Sample App stage site is ready! Visit it here: https://unowasmprstaging.z20.web.core.windows.net/pr-18948/index.html |
🤖 Your Docs stage site is ready! Visit it here: https://unodocsprstaging.z13.web.core.windows.net/pr-18948/index.html |
|
The build 149008 found UI Test snapshots differences: Details
|
GitHub Issue (If applicable): closes #18717
PR Type
What kind of change does this PR introduce?
What is the current behavior?
We are missing two of the possible values in the dictionary when matching for the right format.
PR Checklist
Please check if your PR fulfills the following requirements:
Screenshots Compare Test Run
results.