Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
Summary
🚀Features
📝Docs
0. New Token Blacklist Model
To log users out, a token blacklist was created. Now you can invalidate a token at any moment. To do so,
verify_tokenfunction (also schemas and CRUD) created.🚚Migration
0. Update user table definition in
create_first_superuser.pyIf you change the
usermodel, you must also update the table definition insrc/scripts/create_first_superuser.pyin order for it to keep working.Here is the table definition:
Let's say you added a column in your user model,
age.I'll now update the table definition in
create_first_superuser.pyaccordingly:1. Token Blacklist
This should work out of the box, all you need to do is run the alembic migration.
While in the
srcfolder:And to apply the migration
🔎Bug fixes
create_first_superusernow working again.Warning
If you change the user model, now you'll also have to change the definition in
create_first_superuserscript. That happens because the script wasn't working without the relationship definitions, also getting the user model isn't trivial for async. May be fixed eventually.