When pretty-printing this date, it corrects it to a valid date list, in the case above Jan 01,Jan 04,Jan 05.
In the case that a year is specified, the logic that generates the string creates ambiguities in the resulting string that didn't exist in the source string:
2023 Jul 21,28 10:00-18:00 is converted to
2023 Jul 21,Jul 28 10:00-18:00
Previously, the rule was clear that it is not opened outside of July 2023. Now, it could be read that generally, it is open July 28th. This creation of an ambiguity could be avoided by instead converting the source string to
2023 Jul 21,2023 Jul 28 10:00-18:00
i.e. ascribing the year selector to the month/date selector if there is only a single year and only single month/date selector.
In non-strict mode, this parser is able to parse
When pretty-printing this date, it corrects it to a valid date list, in the case above
Jan 01,Jan 04,Jan 05.In the case that a year is specified, the logic that generates the string creates ambiguities in the resulting string that didn't exist in the source string:
2023 Jul 21,28 10:00-18:00is converted to2023 Jul 21,Jul 28 10:00-18:00Previously, the rule was clear that it is not opened outside of July 2023. Now, it could be read that generally, it is open July 28th. This creation of an ambiguity could be avoided by instead converting the source string to
2023 Jul 21,2023 Jul 28 10:00-18:00i.e. ascribing the year selector to the month/date selector if there is only a single year and only single month/date selector.