-
Notifications
You must be signed in to change notification settings - Fork 392
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
Feature request - indeterminate Event.end #541
Comments
the-moog
added a commit
to the-moog/django-scheduler
that referenced
this issue
Sep 10, 2022
the-moog
added a commit
to the-moog/django-scheduler
that referenced
this issue
Feb 9, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: