all-day events with edit command
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.1k
- Forks
- 233
- Avg merge
- 1h 44m
- Merged PRs (30d)
- 1
Description
Hello,
when using the edit command, I'm unsure of the correct way of setting the datetime for all-day events.
When using the new command and as its argument just the date (without time and end date) or use a keyword (today, tomorrow, etc), the event will show correctly as an all-day event (i.e. not displaying times associated with it). This also happens when marking all-day with ikhal.
However, when I use edit, choose to set the datetime and input the all-day event as I used with new, the event will display its time at 00:00-24:00.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the discrepancy in the edit command using a date-only value or a keyword, then compare it with the equivalent new command and the all-day behavior in ikhal. Trace the datetime parsing and display path for edit; done means an all-day event edited this way no longer displays `00:00-24:00.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100