REQUEST-STATUS is defined in RFC 5545 section 3.8.8.3: https://www.rfc-editor.org/rfc/rfc5545#section-3.8.8.3
In the codebase it is stored under the key RSTATUS. It is a TEXT property that can appear in VEVENT, VTODO, VJOURNAL, and VFREEBUSY. Each value is semicolon-separated: statcode;statdesc[;extdata]. Multiple values per component are allowed.
Currently it is listed in the multiple tuple of Event, Todo, Journal, and FreeBusy, but there is no Python property in attr.py. The parser handles it generically. Please add a getter, setter, and deleter in the style of the other properties. Return type should be list[str]. A note that append and such do not work must be in the docs. The multi_string_property helper in attr.py (line 2493) already handles the get/set/del pattern for multi-value TEXT properties. See refids_property for an example.
Avoid long comments with AI. Write a short one yourself.
REQUEST-STATUS is defined in RFC 5545 section 3.8.8.3: https://www.rfc-editor.org/rfc/rfc5545#section-3.8.8.3
In the codebase it is stored under the key
RSTATUS. It is a TEXT property that can appear in VEVENT, VTODO, VJOURNAL, and VFREEBUSY. Each value is semicolon-separated: statcode;statdesc[;extdata]. Multiple values per component are allowed.Currently it is listed in the
multipletuple of Event, Todo, Journal, and FreeBusy, but there is no Python property in attr.py. The parser handles it generically. Please add a getter, setter, and deleter in the style of the other properties. Return type should be list[str]. A note that append and such do not work must be in the docs. Themulti_string_propertyhelper in attr.py (line 2493) already handles the get/set/del pattern for multi-value TEXT properties. Seerefids_propertyfor an example.Avoid long comments with AI. Write a short one yourself.