test262

Commit Graph

Author	SHA1	Message	Date
Ben Allen	a5e2cf2433	Update InitializeDateTimeFormat references to new CreateDateTimeFormat to reflect recent editorial change (#3889 )	2023-08-07 17:01:48 +02:00
Michael Dyck	82e0487797	"Normalize" some YAML In each case, it's the scalar value associated with the "description" key. Normally in test262, this is written in either: - block notation (indicated by '>' or '\|'), or - flow notation, single-line, on the same line as the key. In the cases addressed by this PR, the value is instead written in: - (1x) flow notation, multi-line, or - (2x) flow notation, single-line, on the line after the key. These are valid YAML, but they're styles that test262 doesn't otherwise use, so could conceivably confuse people or harnesses. This PR changes them to block notation.	2021-07-21 16:34:04 -04:00
jugglinmike	8faacdbaee	Add tests: "Extend TimeZoneName Option" proposal (#3042 )	2021-07-16 09:45:02 -04:00

Author

SHA1

Message

Date

Ben Allen

a5e2cf2433

Update InitializeDateTimeFormat references to new CreateDateTimeFormat to reflect recent editorial change (#3889 )

2023-08-07 17:01:48 +02:00

Michael Dyck

82e0487797

"Normalize" some YAML

In each case, it's the scalar value associated with the "description" key.
Normally in test262, this is written in either:
- block notation (indicated by '>' or '|'), or
- flow notation, single-line, on the same line as the key.

In the cases addressed by this PR, the value is instead written in:
- (1x) flow notation, *multi*-line, or
- (2x) flow notation, single-line, on the line *after* the key.

These are valid YAML, but they're styles that test262 doesn't otherwise use,
so could conceivably confuse people or harnesses.

This PR changes them to block notation.

2021-07-21 16:34:04 -04:00

jugglinmike

8faacdbaee

Add tests: "Extend TimeZoneName Option" proposal (#3042 )

2021-07-16 09:45:02 -04:00

3 Commits