-
Notifications
You must be signed in to change notification settings - Fork 11
Calendar Integration Schema
Every schedule has a calendar and a Google Meet. Each schedule will hold the calendar's ID and the JSON data relating to the meet
Google Meets are generated by creating a dummy event with a request to create a hangoutsMeet. The conferenceData is then extracted from the response and stored on the schedule's model.
When a timeslot first gets a reservation, an event is created on the schedule's calendar. Google allows us to set a custom made ID for a calendar event, so we generate our own ID using the timeslot's data, meaning we don't need to store the event's ID on the database. The reason why we don't store the event's ID is to avoid having NULL values in our database.
In each timeslot's event, every reservation will be recorded in the event's "attendees" field. Google will automatically notify each attendee by email.
- Things we use
- Heroku Maintaining
- Creating a dev environment
- Documentation Guidelines
- Calendar Integration Schema