Closed jdwx closed 1 month ago
It looks like most of this has already been corrected on the master branch, this may just be a request to backport that into a released version, which would be a very small change.
v7.3.5 is currently broken in a couple critical ways. At this time, we're currently recommending upgrading to 10.0.0-RC7 as the changes that need to be made are many and not necessarily trivial.
7.3.5 has worked pretty well for me, but I'll take your word for it and switch over!
Do you want a pull request to add methods for individual flags? E.g., setSuppressNotifications() and setSuppressEmbeds().
Based on the research I did on this, it looks like those might be the only two (and maybe EPHEMERAL?) that are meaningfully set on a new message. But I'm far from sure about that; I'm no expert, and have only tested and confirmed SUPPRESS_NOTIFICATIONS.
Hmm, had to back down to 7.3.5 because messages had empty strings for content in 10.0.0-RC7. I'm sure there's a reason; I'll have to look into that when I have more time.
Environment
Describe the bug The method MessageBuilder::_setFlags() is flagged as "@internal" with the message, "You cannot set flags except for when sending webhooks or interaction. Use the APIs given." This is not correct. Setting flags is needed for other purposes, including sending "@silent" messages. (See https://discord.com/developers/docs/resources/channel#message-object-message-flags )
To Reproduce Steps to reproduce the behavior:
Expected behavior The interface should be modified to expose this functionality, either by promoting this method from _setFlags() to setFlags() and removing @internal, or (if I have understood the comment's reference to using the API) by exposing the ability to set SUPPRESS_NOTIFICATIONS via a separate public method, which would need to binary-OR the flags value.