* Add routes for user activation (#403)
* Add routes for user activation
Generate a token after creating the user in register route, passing to `activation_callback`, if `activation_callback` supplied
Create new `/activate` route that will verify the token and activate the user
Add new error codes to `fastapi_users/router/common.py`
Update documentation
Add tests
Co-authored-by: Mark Todd <markpeter.todd@hotmail.co.uk>
* Rework routes for user activation
* Separate verification logic and token generation into `/fastapi_users/router/verify.py`, with per-route callbacks for custom behaviour
* Return register router to original state
* Added `is_verified` property to user models
* Added `requires_verification` argument to `get_users_router`and `get_auth_router`
* Additional dependencies added for verification in `fastapi_users/authentication/__init__.py`
* Update tests for new behaviour
* Update `README.md` to describe a workaround for possible problems during testing, by exceeding ulimit file descriptor limit
Co-authored-by: Mark Todd <markpeter.todd@hotmail.co.uk>
* Restored docs to original state.
* All other modifications reqested added
Kebab-case on request-verify-token
SECRET now used as test string
Other minor changes
Co-authored-by: Mark Todd <markpeter.todd@hotmail.co.uk>
* Embed token in body in verify route
* Reorganize checks in verify route and add unit test
* Ignore coverage on Protocol classes
* Tweak verify_user function to take full user in parameter
* Improve unit tests structure regarding parametrized test client
* Make after_verification_request optional to be more consistent with other routers
* Tweak status codes on verify routes
* Write documentation for verification feature
* Add not released warning on verify docs
Co-authored-by: Edd Salkield <edd@salkield.uk>
Co-authored-by: Mark Todd <markpeter.todd@hotmail.co.uk>
* fix: Change on the inheritance model, according to the documentation for the request body parameters. #171
* fix: Changes on the documentation examples to fix the inheritance problem when passing the User class (for create or update only passing the pydantic one) #171
* fix: Changes on the documentation examples to fix the inheritance problem when passing the User class (for create or update only passing the pydantic one) #171
* Put back inheritance on update model and factorize create_update_dict methods
Co-authored-by: François Voron <fvoron@gmail.com>
* Use UUID for user id and oauth account id
* Update documentation for UUID
* Tweak GUID definition of SQLAlchemy to match Tortoise ORM one
* Write migration doc
* Inject every model variations in router and DB model in DB adapters
* Update documentation and import Tortoise in db module
* Use path operation decorator dependencies for superuser routes
* add tortoise to dependencies
* add tortoise as optional dependency in pyproject.toml
* add tortoise support (tests needed)
* Add tortoise support (also defined orm_mode in pydantic model
* tests for tortoise support
* format by black
* docs for tortoise
* delete type annotations
* delete underscore
* do it in 1 line
* add 1 line before yield
* fix in docs
* fix bug and add annotation for test
* Tweak documentation and fix Tortoise error about id update
* Improve Tortoise coverage by using get instead of filter
* Fix Pipfile.lock
* Start to write documentation
* Add docs favicon
* Add routes documentation
* Add doc about dependency callables
* Add information about how to make authenticated calls
