Handle attachments and reactions for messages #14
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.
Discord sends a list of all attachments in the JSON when transmitting a message object. Similarly, under certain circumstances a list of all reactions is transmitted. This PR adds both infos to the
dpp::message
object.Firstly, there's a new attachment struct. It closely follows the official docs on what's present and what not.
Secondly, I've added one field to dpp::reaction, the emoji name. Discord sends it, and for non-custom reactions, this is often the only way to figure out which emoji was used to react.
Both are populated accordingly.