bot - A mirrored copy of the python-discord/bot repository.

	Commit message (Collapse)	Author	Lines
2019-11-13	Prevent setting unknown attributes on d.py mocks	Sebastiaan Zeeff	-58/+36
	Our custom `discord.py` now follow the specifications of the object they are mocking more strictly by using the `spec_set` instead of the `spec` kwarg to initialize the specifications. This means that trying to set an attribute that does not follow the specifications will now also result in an `AttributeError`. To make sure we are not trying to set illegal attributes during the default initialization of the mock objects, I've changed the way we handle default values of parameters. This does introduce a breaking change: Instead of passing a `suffix_id`, the `id` attribute should now be passed using the exact name. `id`. This commit also makes sure existing tests follow this change.
2019-11-13	Allow `name` attribute to be set during Mock init	Sebastiaan Zeeff	-0/+3
	The `name` keyword argument has a special meaning for the default mockobjects provided by `unittest.mock`. This means that by default, the common d.py `name` attribute can't be set during initalization of one of our custom Mock-objects by passing it to the constructor. Since it's unlikely for us to make use of the special `name` feature of mocks and more likely to want to set the d.py `name` attribute, I added special handling of the `name` kwarg.
2019-11-13	Prevent unwanted logging while running tests	Sebastiaan Zeeff	-1/+14
	Previously, logging messages would output to std.out. when running individual test files (instead of running the entire suite). To prevent this, I've added a `for`-loop to `tests.helpers` that sets the level of all registered loggers to `CRITICAL`. The reason for adding this to `tests.helpers` is simple: It's the most common file to be imported in individual tests, increasing the chance of the code being run for individual test files. A small downside of this way of handling logging is that when we are trying to assert logging messages are being emitted, we need to set the logger explicitly in the `self.assertLogs` context manager. This is a small downside, though, and probably good practice anyway. There was one test in `tests.bot.test_api` that did not do this, so I have changed this to make the test compatible with the new set-up.
2019-11-04	Change invite filter message to accurately reflect the new rules	kosayoda	-1/+1

2019-11-03	Show custom statuses in !user output	Jeremiah Boby	-1/+9
	Resolves #647
2019-11-02	Use `casefold` in some cases.	Johannes Christ	-1/+4