CreateMessageParams that are automatically created (via .Send, .SendMsg, and .Reply) should now respect Message.MessageReference where appropriate. This was previously not included so it wasn't very intuitive for how to quickly reply to a message and include that original message as a reference.
Description
Included code that copies MessageReference from the Message object to the CreateMessageParams object when other params are copied.
Type of change
[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
Benchmarks
N/A
Checklist:
[N/A] I ran go generate
[X] I ran go fmt ./...
[X] I have performed a self-review of my own code
[N/A] Commented complex situations or referenced the discord documentation
[N/A] Updated documentation
[N/A] Added/Updated unit tests
[N/A] Added/Updated benchmarks (if this is a performance critical component)
CreateMessageParams that are automatically created (via .Send, .SendMsg, and .Reply) should now respect Message.MessageReference where appropriate. This was previously not included so it wasn't very intuitive for how to quickly reply to a message and include that original message as a reference.
Description
Included code that copies MessageReference from the Message object to the CreateMessageParams object when other params are copied.
Type of change
Benchmarks
N/A
Checklist:
go generate
go fmt ./...