-
Notifications
You must be signed in to change notification settings - Fork 85
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
Date and time are converted to NAN in Google Calendar #84
Comments
When I change the start and end in the object (options) to:
it works for the other calendars. But for Google Calendar, I get:
|
Hi, Yes, the docs appear to have the wrong date format. I'm opening a PR to fix this now. As you pointed out, the dates should be in ISO 8601. I will investigate the Google Calendar issue. |
Hi mate, Thanks. It's only in Google Calendar. Hope it gets fixed soon |
Fixes issue with Google Calendar returning NaN... for timestamps. Updates documentation to reflect proper ISO 8601 handling of timestamp formats. Updates incorrect timestamp formats for recurrences and Yahoo calendar. Fixes Outlook calendar base URL.
Fixes issue with Google Calendar returning NaN... for timestamps. Updates documentation to reflect proper ISO 8601 handling of timestamp formats. Updates incorrect timestamp formats for recurrences and Yahoo calendar. Fixes Outlook calendar base URL.
Fixes issue with Google Calendar returning NaN... for timestamps. Updates documentation to reflect proper ISO 8601 handling of timestamp formats. Updates incorrect timestamp formats for recurrences and Yahoo calendar. Fixes Outlook calendar base URL.
@hzrcan should be fixed now in version 4.1.2 |
Hi,
When I use the Datebook I get the startdate and enddate as
NaNaNaNTaNaNaN/NaNaNaNTaNaNaN
for each calendar.It returns:
https://calendar.google.com/calendar/r/eventedit?text=Happy+Hour&details=Let%27s+blow+off+some+steam+from+our+weekly+deployments+to+enjoy+a+tall+cold+one!&location=The+Bar,+New+York,+NY&dates=NaNaNaNTaNaNaN/NaNaNaNTaNaNaN&recur=RRULE:FREQ%3DWEEKLY;INTERVAL%3D2
The text was updated successfully, but these errors were encountered: