virajvchavan / calendar_app Goto Github PK

https://developers.google.com/calendar/v3/sync#full_sync_required_by_server

Possible use case:
When user logs in for the first time, currently all of his calendars with all the events are loaded all at once, and then only user is redirected to auth/:provider/callback.

If user has thousands of events, it may take a long time to load the events, and even lead to a timeout before redirecting to our website. It'll be better to start a background job and then return a success response immediately. Then just find a way to show the newly loaded events as they come. (websockets?)

https://developers.google.com/calendar/v3/version-resources

Current test cases cover only validations, associations and some other standard things.
Need test cases for the following and more:

• Controllers
• GoogleCalendarApi
• User creation during OAuth flow

• Use partial responses for calendar API (https://developers.google.com/calendar/performance#partial-response). Fetch only what is needed
• Use background jobs (#5)

A user may have hundreds of events under one calendar

Currently there is no abstraction over Google Calendar API's registered webhooks (Notification channels).

We are relying on custom tokens sent on each webhook registration to identify which resources to update. Along with that we're storing sync_tokens for resources in their respective models.

Currently there is no way to cancel a webhook because we are not persisting its channel_id. Which means even if we delete a resource from our system, we'll keep getting callback requests for those resources.

A new model called 'NotificationChannel' can provide a simple interface for dealing with this. A NotificationChannel can belong to any resource that is being watched. This will also eliminate the need to store sync_tokens in respective models.

Also, When fetching 'Daily Events' for a user:
Since we're storing all start and end times in UTC in the database, and the user may be in any timezone, how to query the start and end times for that user in his timezone?