v1.4.1

Highlights

• Date formats checked up front: a date_offset whose format can't parse its base column now fails validate and names the layout to set:

  date_offset: base field "start_date" is written as "2006-01-02", which format "2006-01-02T15:04:05Z07:00" cannot parse; set format: "2006-01-02"
  

  This covers base columns written by time, time_seq, or date_offset, in the same row or exposed from a driven_by parent. Dates from other generators (a pick of date strings) are still parsed per row, and that error now says to set format to the field's layout.

Upgrading from v1.4.0

• Output: unchanged; every example plan is byte-identical to v1.4.0.
• Stricter validation: such plans used to pass validate and fail during generation (exit 2). They now fail validation (exit 1) with the new issue code date_format_mismatch.

Changelog

Bug fixes

• 27f2b7a: fix: catch date_offset format mismatches early (@compuficial)