-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
fix(api): various fixes for overlooked stuff #9588
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ |
According to the Discord docs, creating a followup message is the same as executing a webhook, but *wait is always true*, meaning we always get the message.
Can you test if this is the case? If I recall correctly, followUp didn't return anything. |
The following code leaves me with a client.on(GatewayDispatchEvents.InteractionCreate, async ({ api, data: interaction }) => {
await api.interactions.reply(interaction.id, interaction.token, {
content: 'reply',
});
const message = await api.interactions.followUp(interaction.application_id, interaction.token, {
content: 'followup',
});
console.log(message);
}); Other than this test the Discord docs say that |
Apologies, I got this endpoint mixed up the the reply endpoint. |
Please describe the changes this PR makes and why it should be merged:
This PR mainly contains corrections for incorrect typings that were overlooked.
In addition this also makes
InteractionsAPI#followUp()
return a result which should always bePromise<APIMessage>
on success (according to the Discord docs on the creation of followup messages: "Functions the same as Execute Webhook, butwait
is always true.")Status and versioning classification: