tyler.durden
/
test262
mirror of https://github.com/tc39/test262.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Temporal: Add coverage for validating offset string syntax vs suitability 

Syntax is validated first. Only after the property bag is fully converted
into a Calendar Fields Record does the time zone validate whether the UTC
offset is correct for that exact time in the time zone.

See tc39/proposal-temporal#2962
This commit is contained in:
Philip Chimento 2024-10-03 12:17:17 -07:00 committed by Ms2ger
parent 6dced5dead
commit 459cef7185
1 changed files with 27 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
test/built-ins/Temporal/ZonedDateTime/from/offset-string-invalid.js Normal file
View File

@ -0,0 +1,27 @@
// Copyright (C) 2024 Igalia, S.L. All rights reserved.
// This code is governed by the BSD license found in the LICENSE file.
/*---
esid: sec-temporal.zoneddatetime.from
description: Validation of monthCode
features: [Temporal]
---*/
const bag = { year: 2024, monthCode: "M10", day: 3, timeZone: "UTC" };
["garbage", "00:00", "+000:00", "-00:000", "-00:00:000", "+00:00.0", "+00:00:00.0000000000"].forEach((offset) => {
assert.throws(RangeError, () => Temporal.ZonedDateTime.from({ offset, year: 2024, monthCode: "M10", day: 3, timeZone: "UTC" }),
`UTC offset '${offset}' is not well-formed`);
});
assert.throws(
RangeError,
() => Temporal.ZonedDateTime.from({ offset: "--00:00", year: Symbol(), monthCode: "M10", day: 3, timeZone: "UTC" }),
"UTC offset syntax is validated before year type is validated"
);
assert.throws(
TypeError,
() => Temporal.ZonedDateTime.from({ offset: "+04:30", year: Symbol(), monthCode: "M10", day: 3, timeZone: "UTC" }),
"UTC offset matching is validated after year type is validated"
);