There is separate jira issue for recurrence support I would create everything for non-recurring appointnnents And add recurrence support later on
WBR, Maxim (from mobile, sorry for the typos) On Jun 3, 2016 22:05, "Ankush Mishra" <ankushmish...@gmail.com> wrote: > I had a specific doubt regarding this, specifically the Recurrence of the > Events. Note, over here events and Appointments are synonymous. Sometimes, > the RRULE as it's stated can be like this: > > RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10 > > which basically states that the event repeats for every last Sunday of > October every year. Other examples are : > > RRULE:FREQ=YEARLY;INTERVAL=2;BYMONTH=1;BYDAY=SU;BYHOUR=8,9; > BYMINUTE=30 > > which is for every Sunday in January at 8:30 AM and 9:30 AM, every other > year. So, as you can see things can get pretty complex with these rules. > And both of these examples are from the RFC2445 for iCalendar Objects. > > My problem is when I convert to Appointment Objects with recurrences, > there is no current possible way of doing something like the previous two > examples, thus, I was wondering, on how to proceed along on this situation? > > One solution I came up with is to use the CalDAV REPORT method's > Calendar-Data expand property, which expands all the recurring events in > separate events i.e. say we have an event with > RRULE:FREQ=DAILY;UNTIL:[some-end-time]. When expanded it will give us all > the events for each day (Since it's daily) up until the end time we > specify. Thus, making it possible to easily store the event. > > Now the range for which we need the the expanded events has to specified > in the query. Other than that, it would also mean, that we will have more > number events instead of one event which has a recurrence property. Should > I handle this differently or does this method work, i.e. expansion of > events? > > Ankush Mishra >
