| Commit message (Collapse) | Author | Age | Lines |
|
|
| |
update server's user count
|
|
|
|
|
|
| |
Revert commit 330a27926a7f2a9bdae56a5928cd81e55ccb38ed to reverse
changes made to 6c08da2f3e48db9c9dd452f2e0505c4a61e46592. Migrations
were failing when those changes were deployed.
|
|\
| |
| | |
Off-topic channel names non random selecting
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\
| |/
|/| |
|
|\ \
| | |
| | | |
Allow direct fetching of reminders by id
|
| | | |
|
| | | |
|
| | | |
|
|/ / |
|
| |
| |
| |
| |
| | |
This had the wrong data for GUILD_INVITES - it had invites instead of
Guild IDs. This new migration solves this problem.
|
|\ \
| | |
| | | |
FilterList model and endpoints
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Now that we have a migration that adds data, we can no longer have tests
that operate on the assumption that the database is going to be empty.
So, we're now clearing that table before these tests run.
|
| | |
| | |
| | |
| | |
| | | |
This will populate the table with domain names, guild invites, filter
tokens and file formats.
|
| | |
| | |
| | | |
Co-authored-by: Sebastiaan Zeeff <[email protected]>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This really should've been handled automatically by DRF, and in the
future, it will be. But for now, we need to have constraints both on the
serializer (to get status code 400), and on the model (to prevent direct
database constraint violations).
See https://github.com/encode/django-rest-framework/issues/7173
|
| | | |
|
| |\ \
| |/ /
|/| | |
|
|\ \ \
| | | |
| | | | |
Add mentions field to Reminders model
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Since the mentions field stores static IDs and not foreign keys, there
is no need to create the objects for the test.
|
| | | | |
|
| |\ \ \
| |/ / /
|/| | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
I was handling this in a Django vanilla kind of way, which was causing
the constraint to return a 500 instead of a 400. This changes the
approach to use the DRF way, and makes it return 400.
It doesn't actually change the way anything behaves, other than
returning the right status code.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
GUILD_INVITE_ID -> GUILD_INVITE
WORD_WATCHLIST -> FILTER_TOKEN
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This will be used to describe or justify the entries in the blacklist or
whitelist, for example for the guild name in the case of guild invite
IDs, so that we have some context when we're displaying the list.
https://github.com/python-discord/site/issues/305
|
| | | |
| | | |
| | | |
| | | | |
https://github.com/python-discord/site/issues/305
|
| | |\ \
| |_|/ /
|/| | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
The Django wiki updated the jQuery version, so our reference needs to
be updated too. Otherwise, we will get a 404 for the script.
|
| | | |
| | | |
| | | |
| | | | |
https://github.com/python-discord/site/issues/305
|
| | | |
| | | |
| | | |
| | | | |
https://github.com/python-discord/site/issues/305
|
| | | |
| | | |
| | | |
| | | | |
https://github.com/python-discord/site/issues/305
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The test_utils_account.py tests were never running, because the folder
they were in had no __init__.py file.
The test_models.py file was failing because it had an outdated import of
the ModelReprMixin, which has moved to a new file.
https://github.com/python-discord/site/issues/305
|
| | | |
| | | |
| | | |
| | | | |
https://github.com/python-discord/site/issues/305
|