Add ScheduledEvents support #152
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This includes a few convenience methods and all the necessary attributes for the class based on what the API returns for scheduled events.
It's events all the way down. Also a method on the Server class for getting scheduled events for a guild.
For getting a list of scheduled events off of a given guild.
Pretty basic implementation. Also renamed the create handler to match the other guild-based event handlers.
connorshea
commented
Apr 24, 2022
Added endpoints for Show/Create/Update/Delete.
Now we can use event listeners to track when a user is added or removed from a scheduled event.
This allows bots to request access for scheduled event creation, deletion, etc events.
Need to figure out how to handle these properly, for now it's just TODOs.
Also fix the event handlers. I wasn't defining the `matches?` method correctly.
|
Hey @connorshea; was this something you were still working on? I have a use case for what you've built here. Not sure if I can be of any help, but I'm happy to get my hands dirty if you'd like! |
|
Interested if anyone is going to pick this up? Is it close? I can look at it if nobody is owning it but it's lots of context to pickup if someone already has the context. Looks unfinished in #183 I'm using the REST api with the bot token for now, if anyone has the same requirements as me, but it's messy and not well integrated. |
|
Up |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
I think I've got most of this working now, and I've tested it with my own bot. The only thing that isn't working is the event handlers, because I didn't add them to
handle_dispatch. I might need some help on that part.TODO:
handle_dispatchso the event handlers actually get triggered.Added
Discordrb::ScheduledEventclass to represent Discord's Scheduled Events functionalityscheduled_eventsmethod onDiscordrb::Serverto get scheduled events for the given server.scheduled_eventmethod onDiscordrb::Serverfor getting individual scheduled events.deletemethod onDiscordrb::ScheduledEventto delete the ScheduledEvent.Discordrb::API::Serverfor creating, updating, and deleting scheduled events. These aren't exposed on the Discordrb::Server class right now, but you can use the "raw" endpoints if you really want to.