What custom date format are you trying to parse with Temporal?

[sina-heidariaan]

Temporal only reads ISO 8601 and RFC 9557. Real systems do not.

I am collecting the actual date layouts people are stuck with, so this library covers
real inputs instead of the ones I imagined. If you have one, please drop a reply with:

1. One real example string (change any private parts, keep the shape):
   20260713093000Z
2. Where it comes from: a Postgres export, an LDAP directory, an SAP feed, a bank
   file, a partner's CSV, a legacy mainframe…
3. What you want back: a PlainDate, a PlainDateTime, a ZonedDateTime…
4. What you use today, if anything: Luxon fromFormat, date-fns parse, a regex,
   a hand-written splitter…

That is all — no bug report, no reproduction needed. A one-line reply is genuinely
useful to me.

Does it already work?

Most numeric layouts do. Quick check:

import { parse } from "temporal-format-parse";

parse("20260713", "yyyyMMdd", "PlainDate");
parse("13.07.2026", "dd.MM.yyyy", "PlainDate");
parse("2026-07-13T09:30:00.123456789-04:00[America/New_York]",
      "yyyy-MM-dd'T'HH:mm:ss.SSSSSSSSSZZ'['VV']'", "ZonedDateTime");

Token list: https://github.com/sina-heidariaan/temporal-format-parse#tokens

Known to NOT work yet

• Month or weekday names (Jul, July, Monday) — deliberately out of scope for
  now, because it needs locale data.
• Non-ISO calendars (Hebrew, Japanese eras…) — see the README's
  "Calendars — current limitation".

If yours falls in either bucket, still post it. That is exactly the evidence I need to
decide whether to build it.