Editing a recurring event removes previous instances
Open
Nobody has claimed this yet.
cat:recurrence
type: bug
- Dominant language
- Python
- Stars
- 3.1k
- Forks
- 233
- Avg merge
- 1h 44m
- Merged PRs (30d)
- 1
Description
Steps to repro:
- Create a recurring event.
- Run
ikhal, go to a non-first entry, and edit the time to something different - Save
Result:
- Any entries previous to the edited one are deleted.
Expected:
- All entries should continue to exist:
- I suppose that we'd want previous ones to be edited too.
I actually noticed this when editing a recurring even that I've had around for a week; I updated the time (it's actually shorter than I'd scheduled), and all the previous entries disappeared. This is most likely because we store the edited entry as the first one.
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
Start at the ikhal entry point and reproduce the recurring-event edit with a non-first occurrence. Trace how the edited occurrence is stored and verify that saving preserves all earlier entries; the expected result is that they remain, with the issue noting they may also need the new time.
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
- 48/100