Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Receive message builder result within builder API #461

Open
gdude2002 opened this issue Dec 20, 2021 · 2 comments
Open

Receive message builder result within builder API #461

gdude2002 opened this issue Dec 20, 2021 · 2 comments

Comments

@gdude2002
Copy link
Contributor

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.

@DRSchlaubi
Copy link
Member

Currently, it's impossible to make components update themselves by editing the message they were sent in,

Seemingly Discord has since added a new method https://dokka.kord.dev/core/dev.kord.core.behavior.interaction/acknowledge-public-update-message.html

Does this apply for your use case?

@gdude2002
Copy link
Contributor Author

Nope.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants