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
fix: accept_invite() falls back to client username when calendar-user-address-set is unavailable
When the server does not expose the calendar-user-address-set property
(RFC6638 §2.4.1), accept_invite() (and decline_invite(),
tentatively_accept_invite()) now fall back to the client username as
the attendee email address. A NotFoundError with a descriptive message
is raised when the username is also not an email address.
Fixes#399
Copy file name to clipboardExpand all lines: CHANGELOG.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,6 +21,7 @@ This project should adhere to [Semantic Versioning](https://semver.org/spec/v2.0
21
21
*`Calendar.get_supported_components()`
22
22
* raised `KeyError` when the server did not include the `supported-calendar-component-set` property in its response. RFC 4791 section 5.2.3 states this property is optional and that its absence means all component types are accepted; the method now returns the RFC default `["VEVENT", "VTODO", "VJOURNAL"]` in that case, trimmed by any known server limitations from the compatibility hints (e.g. if `save-load.todo` is `unsupported`, `VTODO` is excluded). Fixes https://github.com/python-caldav/caldav/issues/653
23
23
* async path returned an unawaited coroutine instead of the actual result.
24
+
*`accept_invite()` (and `decline_invite()`, `tentatively_accept_invite()`) now fall back to the client username as the attendee email address when the server does not expose the `calendar-user-address-set` property (RFC6638 §2.4.1). A `NotFoundError` with a descriptive message is raised when the username is also not an email address. Fixes https://github.com/python-caldav/caldav/issues/399
0 commit comments