Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better recurrence instance handling and wallentry management. #194

Open
buddh4 opened this issue Jul 31, 2020 · 0 comments
Open

Better recurrence instance handling and wallentry management. #194

buddh4 opened this issue Jul 31, 2020 · 0 comments

Comments

@buddh4
Copy link
Contributor

buddh4 commented Jul 31, 2020

Recurring root event wallentry

In the latest version I've removed the wallentry of recurrent root events, since the wallentry of the recurrent root event is identical to the wallentry of the first instance. A recurring root event wallentry should rather contain information as:

xy created a recurring event starting at xy repeating every year

E.g. by using https://github.com/simshaun/recurr#rrule-to-text

Recurring instance creation

There currently is no well defined rule when recurring instances are initialized. Recurrent instances (and the related wallentries) are created when:

  • Clicking on the event in the calendar
  • Reminder process which searches for upcoming events and initializes recurrent instances

There should be a cronjob which automatically creates all upcoming recurrence instances of a month. Furthermore the
next recurrent instance should be created, once the last event has finished.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant