Skip to content

Parse Wilton's times written with a colon - #757

Merged
alistairjcbrown merged 1 commit into
mainfrom
ccr-ca4704c8-4cgdo2
Oct 7, 2026
Merged

alistairjcbrown merged 1 commit into
mainfrom
ccr-ca4704c8-4cgdo2

Conversation

@alistairjcbrown

Copy link
Copy Markdown
Member

Follow-up to #756. With the year now parsed, the wiltons.org.uk transform failed on the next row:

Error: Unable to parse performance date: Sat 6 Feb 2027 2:30 pm

Wilton's writes most times as 7 pm or 7.30 pm, but some use a colon (2:30 pm). The time format only knew the dot, so the colon is now normalised to a dot before parsing.

Verification

  • Ran the transform over the Wilton's asset from the latest data-retrieved release (20261007.191751): all 9 films and 10 performances parse. Every format in that data is covered: dates with and without a year, and times as N pm and N:NN pm.
  • npm test -- cinemas/wiltons.org.uk and lint pass. The recording has no year or colon rows, so its snapshot is unchanged.

🤖 Generated with Claude Code

https://claude.ai/code/session_01PPQC7pUHLSSD6ayU5cZiBQ


Generated by Claude Code

Some Wilton's times use a colon ("2:30 pm") rather than a dot ("7.30
pm"), which the time format rejected, failing the transform.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PPQC7pUHLSSD6ayU5cZiBQ
@alistairjcbrown
alistairjcbrown merged commit f70b5ab into main Oct 7, 2026
2 checks passed
@alistairjcbrown
alistairjcbrown deleted the ccr-ca4704c8-4cgdo2 branch October 7, 2026 22:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants