Closed ozten closed 7 months ago
Describe the bug I am trying to parse a string like 11/15/23 00:51 UTC. I get { Invalid, reason: unparsable }.
11/15/23 00:51 UTC
{ Invalid, reason: unparsable }
To Reproduce These fail when added to test/datetime/tokenParse.test.js
test/datetime/tokenParse.test.js
expect(DateTime.fromFormat("UTC", "ZZZZ").zoneName).toBe('UTC'); expect(DateTime.fromFormat('11/15/23 00:51 UTC', 'LL/dd/yy T ZZZZ').toMillis()).toBe(1700009460000);
These both fail.
Actual vs Expected behavior
DateTime.fromFormat should support ZZZZ formatting.
ZZZZ
Desktop (please complete the following information):
Note: This is happening in NodeJS process as well as in the browser.
Additional context
Parsing has a separate table of tokens from formatting. This is due to limitations of the Intl API that Luxon uses, this is explained here.
Describe the bug I am trying to parse a string like
11/15/23 00:51 UTC
. I get{ Invalid, reason: unparsable }
.To Reproduce These fail when added to
test/datetime/tokenParse.test.js
These both fail.
Actual vs Expected behavior
DateTime.fromFormat should support
ZZZZ
formatting.Desktop (please complete the following information):
Note: This is happening in NodeJS process as well as in the browser.
Additional context