Add support for forwarded messages to autowarn checks #263
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Erisa
approved these changes
Feb 7, 2025
FloatingMilkshake
deleted the
floatingmilkshake/fowarded-msg-autowarn-checks
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adds support for forwarded messages; their content (& the content of any associated embeds—and embeds that are not part of a forwarded message!) are now run through all autowarn checks (I think I got all of them). Forwarded messages are not passed through "passive" checks, like looking for CTS pings for #cts-support-feed.
The content of the original message, the content of any forwarded messages, and any text in all embeds are concatenated into a long string that is passed through filters in place of
message.Content.Closes #234