-
Notifications
You must be signed in to change notification settings - Fork 98
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
Possible arguments to calendar.save_event()
and calendar.search()
is poorly documented
#253
Comments
Parameters for search are listed well. The same for
confuses me as well. Edit: This? Edit: Another edit: |
Did anyone manage to add an alarm using the props? The following is listed, but doesn't seems to work.
|
Is that when doing I was working a bit on alarms at one point, but ran out of time ... I think that work is still in a separate branch (with a draft pull request and an issue attached). |
#221 that was. And #132 (comment) |
No problem, I can use Ical data to add I had the following error when adding the event, but that was caused by extra linebreaks at the beginning and ending of the Ical data. Removed the linebreaks in the Ical data, now it is working fine.
|
That's not an error, that's a warning. It's a bit of a bugger, a caldav library is expected to pass the icalendar data unmodified, still I want to be flexible and pragmatic and do whatever I can for things to just work - so that includes fixing broken icalendar data. At some point I decided to add a warning about it - it's been a bugging problem particularly for some HomeAssistant users that gets lots of those messages stuck in the log :-) |
... and there is
calendar.save_todo
andcalendar.save_journal
as well.The text was updated successfully, but these errors were encountered: