-
Notifications
You must be signed in to change notification settings - Fork 49
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
Support for AM/PM in DateTime variable formats #318
Comments
To stay aligned with moment.js we should probably use Note that we do support 12-hours values from 1 to 12 with |
Hi @jeromesimeon, As an old .NET C# developer, Anyway...it was just a suggestion. If Having said that, there's no real point adding support for AM/PM unless we can add support for 12-hour values too. Users would not expect to see Sounds like this is not an easy enhancement? |
…ccordproject#318 Signed-off-by: Jerome Simeon <jeromesimeon@me.com>
…318 Signed-off-by: Jerome Simeon <jeromesimeon@me.com>
Added in #319 Semantics notes:
|
Released in https://github.com/accordproject/cicero/releases/tag/v0.21.7 Let me know if it works. |
@jeromesimeon - We are using this new AM/PM format in our real estate contract templates now. Works like a charm! Thank you!! |
Is your feature request related to a problem? Please describe.
Currently, it is only possible to display DateTime variables in 24 Hr format (e.g. 15:00) whereas some end-users may expect to see times displayed in AM/PM format (e.g. 3:00 pm).
Describe the solution you'd like
Current DateTime format options are defined at https://docs.accordproject.org/docs/markup-variables.html
Would be great if DateTime variables supported the following additional format options:
t
- The first character of the AM/PM designator. (Example: A or P)tt
- The AM/PM designator. (Example AM or PM)Of course, if the
t
ortt
format were to be used then the PM hour values would need to be displayed using their 12-hour values instead of their 24-hour values (e.g. 3:00 PM instead of 15:00 PM).The text was updated successfully, but these errors were encountered: