Fix CLI datetime parsing to default date-only strings to midnight instead of current time #199
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The CLI was incorrectly interpreting date-only strings like
--until 2025-08-06
by using the current time instead of defaulting to 00:00:00 (midnight). This caused unexpected behavior where users expected the date to represent the start of the day.Problem
When using the CLI with date-only parameters, the
FuzzyDateTime
class was usingparsedatetime.Calendar().parseDT()
which defaults to the current time for the time component:Solution
Added intelligent detection of date-only strings using regex patterns to distinguish between:
2025-08-06
,2025/08/06
,08/06/2025
,08-06-2025
in 1 hour
,tomorrow
,in 2 days
For date-only strings, the parser now uses a
sourceTime
parameter set to midnight, ensuring consistent behavior. Relative time expressions continue to use the current time as the reference point.Changes
FuzzyDateTime.convert()
in_cli_types.py
to detect date-only patternsTesting
Fixes #198.
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.