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

when patching a message, the allowed_mentions property is deleted #3378

Closed
arnim279 opened this issue Jul 2, 2021 · 2 comments
Closed

when patching a message, the allowed_mentions property is deleted #3378

arnim279 opened this issue Jul 2, 2021 · 2 comments
Labels

Comments

@arnim279
Copy link

arnim279 commented Jul 2, 2021

Description
When I patch a message, the allowed_mentions property is resetted/deleted if I don't send it in the body again. On the other hand, when I update only the content property, the components property doesn't change (as it should)

Steps to Reproduce

  1. create a new message using
    POST /channels/{channel_id}/messages { "content": "test <@{user_id}>", "allowed_mentions": {"parse": [] }, "components": [] }
    --> the user should not be mentioned

  2. update the message using
    PATCH /channels/[channel_id}/messages/{message_id} { "content": "now I mention <@{user_id}>" }
    --> the allowed_mentions property doesn't work anymore

  • this only works if the message has components!

Expected Behavior
the allowed_mentions property should still work and the user shouldn't be mentioned

Current Behavior
the allowed_mentions property is deleted

Screenshots/Videos

  1. creating the message
    image
    image

  2. updating the message
    image
    image

Client and System Information
Discord Canary
Windows 11 (shouldn't matter)
I enabled threads if that matters

@arnim279 arnim279 added the bug label Jul 2, 2021
@SinisterRectus
Copy link
Contributor

The allowed_mentions property isn't stored. You have to send it every time content is created or updated. See #1864.

@arnim279
Copy link
Author

arnim279 commented Jul 2, 2021

well, that explains it

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

No branches or pull requests

2 participants