The casual parsing is a little too aggressive to my use case, as it thinks that "today" should be parsed.
I could use strict parsing, but I saw this problem: if I write "tomorrow 5pm" Chrono parses only "5pm" and think that it is today (not tomorrow).
I suggest:
Create a parsing option "requireTime" which parses casually, but so that the time has to be defined in one way or another. Like "tomorrow 5pm" which has the date and the time.
Problems:
I suggest:
Create a parsing option "requireTime" which parses casually, but so that the time has to be defined in one way or another. Like "tomorrow 5pm" which has the date and the time.