gethinwebster
commented
3 weeks ago Thanks - this seems like a reasonable request. We will consider it for prioritization and post updates on this thread if anything changes.
Open pavelvrublevskij opened 1 month ago
gethinwebster
commented
3 weeks ago Thanks - this seems like a reasonable request. We will consider it for prioritization and post updates on this thread if anything changes.
Problem Description
What we have and see now when whole system has date format as yyyy MMM dd, we have 3 different date formats what looks not quite well:
ISO format is not a solution when you want to have one date standard in your web application.
i.e. application could have by design date standard as: 2024 Jun 23 by date format yyyy MMM dd in this case.
Date range picker does not support this (no ISO standard for that). I looked in specification what ISO supported and there no short english version for month, but still if it is, the ISO is not a solution but a workaround solution.
en (English): January 22, 2024 en-GB (British English): 22 January 2024 de (German): 22 Jan 2024 es (Spanish): 22 ene 2024 fr (French): 22 janv. 2024 ja (Japanese): 2024年1月22日 it (Italian): 22 gen 2024 pt-BR (Brazilian Portuguese): 22 jan 2024 ko (Korean): 2024년 1월 22일 zh-CN (Simplified Chinese): 2024年1月22日 zh-TW (Traditional Chinese): 2024年1月22日 id (Indonesian): 22 Jan 2024 tr (Turkish): 22 Oca 2024
What expected in this feature request:
Would be great to have possibility to use different date formats for date range representation ts example what could be used in your component.
format(parseISO(date), "yyyy MMM dd") <-- where possible to represent by formatCode of Conduct