Skip to content

docs: say what a pattern means when the clock changes - #25

Merged
tkoehlerlg merged 1 commit into
mainfrom
docs/timezone-semantics
Sep 24, 2026
Merged

tkoehlerlg merged 1 commit into
mainfrom
docs/timezone-semantics

Conversation

@tkoehlerlg

Copy link
Copy Markdown
Contributor

Three one-liners in the README, each where a reader meets a surprise the docs were silent about.

Weekly Availability — a pattern names times on your clock, not instants. 09:00–17:00 is eight hours on the clock every week, which is seven or nine elapsed hours on the two days a year the zone changes offset, the same thing a recurring block does in Google Calendar or Outlook. A wall time the clock skips is not offered; one it repeats is offered twice.

Daily windows — the window is measured on the caller's local day, so an evening window crossing UTC midnight (20:00–24:00 in New York) keeps its slots. That one used to be false: those slots were dropped.

Managing busy times — validation now throws on an unparseable or inverted interval, and the Dates are copied, so mutating your input or getBusyTimes() output no longer changes the answers.

Documents behaviour shipped in #24; no code changes. package.json stays at 0.7.1, which is still ahead of npm's 0.7.0.

🤖 Generated with Claude Code

Three places a reader meets a surprise and the README was silent: that an
availability pattern names wall-clock times, so a shift is eight hours on the
clock and seven or nine elapsed on a transition day; that a daily window is
measured on the caller's day, so an evening window crossing UTC midnight keeps
its slots; and that busy times are now validated and copied on the way in, so a
bad Date throws rather than being scheduled against.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@codecov

codecov Bot commented Sep 24, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@tkoehlerlg
tkoehlerlg merged commit 9ad2715 into main Sep 24, 2026
6 checks passed
@tkoehlerlg
tkoehlerlg deleted the docs/timezone-semantics branch September 24, 2026 21: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.

1 participant