aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorHugo Hörnquist <hugo@lysator.liu.se>2021-11-08 18:07:49 +0100
committerHugo Hörnquist <hugo@lysator.liu.se>2021-11-08 18:07:49 +0100
commite48fac299412ab4e3ff5e59439c4262473f040f0 (patch)
treec675ffd4b12370a4c127eebab60b01cc71652935
parentdoc updates. (diff)
downloadcalp-e48fac299412ab4e3ff5e59439c4262473f040f0.tar.gz
calp-e48fac299412ab4e3ff5e59439c4262473f040f0.tar.xz
Fix flat event slice for calendars.
As noted in the fidd, our simple filter-sorted-stream on event-overlaps? missbehaves in some edge cases. The new system "should" work *fingers crossed*.
Diffstat (limited to '')
-rw-r--r--module/calp/html/view/calendar.scm8
-rw-r--r--tests/annoying-events.scm59
2 files changed, 65 insertions, 2 deletions
diff --git a/module/calp/html/view/calendar.scm b/module/calp/html/view/calendar.scm
index 727fd8ba..82cccdf3 100644
--- a/module/calp/html/view/calendar.scm
+++ b/module/calp/html/view/calendar.scm
@@ -355,12 +355,16 @@
(id "xcal-data"))
,((@ (vcomponent xcal output) ns-wrap)
(map (@ (vcomponent xcal output) vcomponent->sxcal)
+ ;; A simple filter-sorted-stream on event-overlaps? here fails. See tests/annoying-events.scm
(stream->list
- (filter-sorted-stream
+ (stream-filter
(lambda (ev)
((@ (vcomponent datetime) event-overlaps?)
ev start-date
(date+ end-date (date day: 1))))
- events))))))
+ (stream-take-while (lambda (ev) (date<
+ (as-date (prop ev 'DTSTART))
+ (date+ end-date (date day: 1))))
+ events)))))))
))
diff --git a/tests/annoying-events.scm b/tests/annoying-events.scm
new file mode 100644
index 00000000..ba93b9c9
--- /dev/null
+++ b/tests/annoying-events.scm
@@ -0,0 +1,59 @@
+(((srfi srfi-41 util) filter-sorted-stream)
+ ((srfi srfi-41) stream stream->list stream-filter stream-take-while)
+ ((vcomponent base) extract prop make-vcomponent)
+ ((vcomponent datetime) event-overlaps?)
+ ((datetime) date date+ date<)
+ ((calp util) set!))
+
+(define* (event key: summary dtstart dtend)
+ (define ev (make-vcomponent 'VEVENT))
+ (set! (prop ev 'SUMMARY) summary
+ (prop ev 'DTSTART) dtstart
+ (prop ev 'DTEND) dtend)
+ ev)
+
+(define start #2021-11-01)
+(define end (date+ start (date day: 8)))
+
+(define ev-set
+ (stream
+ (event ; should be part of the result
+ summary: "A"
+ dtstart: #2021-10-01
+ dtend: #2021-12-01)
+ (event ; should NOT be part of the result
+ summary: "B"
+ dtstart: #2021-10-10
+ dtend: #2021-10-11)
+ (event ; should also be part of the result
+ summary: "C"
+ dtstart: #2021-11-02
+ dtend: #2021-11-03)))
+
+;; (if (and (date< (prop ev 'DTSTART) start-date)
+;; (date<= (prop ev 'DTEND) end-date))
+;; ;; event will be picked, but next event might have
+;; (and (date< start-date (prop ev 'DTSTART))
+;; (date< end-date (prop ev 'DTEND)))
+;; ;; meaning that it wont be added, stopping filter-sorted-stream
+;; )
+
+;; The naïve way to get all events in an interval. Misses C due to B being "in the way"
+
+(test-equal "incorrect handling of non-contigious"
+ '("A" #; "C")
+ (map (extract 'SUMMARY)
+ (stream->list
+ (filter-sorted-stream
+ (lambda (ev) (event-overlaps? ev start (date+ start (date day: 8))))
+ ev-set))))
+
+;; A correct way
+
+(test-equal "correct handling of non-contigious"
+ '("A" "C")
+ (map (extract 'SUMMARY)
+ (stream->list
+ (stream-filter (lambda (ev) (event-overlaps? ev start end))
+ (stream-take-while (lambda (ev) (date< (prop ev 'DTSTART) end))
+ ev-set)))))