for testing and deploying your application
for finding and fixing issues
for empowering human code reviews
from djoser import utils
The coding style of this project requires that you add a docstring to this code element. Below, you find an example for methods:
class SomeClass: def some_method(self): """Do x and return foo."""
If you would like to know more about docstrings, we recommend to read PEP-257: Docstring Conventions.
from djoser.conf import settings
def activation_email(request, user, **kwargs):
"""
Side effect of updating is_active field to False
user_email = utils.get_user_email(user)
assert user_email is not None
to = [user_email]
to
(([a-z][a-z0-9_]{2,30})|(_[a-z0-9_]*))$
This check looks for invalid names for a range of different identifiers.
You can set regular expressions to which the identifiers must conform if the defaults do not match your requirements.
If your project includes a Pylint configuration file, the settings contained in that file take precedence.
To find out more about Pylint, please refer to their site.
context = {'user': user}
context.update(kwargs)
settings.EMAIL.activation(request, context).send(to)
user.is_active = False
user.save(update_fields=['is_active'])
def confirmation_email(request, user, **kwargs):
settings.EMAIL.confirmation(request, context).send(to)
The coding style of this project requires that you add a docstring to this code element. Below, you find an example for methods:
If you would like to know more about docstrings, we recommend to read PEP-257: Docstring Conventions.