This is probably the wrong way as we should really take care of removing the permission we added, but I don't see a reason anyone would need to migrate back that far as auth wouldn't work anymore without XML api (and even so newer installs don't have the settings referenced so permissions are not automagically added by the migration). So noop is bad but acceptable to me.
Thanks @mmolitor87
Switch to dedicated add/remove endpoints.
Allow setting max cache age to None for infinite.
Apparently patch has issues.
Thanks @TargetZ3R0 and Discord devs <3
I have no idea why the order is reversing itself. Doesn't matter for functionality which of them comes first. This just checks they're both in there and a comma to separate them.
The "empty" group will never appear as all users have a state so it has been removed.
I haven't yet found a good way to apply this to Teamspeak - perhaps go back to the token generation logic and create one with a user's state instead of "Member" and exempt those names from group sync?
Addresses #950
* Added in_organisation check to EveCharacter model
* Basic name formatter
* Switch mumble service to use name formatter
* Squash services migrations
* Add name to example service to allow it to be used in tests
* Add name formatter to services
* Add abstract views, model, form for services modules
* Refactor mumble service to new style
* Don't set credentials if setting a provided password
* Add success message to set password view
* Refactor settings into importable base.
User deployment should use 'from allianceauth.settings.base import *' in their project settings.
* Restructure tests folder.
Remove DOMAIN setting.
Use localhost for services revoked emails.
* Add missing python3.4 typing requirement
typing is included python3.5+
* Remove legacy setup comments
Remove legacy update script
Temporarily use latest snapshot for esi for dj20
Correct admin urls include
Manually correct old ts3 table migration
Remove obsolete services migrations
Remove bootstrap pagination package
Fix url namespacing
