Skip to content

v0.2.1 — honest docs, real-world recipes, public conformance suite

Latest
Latest

Choose a tag to compare

View all tags
@sina-heidariaan sina-heidariaan released this 19 Aug 02:32
· 4 commits to main since this release
v0.2.1
344000e

Documentation and metadata only. The published code is byte-identical to 0.2.0 — no token, API or behaviour change. Upgrading is safe and optional.

Fixed

  • package.json repository, bugs and homepage pointed at a repository name that no longer exists.

Documentation

  • Removed the overstated claim that "nothing is lost". Nanoseconds, UTC offset and IANA zone id do survive a round trip; the calendar does not. The new "Calendars — current limitation" section shows a Hebrew-calendar round trip coming back as a different day, and the ISO-conversion workaround.
  • New Recipes section: yyyyMMdd, LDAP generalized time, Luxon fromFormat migration, date-fns migration, zoned nanosecond timestamps — each backed by a test.
  • New comparison against Temporal, Luxon, date-fns and temporal-fmt.

Added

  • Public conformance suite — conformance/cases.json, 65 machine-readable cases covering DST gaps and overlaps, inputs that must be rejected, extreme years, offset and zone spellings, and 1–9 fractional-second digits. It is data, not code, so any Temporal token library can be run against it.

Which date format are you stuck with? #2

Assets 2
Loading