Use custom clean cog when purge banning#2033
Conversation
e9313a6 to
fd3bfc7
Compare
|
Since this changeset introduces additional cross-cog dependencies, that could be unintentionally broken, I'm planning on writing some tests for this new behaviour. Will get around to it later this evening/tomorrow. |
268fb63 to
a026dec
Compare
There are some aditional bugs with undefined behavior related to this, depending on how they are implemented. Please check #2022 (comment) for more information. |
I'm only importing for type checking, so I dont follow how that applies for this case? |
ec02d06 to
a14f47c
Compare
dfee235 to
536a4ea
Compare
536a4ea to
37d9e93
Compare
37d9e93 to
7212bea
Compare
If done outside a mod channel, it instead tags the invoker in #mods.
This migrates the purgeban command away from Discord's native purgeban to our custom logic. Discord's native purgeban does not leave us with any evidence or context of what messages were deleted. So when mods reference the infraction at a later date they are lacking information. Instead, we use our custom clean cog to delete all messages from the user in question for the last hour, and automatically append the link to the clean log to the infraction reason. .
Co-authored-by: GDWR <gregory.dwr@gmail.com>
Co-authored-by: GDWR <gregory.dwr@gmail.com>
7212bea to
762b107
Compare
This PR migrates our purgeban command away from Discord's native purgeban in favour of our custom logic.
Discord's native purgeban does not leave us with any evidence or context of what messages were deleted. So when mods reference the infraction at a later date, as example for an appeal, they are lacking required information.
Instead, we can use our custom clean cog to delete all messages from the user in question for the last hour, and automatically append the link to that clean log to the infraction reason.