Open
Conversation
Contributor
Author
|
For future reference, the workaround to the problem I described when editing an embed message, is not to remove the attachment, but to use the same Removing the attachment can invalidate the attachment's CDN URL - it's probably deleted on Discord's backend - if the message being edited is the only reference to the attachment. As for this PR, some people may still find it useful to be able to remove or edit attachments from messages, but I don't have a use case for it right now 🙂 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
From the documentation:
In particular, this allows editing a message with an embed that referenced a file uploaded in the same message, without the file now showing up outside the embed. This issue had been previously reported here, and the workaround from one of the responses, translated to racket-cord:
I think it's related to this oddity.
The way the Discord API handles attachments is not great IMO, but since racket-cord is pretty low level, I guess we should just expose it the way it is?