Display whether DM was sent to user when listing infraction(s).#1951
Merged
Conversation
Contributor
Author
|
For the record I'm planning to fix this tests at some point this upcoming week 👍 |
a6a474a to
94936e4
Compare
This was referenced Dec 26, 2021
TizzySaurus
added a commit
that referenced
this pull request
Jan 22, 2022
Fixes an issue caused by #1951.
MarkKoz
pushed a commit
that referenced
this pull request
Jan 26, 2022
Fixes an issue caused by #1951.
This file contains hidden or 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
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.
Closes #1864.
The
!infractionembed now show whether or not a DM was sent when an infraction was made.Possible values:
Yes: the DM was sentNo: the DM wasn't sent (triggers for "hidden" infractions too)N/A: the infraction was made before database change so we don't know if DM was sent or notNOTE: I've not been able to test that the
N/Aactually works since I didn't have any prior infractions in the database, but it should be fine.Relevant other PRs: site#621 and api#28.