| Commit message (Collapse) | Author | Age | Lines |
| ... | |
| | | | | | | | |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Creating a new object caused the assert to fail because different objects were used.
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
`assert_called_once_with` was being tested on call_args which always reported success.st.
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
This allows us to use coroutines with await directly instead of asyncio.run
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Before the channel was not added if `persistent` was `True`.
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
With the removal of the channel args,
it's no longer necessary to mention the channel in the command output.
Tests adjusted accordingly
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Needless call args which were constant were kept in the test cases, resulting in redundant code,
the args were moved directly into the function call.
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Previously silencing a channel reset all overwrites excluding `send_messages`
and unsilencing them removed all overwrites.
This is prevented by getting the current overwrite
and applying it with only send_messages changed.
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Separating the notifier allows us to keep the Silence class
and its methods to be more focused on the class' purpose,
handling the logic of adding/removing channels
and the loop itself behind `SilenceNotifier`'s interface.
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Calling the command coro directly did unnecessary checks and
made tests for the method harder to realize.
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
FirstHash is used for handling channels in `loop_alert_channels` set as tuples without considering other elements.
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
With the updated definition on logging levels, there are a few events that were issuing logs at too high of a level.
This also includes some kaizening of existing log messages.
|
| | | | |\ \ \ \ |
|
| | | | |\ \ \ \ \ |
|
| | | | | |\ \ \ \ \ |
|
| | | | |/ / / / / /
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
to sentence split iterate and equality check.
|
| | | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
matching may not count exact word as best choice.
|
| | | | | | |/ / /
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
The only difference was the automatic addition of word boundaries.
Otherwise, they shared a lot of code. The regex lists were kept separate
in the config to retain the convenience of word boundaries automatically
being added.
* Rename filter to `watch_regex`
* Expand spoilers for both words and tokens
* Ignore URLs for both words and tokens
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
existing function.
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
custom/new one.
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
`send_embed_with_trashcan` function.
|
| | | | | | | | | |
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
`send_embed_with_trashcan`, applied to docstring and to command.
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | |_|_|_|_|/ /
|/| | | | | |
| | | | | | |
| | | | | | | |
deletion handling.
|
| | | | | | | |
| | | | | | |
| | | | | | | |
Co-Authored-By: Mark <[email protected]>
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
infraction that is already expired and reason not specified.
|