Interaction classes #1391
Merged
Interaction classes #1391
Conversation
This file contains hidden or 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
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.
This pull request introduces a refactor to how Discord interaction events are handled, making the system more extensible and type-safe. The main change is the introduction of dedicated classes for each interaction type, enabling more precise handling and easier future maintenance. Additionally, a new method is added to the channel select component to indicate if a field is required.
Interaction handling refactor
Ping,ApplicationCommand,MessageComponent,ApplicationCommandAutocomplete, andModalSubmit, each with their own type constants and data attribute handling. [1] [2] [3] [4] [5]TYPESconstant inInteraction.phpto map interaction type integers to their respective classes for dynamic instantiation.InteractionCreate.phpto instantiate the correct interaction class based on the type using the newTYPESmapping.Component improvements
setRequiredmethod toChannelSelect.phpto allow specifying if a component is required (for modals).