-
Notifications
You must be signed in to change notification settings - Fork 192
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
Use Local Date Format for Required Date in v2.0 unless specified in JSON/Profile #615
Comments
Have no intention of doing this. You can use a different format that works for all regions vs just MM/DD. For example MMM I already didn't want to support this feature, but I did so to be nice. Next request will be to support military vs non military (12 vs 24 hour formats). if you really want this, please create two configs and maintain them. |
I re read this. Perhaps https://www.swiftyplace.com/blog/swift-date-formatting-10-steps-guide would work. But I don't know. Do you know if there is a built in method for this in swift? |
Here is some pseduo code I pulled from ChatGPT and ran through xCode Playgrounds.
When I change the region it updates the format. Interesting it does NOT work if you change the date format seperately. It pulls the date format from the region. |
This should be fixed with 84fb165 https://github.com/macadmins/nudge/actions/runs/10079098388 |
I can confirm that is the date format is now set based on the format selected in System Settings. I also confirmed that setting the Thanks, as always, for your quick response. |
Great. I will release v2.0.5 with this fix once the other person who requested a feature tests and confirms if it solves their issue. |
Currently the required date is displayed in MM/DD/YYYY format unless overridden in a profile/json file. Most EMEA and APAC countries use different formats such as DD/MM/YYYY or YYYY-MM-DD. While we can set a different format, that would mean having different settings by region and country.
Feature request is to use the Locale date format unless overridden in the profile/json.
The text was updated successfully, but these errors were encountered: