Split InteractionCreateEvent into 2 events for command and component events
See original GitHub issueSummary
Split InteractionCreateEvent into 2 separate events for command and component events. More useful for the user, in the same way GuildAvailableEvent was split.
Ideal implementation
2 sperate events and check for the type before deserializing the payload. I will open a PR.
Checklist
- I have searched the issue tracker and have made sure it’s not a duplicate. If it is a follow up of another issue, I have specified it.
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (6 by maintainers)
Top Results From Across the Web
Solved: how can i get two different events individually wh...
Solved: i am using splunk to get the logs. we build a data base where 2 or 3 log events are separated by...
Read more >CQRS - separate command and event handlers - Stack Overflow
Given both interfaces have a Handle method, what is the idea of splitting the commands and events in this way, when a single...
Read more >Advanced Events Example | Lightning Aura Components ...
Displays the event handlers on the UI for the complete demo. The definitions of component and application events are stored in separate .evt...
Read more >Event handling - discord.js Guide
Event handling. Node.js uses an event-driven architecture, making it possible to execute code when a specific event occurs.
Read more >Component Events - HTML5 Builder - Embarcadero DocWiki
For example, a component to render a button could have an OnClick event, ... Events can be separated in two main types: server-side...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It’s related to this. Dispatched when you save the URL for webhook-based interactions.
Dont think this will be done, so will close. Feel free to reopen or create a follow up issue if needed