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

Support RRULE (recurring events) #39

Closed
kfdm opened this issue Nov 29, 2015 · 4 comments
Closed

Support RRULE (recurring events) #39

kfdm opened this issue Nov 29, 2015 · 4 comments
Labels

Comments

@kfdm
Copy link

kfdm commented Nov 29, 2015

My google calendar has a lit of recurring events but it seems like they're ignored. Does bookingjs know how to read recurring events or does it only understand unique events?

@laander
Copy link
Contributor

laander commented Nov 29, 2015

Hi @kfdm

Booking.js uses the Timekit API to sync events with Google. If it encounters a recurring event, it treats each event instance as a regular event, thus the timeslot it occupies are considered busy in the FindTime (availability) algorithm.

From your description, it seems like this is not handled as expected. Could you send me an e-mail (la@timekit.io) with your Google email and a screenshot of the recurring events form the Google Calendar UI (or equivalent)? Then i can dig a bit 👍

@kfdm
Copy link
Author

kfdm commented Nov 30, 2015

Thanks. I've emailed you with the information. :)

@alialkhatib
Copy link

This is a similar but seemingly different question, so my apologies if it should be a separate issue - is it reasonable to extend bookings so that appointments are potentially recurring? I can think of a couple of use cases where it would be preferable to set recurring appointments every week or month (compared to manually booking every appointment).

I'm imagining a dropdown option in the booking form field giving options like ["once","weekly","monthly","annually"] or something (I imagine someone will make an argument for including "daily" but maybe we can hash that out or provide some options on the developer's side to expose frequencies).

@laander
Copy link
Contributor

laander commented Feb 4, 2016

Moving the feature request by @alialkhatib to it's own thread (#73) and closing this

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

No branches or pull requests

3 participants