diff options
| author | Hugo Hörnquist <hugo@lysator.liu.se> | 2020-03-29 23:25:20 +0200 |
|---|---|---|
| committer | Hugo Hörnquist <hugo@lysator.liu.se> | 2020-03-29 23:25:20 +0200 |
| commit | 9d471cd6cdd182c01bb6d7a7c7e0318a2daa3372 (patch) | |
| tree | 0bcc9ef8150e56a810704c6f27dc02aa23104609 /module/vcomponent/recurrence/parse.scm | |
| parent | Change some calendar names in example config. (diff) | |
| download | calp-9d471cd6cdd182c01bb6d7a7c7e0318a2daa3372.tar.gz calp-9d471cd6cdd182c01bb6d7a7c7e0318a2daa3372.tar.xz | |
Clarify error on bad RRULE's.
Diffstat (limited to 'module/vcomponent/recurrence/parse.scm')
| -rw-r--r-- | module/vcomponent/recurrence/parse.scm | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/module/vcomponent/recurrence/parse.scm b/module/vcomponent/recurrence/parse.scm index a93b81df..97e5e980 100644 --- a/module/vcomponent/recurrence/parse.scm +++ b/module/vcomponent/recurrence/parse.scm @@ -48,8 +48,9 @@ `(else ,@body))) cases)))) -;; UNTIL must have the exact same value type as the DTSTART of the event from which -;; this string came. I have however seen exceptions to that rule... +;; RFC 5545, Section 3.3.10. Recurrence Rule, states that the UNTIL value MUST have +;; the same type as the DTSTART of the event (date or datetime). I have seen events +;; in the wild which didn't follow this. I consider that an user error. (define* (parse-recurrence-rule str optional: (datetime-parser parse-datetime)) (fold (lambda (kv o) |