Commit message (Collapse) | Author | Lines | ||
---|---|---|---|---|
2019-12-19 | Ignore coverage for infraction serializer unexpectedly succeeding | -2/+2 | ||
2019-12-19 | Add tests for missing active field of infractions | -0/+28 | ||
2019-12-19 | Remove default value from the active field of infractions | -10/+37 | ||
Due to the active field being specified in the UniqueTogetherValidator, the field is implicitly required. Typically default values are excluded from this restriction but in this case some infraction types must always be False. It's easier and makes more sense to require the active field explicitly rather than to write logic in the serializer which is conditional on the type of infractions. | ||||
2019-12-18 | Output errors more clearly for infraction serializer test failures | -6/+10 | ||
2019-12-18 | Test that new infractions pass validation | -0/+14 | ||
2019-12-18 | Add fixtures to create infractions in serializer tests | -16/+18 | ||
The fixtures are invoked manually because not all cases may need the same infractions. | ||||
2019-12-18 | Add regression test for the UniqueTogetherValidator fix | -0/+41 | ||
2019-12-18 | Infractions: fix UniqueTogetherValidator incorrectly failing | -1/+1 | ||
The active infractions queryset only gets filtered by the fields specified. This meant that if the same user and type had another infraction instance which was active, the validator would fail. The validator assumes failure if it sees any items still in the queryset after filtering. By including the active field in the validator, the queryset will be filtered by the active field too. In the case described above, the queryset would end up empty because a no infractions which are active will ever match an active=False filter. | ||||
2019-12-14 | Rename route /bot/offensive-message to /bot/offensive-messages | -4/+4 | ||
2019-12-09 | Add 1em bottom margin to wiki markdown codeblocks. | -0/+5 | ||
Any text following the end of a codeblock in the wiki would very closely hug the codeblock, impacting readability and giving poor structure to page content. This adds in an appropriate margin to the bottom of codeblocks to give a fair buffer that matches typical paragraph spacing. | ||||
2019-11-20 | Correct the discord tos link in rules endpoint. | -1/+1 | ||
2019-11-16 | Use direct database test intead of relying on GET | -3/+3 | ||
2019-11-16 | Write list test for the offensive message model | -0/+39 | ||
2019-11-12 | Make use of subtests | -20/+20 | ||
Co-authored-by: Sebastiaan Zeeff <[email protected]> | ||||
2019-11-12 | Add the `--debug` flag to the start command | -1/+1 | ||
2019-11-11 | Add pipenv run start command | -0/+1 | ||
2019-11-11 | Change setUpTestData to use aware datetime | -2/+2 | ||
This remove a warning during test run | ||||
2019-11-11 | Add deletion tests | -0/+24 | ||
2019-11-11 | Add tests to make sure the view return 405 for PATCH and PUT requests | -0/+22 | ||
2019-11-10 | Make sure the API return the appropriate response. | -0/+9 | ||
2019-11-07 | Merge master migration files | -2/+2 | ||
2019-11-07 | Block PATCH and PUT methods | -3/+2 | ||
2019-11-07 | Fix copy pasting mistake | -1/+1 | ||
2019-11-07 | Squash down migration files | -36/+3 | ||
2019-11-03 | Resolve migration merge conflicts | -8/+8 | ||
Since other pull requests were merged that also included migrations for the API app, this PR needed to be updated to avoid conflicts in the migration history. In addition, the test files contained names of specific migration files that needed to be updated to the correct names after the merge resolution. | ||||
2019-10-26 | Write tests for the offensive message model. | -3/+70 | ||
2019-10-26 | Delete unnecessary search filter | -4/+0 | ||
2019-10-26 | Change docs to use datetime.datetime instead of datetime.date | -2/+2 | ||
2019-10-26 | Add the offensive message model to the admin panel | -0/+6 | ||
2019-10-26 | Add new rules. | -32/+18 | ||
2019-10-25 | Fix type error in the future date validator | -1/+1 | ||