Skip to content

calendar 0.3.0: Sync this table to Google Calendar (#177 item 14) - #272

Merged
michielbdejong merged 1 commit into
mainfrom
claude/calendar-sync-existing-table
Oct 2, 2026
Merged

michielbdejong merged 1 commit into
mainfrom
claude/calendar-sync-existing-table

Conversation

@michielbdejong

Copy link
Copy Markdown
Contributor

On an event-v1 table the Calendar app is a view of (added with Add view), the "Not synced" banner now offers Sync this table to Google Calendar.

  • Grant: the app asks for the host's "Allow editing" when the row grant doesn't cover its declared row-extras (atomic-server #1849, in pin a12b74a).
  • Binding: a grant never writes the table, so the calendar choice lives on a resource under the App (synced-table, google-calendar-id, -meta).
  • Sync: the same compare-on-open, review-before-send, If-Match and conflict rules as on the app's own table, with bookkeeping on the rows (Design: plugins sync into shared row classes, and plugin views work on any table of that class ("option 4") #177 decisions 1–10).
  • On such a table:
    • existing rows stay local only and rows are never deleted;
    • the table's name and class are never written;
    • a revoked grant pauses the sync, with no proxy calls.
  • No host change was needed.

Tests:

  • Unit: app/syncTable.test.ts (10 tests, with the fake store enforcing the pin's grant scope), plus a view test and the host-operations test.
  • E2E: hand-made table → Add view (Read-only) → Sync this table → Allow editing → connect → import → a Notes edit sent as a PATCH of only description, with If-Match.

Release: apps/calendar/0.3.0 (127,611 bytes, limit 138 KiB). The catalog entry stays enabled: false. Usertest calendar is usertest-10. The pattern for issue-tracker and timesheets is documented in integrations/README.md ("Syncing a table the app didn't make").

Checks: calendar typecheck, unit (175) and e2e (6/6). Also: tooling tests 251/251, apps and ontology checks, certify, e2e tsc, oxlint (0 errors) and oxfmt. Not verified against live Google.

Part of #177 (item 14, calendar only).

🤖 Generated with Claude Code

On an event-v1 table the app is a view of, the "Not synced" banner offers
"Sync this table to Google Calendar". The app asks for the host's "Allow
editing" when the row grant is missing or doesn't cover its declared
row-extras (atomic-server #1740/#1849, pin a12b74a), keeps the calendar
choice on a binding resource under the App (synced-table, google-calendar-id,
-meta), since a grant never writes the table, then syncs that table with the
same compare-on-open, review-before-send, If-Match and conflict rules as its
own table. Bookkeeping stays on the rows. Rows already in the table stay
local only; no row is ever deleted there; a revoked grant pauses the sync.

Unit tests (syncTable.test.ts, a fake store enforcing the pin's grant scope),
a view test, an e2e (hand-made table, Add view read-only, Sync this table,
Allow editing, connect, import, a Notes edit sent with If-Match). Published
as apps/calendar/0.3.0 (127,611 bytes, limit 138 KiB); catalog stays
enabled: false; usertest VERSIONS calendar usertest-10. The pattern is
documented in integrations/README.md for issue-tracker and timesheets.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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