| Commit message (Collapse) | Author | Lines |
|
The API was change a long time ago to not allow such a situation.
|
|
|
|
`format_user` isn't used in the apply mod log cause it already shows
both the old and new nicknames elsewhere.
|
|
This will be used a lot when sending mod logs and will help with
reducing redundancy and maintaining consistency.
|
|
|
|
|
|
|
|
|
|
This reverts commit 776b4379c478284803a4a526b5f14fe63d8e7c01.
This is already being fixed in #835, and therefore is no longer
required.
|
|
This also accounts for the author passing themselves to mention, and
therefore avoids the user from being told they're not allowed to mention
themselves even though they could.
|
|
|
|
|
|
The reminder expiration returnedfrom the API call is also now parsed
again even when the edit is to the duration since it does not matter and
trying to keep it DRY while still doing that check is a pain.
|
|
|
|
|
|
|
|
|
|
Co-authored-by: Mark <[email protected]>
|
|
In addition to 404, this shouldn't send Sentry notifs.
Co-authored-by: MarkKoz <[email protected]>
|
|
|
|
Co-authored-by: MarkKoz <[email protected]>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The function `_delete_reminder` was called twice, once in
`schedule_reminder`, which calls `send_reminder`, then another in
`send_reminder` itself. This led to a 404 response from the site api, as
the reminder was already deleted the first time.
Fixes BOT-6W
|
|
|
|
|
|
https://github.com/python-discord/bot/issues/1041
|
|
Weird.
https://github.com/python-discord/bot/issues/1041
|
|
When we're using the !reply command, using a regular UserConverter is
somewhat problematic. For example, if I wanted to send the message
"lemon loves you", then I'd try to write `!reply lemon loves you` -
however, the optional User converter would then try to convert `lemon`
into a User, which it would successfully do since there's like 60 lemons
on our server.
As a result, the message "loves you" would be sent to a user called
lemon.. god knows which one.
To solve this bit of ambiguity, I introduce a new converter which only
converts user mentions or user IDs into User, not strings that may be
intended as part of the message you are sending.
https://github.com/python-discord/bot/issues/1041
|
|
Co-authored-by: Sebastiaan Zeeff <[email protected]>
|
|
https://github.com/python-discord/bot/issues/1041
|
|
Without this, it is difficult to know precisely who the user that is
DMing us is, which might be useful to us.
https://github.com/python-discord/bot/issues/1041
|
|
This reverts commit 042f472a
|
|
Fixes a regression where the string to be matched was not processed
beforehand.
|
|
|
|
Users can no longer see available channels if they're on cooldown. They
will instead see a special "cooldown" channel which will explain
what's going on.
|
|
The message may be deleted somehow before the wait_for times out.
Fixes #1050
Fixes BOT-6X
|
|
If you're typing up a reply and the bot gets another DM while you're
typing, you might accidentally send your reply to the wrong person.
This could happen even if you're very attentive, because it might be a
matter of milliseconds. The complexity to prevent this isn't worth the
convenience of the feature, and it's nice to get rid of the caching as
well, so I've decided to just make .reply require a user for every
reply.
https://github.com/python-discord/bot/issues/1041
|
|
Co-authored-by: Sebastiaan Zeeff <[email protected]>
|
|
Suggested by Mark during review. If the download fails, we fallback
on showing an informative message, which will link the attachment
cdn link.
The attachment-handling logic was moved from the `archive` coroutine
into `make_embed`, which now also returns the file, if available.
In the end, this appears to be the smoothest approach.
Co-authored-by: MarkKoz <[email protected]>
|
|
|
|
|
|
Adjust description and include link to docs
|
|
The kwarg `active=False` is already being passed in `apply_kick`,
therefore passing it in the parent callers result in a TypeError.
Fixes #976
Fixes BOT-5P
|