Skip to content

Ability to set recurrence #41

@jaredlt

Description

@jaredlt

eg. Monthly for 3 months, or monthly until {date}

There are lots of variations here.

This is partly captured by Stanislav's RRULE PR, with some additional context from me.

In general I think having an option for recurring events is a great idea.

However, I see that Yahoo also supports recurring events and ideally I would like to think about a solution that covers all possible providers. Annoyingly, it looks like Yahoo's implementation is different to RRULE but I would like to try and abstract away those differences to give a single interface for users of the gem.

Using RRULE directly is a bit of a double edged sword. On the one hand, you get the full flexibility of all the complex recurrence scenarios you could want. On the other, it relies on users having to learn how to use this gem and understanding the RRULE iCal RFC.

I'm thinking if perhaps exposing the frequency and count as their own arguments would give us more flexibility here? But equally I can see this getting complicated and I'd prefer not to reinvent the RRULE RFC which I'm sure people smarter than me spent way more time on! I'm thinking about scenarios like: Every 2 weeks on Tuesdays and Thursdays.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions