-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Documentation for ScheduledEvent.recurrence_rule #7058
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
Conversation
Note, awaiting a PR merge in the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@DV8FromTheWorld added a suggestion for the broken link 🚀
- The following are current allowed "sets" | ||
- Monday - Friday (`[0, 1, 2, 3, 4]`) | ||
- Tuesday - Saturday (`[1, 2, 3, 4, 5]`) | ||
- Sunday - Thursday (`[6, 0, 1, 2, 3]`) | ||
- Friday & Saturday (`[4, 5]`) | ||
- Saturday & Sunday (`[5, 6]`) | ||
- Sunday & Monday (`[6, 0]`) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
one interesting thing we could note here is that we store the times in UTC. This means that a user in a different timezone may schedule an event for their Saturday/Sunday but this will actually be stored as Sunday/Monday. That's why those types of sets are allowed.
Co-authored-by: Colin Loretz <colin.loretz@discordapp.com>
Adds documentation for the
guild_scheduled_event
'srecurrence_rule
.As is evidenced in the documentation, the
recurrence_rule
is heavily restricted right now and is based on the current limitations present in the app.Solves:
recurrence_rule
in Guild Scheduled Event #6799recurrence_rule.end
returns "This field is not supported for recurring events." #7020