You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I have an event with the attribute DURATION (https://www.rfc-editor.org/rfc/rfc5545#section-3.8.2.5), then the value DTEND is still set. This makes it an invalid event for to_ical(): DTEND and DURATION MUST not occur at the same time. This might not be so much of an issue but it could be. This should be checked.
To Reproduce
Get the events from the example with duration
See that DTEND and DURATION are both possible.
We're using Polar.sh so you can upvote and help fund this issue. We receive the funding once the issue is completed & confirmed by you. Thank you in advance for helping prioritize & fund our work.
The text was updated successfully, but these errors were encountered:
Describe the bug
When I have an event with the attribute DURATION (https://www.rfc-editor.org/rfc/rfc5545#section-3.8.2.5), then the value DTEND is still set. This makes it an invalid event for
to_ical()
: DTEND and DURATION MUST not occur at the same time. This might not be so much of an issue but it could be. This should be checked.To Reproduce
Get the events from the example with duration
See that DTEND and DURATION are both possible.
ICS file
https://github.com/niccokunzmann/python-recurring-ical-events/blob/main/test/calendars/duration-edited.ics
Expected behavior
I would opt for removing DURATION like RDATE and such, as written in https://github.com/niccokunzmann/python-recurring-ical-events?tab=readme-ov-file#events-as-list
Console output
Version:
Additional context
Suggested implementation
python-recurring-ical-events/test/calendars/issue-15-duplicated-events.ics
Line 1 in f4a90b2
python-recurring-ical-events/test/test_issue_15.py
Line 21 in f4a90b2
We're using Polar.sh so you can upvote and help fund this issue. We receive the funding once the issue is completed & confirmed by you. Thank you in advance for helping prioritize & fund our work.
The text was updated successfully, but these errors were encountered: