Fixed #13382 - confusion around localization date #13455
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #13382 - This is a small change that will hopefully clear up confusing around the date format select list. I had previously used this month, then the day of 25, and the current year (so that date formats like Feb 3, 2023 - which could be month-day-year OR day-month-year would be clearer, since there is no 25th month), but it seems it was causing confusion. This uses today's date, and hopefully the format is guessable via the other options in the menu.
This could still be confusing if the user is changing this on a day where the month and the day are the same (Feb 2, 2023) which was also what I was trying to avoid, but hopefully this will help. (I had considered including the
$format
in the dropdown, but not everyone will know whatn/d/y
means. ¯_(ツ)_/¯