| Commit message (Collapse) | Author | Lines |
|
The help channel prefix is configurable as a constant, but I accidentally used a static prefix in the utility function that cleaned the channel names. This commit makes sure the utility method uses the prefix defined in the constants.
|
|
The current approach of trying to find the maximum channel position, adding one, and using that as the position integer for channels does not seem to work reliably. An approach that seems to work in the testing environment is using a very large integer for the position attribute of the channel: It wil be sorted at the bottom and Discord will automatically scale the integer down to `max + 1`.
This also means the `get_position` utility function is no longer needed; it has been removed.
|
|
I've added channel status emojis as a prefix to our help channels to make it more obvious to the end user what the current status of a channel is. All channels in the Available category will be marked with a green checkmark emoji, while all channels in the In Use category will be marked with an hourglass. Channels in the Dormant category stay unadorned.
Channels will be stripped of their previous prefix when moved to another category. This relies on the `help-` naming convention, as that is the most reliable way to do it that does not break if we ever opt for another emoji.
|
|
The current sorting algorithm we used created unpredictable channel order (for our human end-users) and induced a flickering channel light-show in Discord clients. To combat these undesirable side-effects, I've changed the ordering to always order channels at the bottom of a category. This also means that channels looking for answers the longest will naturally float up.
|
|
|
|
|
|
|
|
The Coding Den is a language agnostic community that's been around for years with over 12000 members.
I think we can allow that invite in our community.
|
|
Co-Authored-By: Mark <[email protected]>
|
|
infraction that is already expired and reason not specified.
|
|
existing function.
|
|
custom/new one.
|
|
`send_embed_with_trashcan` function.
|
|
|
|
`send_embed_with_trashcan`, applied to docstring and to command.
|
|
|
|
The edit causes two channel update events to dispatch simultaneously:
one for the channel topic changing and one for the category changing.
The ModLog cog currently doesn't support ignoring multiple events of
the same type for the same channel. Therefore, the ignore was hard coded
rather than using the typical ignore mechanism.
This is intended to be a temporary solution; it should be removed once
the ModLog is changed to support this situation.
|
|
|
|
Co-Authored-By: Leon Sandøy <[email protected]>
|
|
The "unsilence" action of the silence/hush command used `send_messages=True` when unsilencing a hushed channel. This had the side effect of also enabling send messages permissions for those with the Muted rule, as an explicit True permission apparently overwrites an explicit False permission, even if the latter was set for a higher top-role.
The solution is to revert back to the `Inherit` permission by assigning `None`. This is what we normally use when Developers are allowed to send messages to a channel.
|
|
|
|
|
|
deletion handling.
|
|
|
|
|
|
There is no longer a reliance on static alphabetical position numbers.
|
|
When a channel is moved, all channels below have their positions
incremented by 1. This threw off the previous implementation which
relied on position numbers being static.
Co-authored-by: Sebastiaan Zeeff <[email protected]>
|
|
|
|
|
|
moved PEP 0 sending to function.
|
|
|
|
|
|
docstrings, string formatting and URL hiding to show in logs.
Co-Authored-By: Mark <[email protected]>
|
|
|
|
|
|
confusion in `delete_and_respond` function.
|
|
|
|
|
|
unnecessary function `scan_message`, moved this content to `on_message` event.
|
|
|
|
|
|
|
|
detecting.
|
|
listener.
|
|
|
|
Webhook URLs.
|
|
|
|
`scan_message` helper function to detect Webhook URL.
|
|
|