Fix: Clarify RFC3339 timezone requirement for calendar events#409
Merged
steipete merged 2 commits intosteipete:mainfrom Mar 7, 2026
Merged
Fix: Clarify RFC3339 timezone requirement for calendar events#409steipete merged 2 commits intosteipete:mainfrom
steipete merged 2 commits intosteipete:mainfrom
Conversation
steipete
force-pushed
the
issue-104-rfc3339-date-format
branch
from
6442030 to
950f897
Compare
Owner
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes #104 (reported in openclaw/openclaw).
The Google Calendar API requires RFC3339 format with timezone (e.g.
2026-01-02T00:00:00-08:00). This update clarifies the help text for--fromand--toflags to indicate this requirement explicitly.Steps to reproduce:
Fix:
Updated help text in
calendar.goto mention RFC3339 with timezone.