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
There are use cases where we don't know an event end.
e.g. If the event was a party it is ongoing and we don't know when the party ends.
Currently the Event model requires and end date, though it is barely used by the code (only to generate Occurances)
Suggestion:
Add a 'long grass' end date, e.g. 99 years and a field that indicates this is a best guess.
Then we can update the end date later and fixup the occurances
The text was updated successfully, but these errors were encountered:
the-moog
added a commit
to the-moog/django-scheduler
that referenced
this issue
Sep 10, 2022
There are use cases where we don't know an event end.
e.g. If the event was a party it is ongoing and we don't know when the party ends.
Currently the Event model requires and end date, though it is barely used by the code (only to generate Occurances)
Suggestion:
Add a 'long grass' end date, e.g. 99 years and a field that indicates this is a best guess.
Then we can update the end date later and fixup the occurances
The text was updated successfully, but these errors were encountered: