| Commit message (Collapse) | Author | Age | Lines |
| |
|
|
|
| |
Reads better as separate lines
Co-Authored-By: Mark <[email protected]>
|
| |
|
| |
Co-Authored-By: Mark <[email protected]>
|
| |
|
|
|
| |
Makes the code a bit clearer
Co-authored-by: Shirayuki Nekomata <[email protected]>
|
| |
|
|
| |
It was triggering an error if the user deleted the output before re-evaluating
|
| |
|
|
| |
This avoid recreating partials for each re-eval
|
| | |
|
| |
|
|
| |
It can be used to test aiohttp request functions, since they are async context managers
|
| |
|
|
| |
The use of lambdas made the functions hard to test, this new format allows us to easily test those functions and document them.
|
| |\ |
|
| | |\
| | |
| | | |
Fix user command error for empty custom status
|
| | | |\
| | |/
| |/| |
|
| | |\ \
| | | |
| | | | |
Support applying infractions to users not in the DB via Converter `FetchedUser`
|
| | | |\ \
| | |/ /
| |/| | |
|
| | |\ \ \
| | | | |
| | | | | |
Log voice channel events
|
| | | |\ \ \
| | |/ / /
| |/| | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
This feature will be available in discord.py 1.3.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Use a red icon when leaving or mute/deafened. Use a green icon when
joining or unmuted/undeafened. Use a blue icon when changing channels or
any other possible change.
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The log will already show that the channel changes to the AFK channel
so showing the attribute change is redundant. If the channel were not
clearly named "AFK" then it might've made sense to keep the attribute.
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
* Add corresponding event to the Event enum so the event can be ignored
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
* Add ID for the voice-log channel.
* Add IDs for admins & staff voice channels and make the mod log ignore
them.
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | |\ \ |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
When debugging, the response_text exceeds the character limit since it's
basically an entire HTML document.
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
* Show the user in the post_infraction error log message
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
There's now a check to see if the `user` argument (possibly a
`discord.Object`) needs to be made a `User`, instead of doing so
directly, to avoid unnecessary requests to the Discord API. Besides
that, a possible HTTPException is catched if it the fetch fails,
cancelling the message to be send to the user (which would make the
following calls fail later on for not being of the proper type.)
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This changes also removes the original `proxy_user` used by
`watchchannels` the attributes in its `discord.Object` object to the one
returned by FetchedUser.
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
It turns out how it was originally was the best idea. Now the
`infractions` module imports `FetchedUser` and makes a `typing.Union`
between it and `utils.UserTypes`. The usage of `FetchedUser` isn't
needed in `utils` at all, and it shouldn't be used for/as type hinting there.
|
| | | | | | | |
|
| | | | |\ \ \
| | | | | | |
| | | | | | |
| | | | | | | |
fetched-user
|
| | | | | | | |
| | | | | | |
| | | | | | | |
Co-Authored-By: Mark <[email protected]>
|
| | | | |/ / / |
|
| | | | | | | |
|
| | | | |\ \ \ |
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
The `proxy_user` function now belongs to the `Converters` module,
since its use is directly related to it. `FetchedUser` uses this
function if there's an error trying to fetch and it doesn't indicate
a non existing user.
Technically finished and working.
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
The FetchedUser Converter now counts with a `proxy_user` helper function (which
SHOULD NOT be there) to return a user as a last resource, in case
there was an issue fetching from the Discord API, as long as the error
isn't that there's no user with the given ID.
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Now `post_user(...)` expects either a `discord.User` or a
`discord.Object` object as `user`. Either way, it will try to take the relevant
attributes from `user` to fill the DB columns. If it can't be done,
`.avatar_hash`, `.discriminator`, and `name` will take default values.
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Try twice to apply the infraction. If the user is not in the database,
try to add it, then try to apply the infraction again.
This allows any moderation function that uses `FetchedUser` as a
converter to apply the infraction even when the user is absent in the
local database.
|