Planned modifications to the script, most of which are aimed at improving the setup experience
[x] #38
[x] #39
[x] #40
The reason for the full-sync refactoring is so that the user can execute a full-sync operation without needing to modify anything in the script. This reduces anxiety for those that are unfamiliar with coding and helps ensure that the full-sync option isn't accidentally left on. Having a standalone function can also help with some of the time out errors by skipping the Notion to GCal synchronization direction. This sync direction is not required during initial setup since we expect one to start with a clean database anyways. It is also not necessary for debugging the time out errors that happen for some folks during this initial setup since the primary cause of the error is excessive compute time with a full-sync pulling from GCal.
Planned modifications to the script, most of which are aimed at improving the setup experience
The reason for the full-sync refactoring is so that the user can execute a full-sync operation without needing to modify anything in the script. This reduces anxiety for those that are unfamiliar with coding and helps ensure that the full-sync option isn't accidentally left on. Having a standalone function can also help with some of the time out errors by skipping the Notion to GCal synchronization direction. This sync direction is not required during initial setup since we expect one to start with a clean database anyways. It is also not necessary for debugging the time out errors that happen for some folks during this initial setup since the primary cause of the error is excessive compute time with a full-sync pulling from GCal.