summaryrefslogtreecommitdiffstats
path: root/vendor/github.com/mattermost/mattermost-server/v5/utils/jsonutils
diff options
context:
space:
mode:
authorSimon THOBY <simonthoby@live.fr>2020-11-14 05:08:09 +0100
committerGitHub <noreply@github.com>2020-11-14 04:08:09 +0000
commitcbb46293ab670c1989bfcd9aae5d853223074038 (patch)
tree3376530d6ac2816c49140d7bef365ad05dff846d /vendor/github.com/mattermost/mattermost-server/v5/utils/jsonutils
parent765e00c949344b958d4681c91db8502d150f0353 (diff)
downloadmatterbridge-msglm-cbb46293ab670c1989bfcd9aae5d853223074038.tar.gz
matterbridge-msglm-cbb46293ab670c1989bfcd9aae5d853223074038.tar.bz2
matterbridge-msglm-cbb46293ab670c1989bfcd9aae5d853223074038.zip
Update webhook messages via new endpoint (discord)
When using the webhook, the previous method to edit a message was to delete the old one via the classical API, and to create a new message via the webhook. While this works, this means that editing "old" messages lead to a mess where the chronological order is no longer respected. This uses an hidden API explained in https://support.discord.com/hc/en-us/community/posts/360034557771 to achieve a proper edition using the webhook API. The obvious downside of this approach is that since it is an undocumented API for now, so there is no stability guarantee :/
Diffstat (limited to 'vendor/github.com/mattermost/mattermost-server/v5/utils/jsonutils')
0 files changed, 0 insertions, 0 deletions