nextcloud / nextcloud/calendar

`End repeat after n times` ambiguous

Open
#3,915 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

0. to triage design
Dominant language
JavaScript
Stars
1.2k
Forks
332
Avg merge
16h 13m
Merged PRs (30d)
137

Description

Hello,

I'm having a hard time understanding the implemented logic within this setting.

To make it understandable, I'm giving an example:

Let's say I create an event that will be repeated within a week 3 times (for me, that's one of my jobs, but it changes regularly).
I select the Repeat every 1 week option and choose Wed, Fri and Sat.
Now I select End repeat after 3 times.

Expected behavior: The events are created for the next three weeks
Actual behavior: The events are created for one week, because there are three events in this week

The issue with the current behavior is rather simple: I choose to set End repeat after to, let's say, 4 and I get the result, that the events for the current week are being created and the one for next Wednesday. Is this intended? Because for me it doesn't feel natural and seems to be a bug...

I'm open to feedback, maybe I just don't get the point of this setting or I'm using it wrong :)

repeat_settings

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the recurrence settings described in the issue, using multiple weekdays and an “End repeat after” count. No files, tests, or entry points are named; trace the code that expands recurring events and verify that the count is interpreted consistently across weeks. Done means the behavior matches the documented interpretation and has regression coverage.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
full-stack
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.