Skip to content

Conversation

Paillat-dev
Copy link
Member

@Paillat-dev Paillat-dev commented May 12, 2025

Summary

Superseeds: #2778 - no need to merge both.
Fixes #2777
Message update contains a full message object - no need to use that messy update logic. See:

Information

  • This PR fixes an issue.
  • This PR adds something new (e.g. new method or parameters).
  • This PR is a breaking change (e.g. methods or parameters removed/renamed).
  • This PR is not a code change (e.g. documentation, README, typehinting,
    examples, ...).

Checklist

  • I have searched the open pull requests for duplicates.
  • If code changes were made then they have been tested.
    • I have updated the documentation to reflect the changes.
  • If type: ignore comments were used, a comment is also left explaining why.
  • I have updated the changelog to include these changes.

Lulalaby
Lulalaby previously approved these changes Aug 2, 2025
Lulalaby
Lulalaby previously approved these changes Aug 28, 2025
Soheab
Soheab previously requested changes Sep 1, 2025
Copy link
Contributor

@Soheab Soheab left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not a fan of the attribute name new_message, but it makes sense and is fine for now. Good stuff.

@Lulalaby Lulalaby enabled auto-merge September 3, 2025 14:51
@Lulalaby Lulalaby merged commit 4e853f8 into Pycord-Development:master Sep 3, 2025
28 checks passed
@Paillat-dev Paillat-dev deleted the feat/mssage-update-parse-message branch September 3, 2025 14:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

after._raw_data in on_message_edit() does not reflect updated message data
4 participants