Beispiel
Configure Luxon error handling and distinguish silent invalid object propagation from immediate exceptions using Settings.throwOnInvalid
sha256:b57c3a02647506219a15642c1ba4615bc67c7e74936f7926208302ed8ef855a5
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Fall
- Ziel
- Configure Luxon error handling and distinguish silent invalid object propagation from immediate exceptions using Settings.throwOnInvalid HOW
- Pakete
- luxon 3.5.0
- Umgebung
- node
- Erstellt
- 2026-08-16T18:38:35Z
Häufige Annahme
Parsing an invalid ISO date string or out-of-range calendar date in Luxon throws an Error or rolls over to a valid date.
So hat der Autor des Samples festgehalten, was eine Entwicklerin oder ein Modell hier erwarten würde. Der Vertrag darunter ist das, was tatsächlich lief.
Contract
- DateTime.fromISO with an unparsable string or impossible calendar date does not throw and does not roll over, returning an invalid DateTime object with isValid false and toISO null
- Operations and arithmetic on an invalid DateTime propagate isValid false without throwing, returning NaN for toMillis and null for toISODate
- DateTime.fromObject with month 0 is treated as out of range and invalid rather than wrapping to January or December
- Setting Settings.throwOnInvalid to true switches Luxon from silent invalid object propagation to immediately throwing an Error on invalid parsing, units, or timezones
- Interval.fromDateTimes with end before start creates an invalid Interval with reason 'end before start' rather than throwing unless throwOnInvalid is enabled
Dateien
- NOTES.md
- csx.json
- package-lock.json
- package.json
- test/contract.mjs
Verifiziertes Artefakt herunterladen (tar.gz) — genau die Bytes, gegen die der Contract lief
Ursprungs-Seeder
Verifizierungsbelege
- node 22 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-16 · ed25519:d91480838ac982c9