-
-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
Message Forwarding #9950
Message Forwarding #9950
Conversation
Create enums and class attributes tracking the type of a message reference (default or forward)
Create a class to track a snapshot of a message
Add class MessageSnapshot to classes exported from message.py
…/discord.py into feature/message_snapshots
Co-authored-by: MCausc78 <[email protected]>
Move MessageReferenceType definition in types/message.py above MessageReference typed dict
Co-authored-by: owocado <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good but there are unfortunately merge conflicts.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, I forgot this PR also introduces instances of Optional[List[X]]
.
Merge conflicts have been resolved and suggestions have been commited, PR is now ready to be merged. |
This has conflicts again. |
Fixed merge conflicts again. |
Summary
redmvc said in #9892 they will not be able to continue with the PR anytime soon so I've continued their work in this PR.
This has all the previous changes in addition of:
PartialMessage.forward(...)
method for message forwardingMessageReference
constructor not a breaking changeMessageSnapshot
from "Data Classes" section to "Discord Models"MessageReferenceType
enum to docs.. versionadded::
s where it was missing.Related Discord API Docs PRs:
Checklist