The only reason it is a draft is that I didn’t bring a fix, only expose a shortcoming.
It seems that mldoc cannot associate a schedule or deadline timestamp to a heading, and this might be the root cause for the issue with logbooks and repeaters in Logseq
The tests only make sure that headlines with schedules and/or deadlines are parsed "correctly" (meaning that the headline object has the corresponding properties)
It also seems that it’s hard to parse ranges for timestamps, at least I wasn’t able to express the "expected" result that I wanted
The only reason it is a draft is that I didn’t bring a fix, only expose a shortcoming.
It seems that mldoc cannot associate a schedule or deadline timestamp to a heading, and this might be the root cause for the issue with logbooks and repeaters in Logseq
The tests only make sure that headlines with schedules and/or deadlines are parsed "correctly" (meaning that the headline object has the corresponding properties)
It also seems that it’s hard to parse ranges for timestamps, at least I wasn’t able to express the "expected" result that I wanted