Currently, the output for parseValue("Feb 20") is parsed as { v: 44612, z: 'mmm-d' } (20 feb 2022). This is consistent with what Google Sheets does but not what users seem to expect.
One can reason it this way:
In Feb 2 the digits are obviously a day.
So then Feb 9 is also obviously a day in February.
But then it gets strange if Feb 10 is all of a sudden a year... so better to interpret them all as days.
However, Feb 02 seems obviously to be a month-year. So then why isn't Feb 20?
Ultimately there are no right or perfect answers here, but my feeling is that is more likely that trailing digits are years in this context than days (and the inverse: leading digits more likely to be days).
So we should move to:
2 May = day, month
02 May = day, month
22 May = day, month
2222 May = year, month
May 2 = Either invalid OR month, day (still undecided)
Currently, the output for
parseValue("Feb 20")is parsed as{ v: 44612, z: 'mmm-d' }(20 feb 2022). This is consistent with what Google Sheets does but not what users seem to expect.One can reason it this way:
Feb 2the digits are obviously a day.Feb 9is also obviously a day in February.Feb 10is all of a sudden a year... so better to interpret them all as days.However,
Feb 02seems obviously to be a month-year. So then why isn'tFeb 20?Ultimately there are no right or perfect answers here, but my feeling is that is more likely that trailing digits are years in this context than days (and the inverse: leading digits more likely to be days).
So we should move to:
2 May= day, month02 May= day, month22 May= day, month2222 May= year, monthMay 2= Either invalid OR month, day (still undecided)May 02= month, yearMay 22= month, yearMay 2222= month, year