-
-
Notifications
You must be signed in to change notification settings - Fork 187
Fix Google Calendar Time Range #356
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
- Add time range validation in events() and freeBusy() methods - Ensure timeMax is always after timeMin before API calls - Enhanced error logging for time range validation failures - Add context logging with calendar/schedule details for debugging
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Requesting review from @JeanMeijer who has experience with the following files modified in this PR:
|
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Join our Discord community for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR/Issue comments)Type Other keywords and placeholders
CodeRabbit Configuration File (
|
|
Tembo is working on fixing this failing workflow: |
Description
Resolve Google Calendar API error caused by empty time range parameters
Changes
Summary by cubic
Fixes Google Calendar timeRangeEmpty errors by validating timeMin/timeMax and sending only valid UTC instants to the API. Also improves error logs with helpful context for faster debugging.