Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

feat: message forwarding #2598

Open
wants to merge 38 commits into
base: master
Choose a base branch
from

Conversation

NeloBlivion
Copy link
Member

@NeloBlivion NeloBlivion commented Oct 6, 2024

Summary

Implements message forwarding, alongside some small cleanups for other message features.

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.

@NeloBlivion
Copy link
Member Author

NeloBlivion commented Oct 6, 2024

more or less done, just need to add mention/role mention handling and partialmessage support... but still 403ing on my bot 😔

@Lulalaby
Copy link
Member

Lulalaby commented Oct 6, 2024

unlucky bcs its 95% out. you're in th holdout group. try making a new bot

@JustaSqu1d JustaSqu1d added priority: medium Medium Priority feature Implements a feature API reflection Discord API isn't correctly reflected python Pull requests that update Python code labels Oct 21, 2024
Signed-off-by: UK <41271523+NeloBlivion@users.noreply.github.com>
@JustaSqu1d JustaSqu1d added this to the v2.7 milestone Nov 18, 2024
@Dorukyum
Copy link
Member

Dorukyum commented Jan 5, 2025

@NeloBlivion status?

auto-merge was automatically disabled February 6, 2025 03:15

Head branch was pushed to by a user without write access

Lulalaby
Lulalaby previously approved these changes Feb 6, 2025
@Lulalaby Lulalaby requested a review from plun1331 February 6, 2025 05:33
Copy link
Member

@Dorukyum Dorukyum left a comment

Choose a reason for hiding this comment

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

Testing required

@NeloBlivion
Copy link
Member Author

ah yeah, forgot to tick that box; as far as i've tested there haven't been any issues.

Signed-off-by: UK <41271523+NeloBlivion@users.noreply.github.com>
Copy link
Member

@Lulalaby Lulalaby left a comment

Choose a reason for hiding this comment

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

whats the status here, can this be tested and merged?

@NeloBlivion
Copy link
Member Author

As far as I've tested it operates fine, would appreciate others testing if they may know of any edge cases/weird behaviour with the attributes of ForwardedMessage but otherwise it's feature complete.

@NeloBlivion
Copy link
Member Author

(Actually haven't done a full review of docs so maybe that'd be a good idea)

Copy link
Contributor

@DA-344 DA-344 left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Contributor

@Paillat-dev Paillat-dev left a comment

Choose a reason for hiding this comment

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

IS there a particular reason this is not getting merged ? Or is this ok di per se ?

Comment on lines +1496 to +1497
A reference to the :class:`~discord.Message` you are replying to or forwarding, this can be created using
:meth:`~discord.Message.to_reference` or passed directly as a :class:`~discord.Message`. When replying, you can control
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
A reference to the :class:`~discord.Message` you are replying to or forwarding, this can be created using
:meth:`~discord.Message.to_reference` or passed directly as a :class:`~discord.Message`. When replying, you can control
A reference to the :class:`~discord.Message` you are replying to or forwarding, this can be created using
:meth:`~discord.Message.to_reference` or passed directly as a :class:`~discord.Message`. When replying, you can control

Two things here

  • this is a run-on sentence. Please reword and fix.
  • "you" is too casual and the sentence should be reworded in passive voice.

Lulalaby and others added 2 commits March 27, 2025 07:59
Co-authored-by: JustaSqu1d <89910983+JustaSqu1d@users.noreply.github.com>
Signed-off-by: Lala Sabathil <aiko@aitsys.dev>
Signed-off-by: Lala Sabathil <lala@pycord.dev>
@Paillat-dev
Copy link
Contributor

This pr should be marked as fixing

@Lulalaby Lulalaby linked an issue Mar 31, 2025 that may be closed by this pull request
@Lulalaby
Copy link
Member

done but i still won't pay you

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
API reflection Discord API isn't correctly reflected feature Implements a feature PA: Maintainers pending priority: medium Medium Priority python Pull requests that update Python code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Message Forwarding
6 participants