nextcloud / nextcloud/calendar
Handle recurring event modification/excemptions better
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 332
- Avg merge
- 16h 13m
- Merged PRs (30d)
- 137
Description
Is your feature request related to a problem? Please describe.
Yes
a) if a user modifies a event in a recurring series there are no visual indicators in the editors that the event is still part of a recurring series as the event appears to be a separate singleton event, even though the event is still technically part of that series and is saved in the same ics file.
b) if the event is a modification of a recurrence in a series, there is no way to delete the recurrence modification.
Describe the solution you'd like
It would be great if the user could,
a) see that the event is still part of a recurring series and is only a recurrence modification (visual indicator)
b) delete the recurrence modification
Describe alternatives you've considered
Manually editing and re-importing the event
Additional context
No response
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
No files or tests are named. Reproduce a modified recurring event in the calendar editor, then trace how the editor represents the recurrence modification and how deletion is handled. Done means modified occurrences are visibly identified as part of a recurring series and can be deleted without manually editing or re-importing the event.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100