Skip to content

calendar 0.2.0: rows are the shared event-v1 class (#177 item 5) - #253

Merged
michielbdejong merged 1 commit into
mainfrom
claude/calendar-event-v1
Oct 1, 2026
Merged

michielbdejong merged 1 commit into
mainfrom
claude/calendar-event-v1

Conversation

@michielbdejong

Copy link
Copy Markdown
Contributor

Moves the Google Calendar drive app onto the shared event-v1 class of #177 (item 5).

  • Fields: shared fields are the published Pages properties, read through ontology-kit's strict resolver. The Google extras stay in the app's own ontology and are declared as row-extras (atomic-server #1849).
  • First open moves the app's own table and rows onto event-v1 in place, so unsent edits survive (Design: plugins sync into shared row classes, and plugin views work on any table of that class ("option 4") #177 Q10). It then retargets classtype and adds event-v1 to renders.
  • Other event-v1 tables (reached through Add view): the app shows the rows read-only and syncs nothing. "Sync this table" (§6.2 item 14) is not built.
  • Day-only rows are drawn as all-day events.
  • Spike: a drive app can write tables and rows with external-subject classes and properties at pin a12b74a. The subject validator that blocks money 0.4.0: sync into the shared bank-transaction-v1 class (#177 item 8) #252 applies only to sandbox importer destinations.
  • README: the host side of H6 (/changes, afterCommit) is in the pin but not reachable from a drive-app frame, so compare-on-open stays.
  • E2E: uses the real GitHub Pages subjects (needs network access to ontola.github.io), checked first with ontology-kit/served.mjs, which is the same file as in money 0.4.0: sync into the shared bank-transaction-v1 class (#177 item 8) #252. A new test covers a hand-made event-v1 table.
  • Release: app 0.2.0 (122,135 bytes, limit 132 KiB). The catalog entry stays enabled: false (ontology gate). Usertest is usertest-9.

Checks: calendar typecheck, unit (164 tests) and e2e (5/5, three runs). Also: tooling tests 248/248, apps and ontology checks, certify, e2e tsc, oxlint (0 errors) and oxfmt.

Not verified:

  • The in-place migration from a 0.1.4 install (unit-tested only).
  • Behaviour during a Pages outage.
  • Live Google.

Part of #177; doesn't close it.

🤖 Generated with Claude Code

- Shared fields (Day, End day, All day, Start, End, Location, Notes) are
  the published event-v1 properties, inlined from ontology-kit/terms.mjs
  and read through ontology-kit's strict resolver only (app/fields.ts).
  The Google extras stay Properties of the app's own ontology.
- First open (app/adopt.ts): moves the app's own table's rows onto
  event-v1 in place (values copied from 0.1.x's own Properties, isA
  rewritten), so unsent edits survive (#177 Q10); then retargets the
  table's classtype, adds event-v1 to the App's renders and declares the
  four row extras as row-extras (atomic-server #1849).
- On another event-v1 table (via Add view) the app shows the rows, read
  only, and syncs nothing ("Sync this table" is not built).
- A row with a Day and no Start or End is drawn as an all-day event.
- README: the H6 host side exists at the pin (/changes, afterCommit) but a
  drive app's frame cannot reach it, so compare on open stays.
- e2e uses the real Pages subjects, checked first with
  ontology-kit/served.mjs (copied unchanged from #252), and adds the app
  as a view of a hand-made event-v1 table; counts only the signed-in
  user's proxy connections (the lane's tests run in parallel).
- Release: apps/calendar/0.2.0, catalog stays enabled: false, usertest-9,
  size limit 132 KiB (measured 122,135 bytes).

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