Pull remote calendar information on a month by month basis. (Fixes #186) #206
Conversation
This file contains 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
devmount
approved these changes
Dec 11, 2023
Co-authored-by: Andreas <mail@devmount.de>
|
Ah right, that makes sense! Thanks! |
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.
Very simple fix, I think we originally pulled an entire year to save on google api calls, but I'm not sure that matters. I don't cache the calendar data as we don't have a way of knowing if its been updated without doing the entire request.
Eventually we'll store this data and have google tell us what's new (with occasionally double checks on our side) but for now this should speed things up quite a bit!