Repository navigation
calendar 0.2.0: rows are the shared event-v1 class (#177 item 5) - #253
Merged
Merged
Conversation
- 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>
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
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.
Moves the Google Calendar drive app onto the shared
event-v1class of #177 (item 5).ontology-kit's strict resolver. The Google extras stay in the app's own ontology and are declared asrow-extras(atomic-server #1849).event-v1in 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 retargetsclasstypeand addsevent-v1torenders.event-v1tables (reached through Add view): the app shows the rows read-only and syncs nothing. "Sync this table" (§6.2 item 14) is not built.subjectvalidator that blocks money 0.4.0: sync into the shared bank-transaction-v1 class (#177 item 8) #252 applies only to sandbox importer destinations./changes,afterCommit) is in the pin but not reachable from a drive-app frame, so compare-on-open stays.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-madeevent-v1table.enabled: false(ontology gate). Usertest isusertest-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:
Part of #177; doesn't close it.
🤖 Generated with Claude Code