Skip to content

Publish: a date range keeps a trip's stops by their own dates - #38

Merged
davd-gzl merged 2 commits into
mainfrom
fix-publish-stop-dates
Sep 30, 2026
Merged

davd-gzl merged 2 commits into
mainfrom
fix-publish-stop-dates

Conversation

@davd-gzl

Copy link
Copy Markdown
Collaborator

Based on #31, whose branch it builds on; merge that first.

A trip from Paris on 2 May through Rome on 10 May to Cairo on 20 May vanishes from a site published for 8 to 31 May, and a site ending on 12 May shows Cairo. The publish range compares only the trip's first date, while each stop can now carry its own.

Each stop is now dated by its own date, or else by the last dated stop before it, or else by the trip's date, and a range keeps only the stops inside it. A trip appears when any of its stops is kept. The range is a window of days, and the site's visits and stories are already cut by day, so a trip is clipped rather than published whole. A trip without per-stop dates publishes exactly as before.

The range filtered trips by the trip's date, its first stop's day, and ignored
the per-stop dates: a trip whose later stops fell in the range was left out, and
one starting inside it was published whole, with every step on the first day.
Date each stop by its own day or the last dated stop before it, and keep the
stops inside the range.
@davd-gzl
davd-gzl changed the base branch from audit-fixes to main September 30, 2026 17:24
@davd-gzl
davd-gzl merged commit 1ebcea5 into main Sep 30, 2026
1 check passed
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.

1 participant