Expands the kinds of dates you can enter in commentary entries!
around <date>
around <date> - <secondDate>
throughout <date> - <secondDate>
sometime <date> - <secondDate>
or just <date> - <secondDate>
All of these work alongside access/capture date (#527). They're displayed in the date column (#530), just like normal dates. (The entire date line is the tooltip hoverable.)
Technically, all combinations of date kind (or none) and - <secondDate> are valid, as far as parsing is concerned. You can do throughout 2024/04/15 and it'll, ah, "Just Work". Content code deals with semantics, here, for now, and will make sure "sometime" and "throughout" are only shown next to an actual range. There are probably nicer ways to approach this, especially if we support less specific dates (e.g. "May 2008"), but for now it's OK. ✨
Updating the unit tests has sucked the life out of us lol
Expands the kinds of dates you can enter in commentary entries!
around <date>
around <date> - <secondDate>
throughout <date> - <secondDate>
sometime <date> - <secondDate>
<date> - <secondDate>
All of these work alongside access/capture date (#527). They're displayed in the date column (#530), just like normal dates. (The entire date line is the tooltip hoverable.)
Technically, all combinations of date kind (or none) and
- <secondDate>
are valid, as far as parsing is concerned. You can dothroughout 2024/04/15
and it'll, ah, "Just Work". Content code deals with semantics, here, for now, and will make sure "sometime" and "throughout" are only shown next to an actual range. There are probably nicer ways to approach this, especially if we support less specific dates (e.g. "May 2008"), but for now it's OK. ✨Updating the unit tests has sucked the life out of us lol