You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to the Document and tests from the live meridiem site, dateFormat: tag only decides whether M/d/y or d/M/y format.
In my culture people use Year/Month/Day format, so it was a little shame that format parsing does not support like:
2031/11/19 - 2099/08/04 (just the y/M/d transposition of current M/d/y format)
or
2031/11/19 ~ 2099/08/04 (you may see its strange, but using '~' as a 'range sign' is pretty popular in Asian countries)
I hope someday dateFormat would support at least yMd sequencing..
p.s) And I also found that the degree of freedom in formatting was a little bit inconsistent:
[o] 2031-11-19T01:35:10Z-2099-08-04T18:22:48Z
[x] 2031-11-19-2099-08-04
[o] 2031-11-19/2099-08-04
The text was updated successfully, but these errors were encountered:
According to the Document and tests from the live meridiem site, dateFormat: tag only decides whether M/d/y or d/M/y format.
In my culture people use Year/Month/Day format, so it was a little shame that format parsing does not support like:
2031/11/19 - 2099/08/04 (just the y/M/d transposition of current M/d/y format)
or
2031/11/19 ~ 2099/08/04 (you may see its strange, but using '~' as a 'range sign' is pretty popular in Asian countries)
I hope someday dateFormat would support at least yMd sequencing..
p.s) And I also found that the degree of freedom in formatting was a little bit inconsistent:
[o] 2031-11-19T01:35:10Z-2099-08-04T18:22:48Z
[x] 2031-11-19-2099-08-04
[o] 2031-11-19/2099-08-04
The text was updated successfully, but these errors were encountered: