We don't want to supply the bot's own messages to the message supply because ignoring your own messages is tedious boilerplate. So we can add a Promise to the created Message and keep it when the API sees the message come back. #35730

TonyHCIR · 2023-07-04T00:22:40Z

We don't want to supply the bot's own messages to the message supply because ignoring your own messages is tedious boilerplate. So we can add a Promise to the created Message and keep it when the API sees the message come back.

We would need to know how Discord munge messages so we can recognise that it was the "same" one. Maybe we're given a message ID on POST?

Originally posted by @Altreus in shuppet/raku-api-discord#57

alzimmermsft closed this as completed Jul 5, 2023

github-actions bot locked and limited conversation to collaborators Oct 3, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

We don't want to supply the bot's own messages to the message supply because ignoring your own messages is tedious boilerplate. So we can add a Promise to the created Message and keep it when the API sees the message come back. #35730

We don't want to supply the bot's own messages to the message supply because ignoring your own messages is tedious boilerplate. So we can add a Promise to the created Message and keep it when the API sees the message come back. #35730

TonyHCIR commented Jul 4, 2023

We don't want to supply the bot's own messages to the message supply because ignoring your own messages is tedious boilerplate. So we can add a Promise to the created Message and keep it when the API sees the message come back. #35730

We don't want to supply the bot's own messages to the message supply because ignoring your own messages is tedious boilerplate. So we can add a Promise to the created Message and keep it when the API sees the message come back. #35730

Comments

TonyHCIR commented Jul 4, 2023