Repository navigation
Update from code changes: RegisterAsDispatchListener and READY guildDelete - #94
mintlify[bot] wants to merge 1 commit into
Conversation
|
Note mintlify[bot] opened this pull request, so PR Lens left it undrawn. Comment
|
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
|
The Fix: run <Warning>
- With `events` set on `forwardGatewayDispatches`, a listener of an event built from a dispatch that is not forwarded runs
- nowhere. Workers receive dispatches at least once, so keep the listener idempotent.
+ With `events` set on `forwardGatewayDispatches`, a listener of an event built from a dispatch that is not forwarded runs nowhere. Workers receive
+ dispatches at least once, so keep the listener idempotent.
</Warning>Verification: after the fix, Blocker: I committed the fix locally as Next step: apply the diff above by running
|

Summary
Documents the new
RegisterAsDispatchListenerdecorator and the forwarding of theGUILD_DELETEthe client emits for guilds aREADYno longer lists.Changes
client.forwardsDispatches, rejected gateway-only events,eventsfilter and idempotency caveats).dispatchemission asGUILD_DELETE.GUILD_DELETEand adds a "Run listeners on the workers only" subsection.Context