Align HEY integration with hey-cli v1.0 / hey-sdk 0.21 - #60
Closed
is2b007 wants to merge 1 commit into
Closed
Conversation
Use the official calendar event form API (including set_time_zone), week-period reads for expanded recurrences, date-only todo writes, canonical email box paths, and time-track start/stop payloads. Timeboxes now PATCH an existing HEY event instead of delete-and-recreate. Co-authored-by: is2b007 <is2b007@users.noreply.github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Owner
Author
|
Landed on |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Align Daybreak’s HEY client with the current hey-cli v1.0 / hey-sdk 0.21 API so existing features use the official paths and payloads instead of form/JSON fallbacks.
What changed
Calendar events. Writes now go to
POST/PATCH /calendar/events.jsonas form data, withcalendar_event[set_time_zone]=1so zone names are not dropped (times were landing as UTC). Responses accept a JSON recording body or a redirect id. Recurring occurrences use/calendar/events/:id/occurrences/:date.json. Timeboxes PATCH an existing HEY event instead of delete-and-recreate.Week timeline. Sync reads
GET /calendar/weeks/:date.jsonfirst so recurring events expand into the week, then still supplements with per-calendarrecordings.jsonfor calendars the user has switched off in HEY. Occurrences are stored as{series_id}:{YYYY-MM-DD}.Todos. Create sends a bare
YYYY-MM-DD. Delete uses/calendar/todos/:id.json. Newupdate_todois used when a sometime task already has a mirrored id.Time tracking. Start sends no body and treats 409 as “already running” (adopts
GET /calendar/ongoing_time_track.json). Stop wraps{ calendar_time_track: { ends_at, category_title } }.Email boxes. Canonical paths:
/laterbox.json,/asidebox.json,/trailbox.json. Pagination followsnext_history_urlor a same-originLink: rel=nextheader. Email triage stays local.Connect page. Official installer (
curl -fsSL https://hey.com/install-cli | bash) andbrew install --cask basecamp/tap/hey.Out of scope
Remote email writes, ActionCable change feeds, habits/contacts/screener/compose.
Tests
Full suite: 146 runs, 0 failures.