You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm currently running into an issue with KordEx's design, where it's impossible to avoid fully wrapping some Kord APIs to make some things function nicely. Specifically, message create and edit builders provide no way to receive the relevant message object after it's been sent/edited.
This issue suggests adding a callback system for this purpose - callbacks could be added to the builders that will be called once the message has been created/edited and the relevant response has been received from discord.
My primary use-case for this is in KordEx's components system. Currently, it's impossible to make components update themselves by editing the message they were sent in, as it's impossible to pass that reference up the chain to them without entirely recreating a bunch of Kord message create/edit APIs - an approach which would be extremely brittle, confusing and unintuitive.
The text was updated successfully, but these errors were encountered:
I'm currently running into an issue with KordEx's design, where it's impossible to avoid fully wrapping some Kord APIs to make some things function nicely. Specifically, message create and edit builders provide no way to receive the relevant message object after it's been sent/edited.
This issue suggests adding a callback system for this purpose - callbacks could be added to the builders that will be called once the message has been created/edited and the relevant response has been received from discord.
My primary use-case for this is in KordEx's components system. Currently, it's impossible to make components update themselves by editing the message they were sent in, as it's impossible to pass that reference up the chain to them without entirely recreating a bunch of Kord message create/edit APIs - an approach which would be extremely brittle, confusing and unintuitive.
The text was updated successfully, but these errors were encountered: