Repository navigation
Conversation
A stand-in for Place::Calendar with the same method signatures, so Place::Bookings runs against it unchanged on a system that has no Google or Microsoft tenant behind it. Events are kept in the module for as long as it runs, held on the organiser's calendar and every attendee's, and nothing reaches a mailbox. Used by the user-interfaces e2e stack, which now runs core, so the workplace availability panel and room check-in have a live Bookings status to bind.
This was referenced Oct 7, 2026
This branch has not been deployed
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
1 participant
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.
What
Place::Demo::Calendar, a stand-in forPlace::Calendarwith the same method signatures (list_events,get_event,create_event,update_event,delete_event,decline_event,accept_event,list_users,get_user,list_calendars), backed by memory instead of Google or Microsoft.Place::Bookingsruns against it unchanged, so a room system on an instance with no calendar tenant still gets a livestatus.Events exist for as long as the module runs. An event is held on the organiser's calendar and on every attendee's, as it is after a real invitation goes out; declining drops it from that calendar only and records the response on the other copies, deleting drops every copy. The directory
list_usersanswers from is auserssetting. Nothing reaches a mailbox.Why
The user-interfaces e2e stack is getting core so it can run drivers (PR to follow there). The first consumer is the workplace availability panel and room check-in, which bind a
Bookingsmodule'sstatus, andPlace::Bookingsneeds aCalendar_1in the system to poll. It also gives a demo system a room panel that works without a tenant.Verified
./harness report drivers/place/demo/calendar_spec.crin a worktree: 1 tested, 0 failures. The spec covers the window filter, the attendee copies, update, decline, delete and the directory.