Date format

[AtomicFS]

It would be great to be able to change the date format in comments. The american dd/mm/yyyy is not great date format.

I find the ISO 8601 to be the best date format ever: yyyy-mm-dd. Especially when used in filenames - when you sort alphabetically you have then also sorted chronologically ;)

Sorry about the rant.

Would it be possible to add such config option?

[stdavis]

Thanks for the feedback. This would be a cool enhancement. I did a few minutes of digging and found that this may be possible but it would have to be an upstream improvement to the parse-reminder package in how it uses chrono-node. It does appear that chrono-node supports a few other locales that use the "best date format ever". :)

We are considering vendoring parse-reminder since it doesn't seem to be maintained so I'll keep this issue open in case we want to include it as part of that issue. I could see exposing a locale input to this action that matches the list supported by chrono-node.

[froque]

I did a few minutes of digging and found that this may be possible but it would have to be an upstream improvement to the parse-reminder package in how it uses chrono-node

I do not think this is needed.

The problem seems to be the usage of toLocaleDateString function call:
https://github.com/agrc/create-reminder-action/blob/9ff30cde74284045941af16a04362938957253b1/index.js#L87C39-L87C64

Replacing it could lead to ISO 8601 format, the best date format ever.

create-reminder-action on  main is 📦 v1.1.17 via  v22.13.1 took 16s 
❯ node
Welcome to Node.js v22.13.1.
Type ".help" for more information.
> var parseReminder = require('parse-reminder')
undefined
> r = parseReminder('remind me to call the doctor tomorrow')
{ who: 'me', what: 'call the doctor', when: 2025-04-18T08:00:00.000Z }
> r.when.toLocaleDateString()
'4/18/2025'
> r.when.toISOString().split('T')[0]
'2025-04-18'

[stdavis]

@froque That looks promising. I may have overlooked this in my previous digging. We'd be open to a PR.