You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First off, great guide! I learned a lot from it. After reading it, I had 2 questions from you:
Obviously, storing individual event instances is a bad idea - but what if you wanted to tie data to a specific instance date? For example, if I have a recurring event that happens every weekday (M-F) of the year. Let's say for one week, a possible attendee would not be at the one on Monday, would be there on Tuesday, not attend Wed/Thu, and would be there on Friday, and bringing a guest? And the following week, the attendance would be on completely different days. How could I tie that information to a specific instance without having an actual record for that instance?
Weekday only recurrence pattern
This is very similar to the question here: Multiple days on a recurring week #4
--
But I was wondering if there was a way to represent events that recurred on weekdays only, but have a single event? If I'm doing weekdays only, I don't really want a Monday event, Tuesday event, Wednesday event, etc. The other option I suppose would be to make the "day" field an array, but, yuck?
Thanks in advance for the advice!
The text was updated successfully, but these errors were encountered:
Hi, @claym, hope you are doing ok!
I'm not super savvy on the library, but I've forked and have been using it for 1+ year, and it has suited me well, so I'll try to answer your question with the knowledge I have.
I ended up creating a new table, with event_id + start_date to handle this situation, but in my case, the user must go 1 by 1 to "join" a specific date. For what I understand, you want the user to be able to do similar to calendar, answering YES to "this and following events", is that correct? What I learnt is, Google probably saves this info in another table and has some kind of worker marking yes for the next X events (you can check that via email, when a user says YES or NO recurrently, you receive 30 emails give or so). But I don't think it's out of the box
Not sure if I completly understood, you want to have a single event instance, ocurring recurrently only on weekend?
First off, great guide! I learned a lot from it. After reading it, I had 2 questions from you:
Obviously, storing individual event instances is a bad idea - but what if you wanted to tie data to a specific instance date? For example, if I have a recurring event that happens every weekday (M-F) of the year. Let's say for one week, a possible attendee would not be at the one on Monday, would be there on Tuesday, not attend Wed/Thu, and would be there on Friday, and bringing a guest? And the following week, the attendance would be on completely different days. How could I tie that information to a specific instance without having an actual record for that instance?
Weekday only recurrence pattern
This is very similar to the question here: Multiple days on a recurring week #4
--
But I was wondering if there was a way to represent events that recurred on weekdays only, but have a single event? If I'm doing weekdays only, I don't really want a Monday event, Tuesday event, Wednesday event, etc. The other option I suppose would be to make the "day" field an array, but, yuck?
Thanks in advance for the advice!
The text was updated successfully, but these errors were encountered: