Could we update the migration guide to include the exception name change:
https://github.com/vimalloc/flask-jwt-extended/blob/master/docs/v4_upgrade_guide.rst
Version 3.x.x uses UserLoadError while version 4.x.x uses UserLookupError. This is a breaking change.
Version 3.x.x uses UserLoadError
|
class UserLoadError(JWTExtendedException): |
|
""" |
|
Error raised when a user_loader callback function returns None, indicating |
|
that it cannot or will not load a user for the given identity. |
|
""" |
|
pass |
Version 4.x.x uses UserLookupError
|
class UserLookupError(JWTExtendedException): |
|
""" |
|
Error raised when a user_lookup callback function returns None, indicating |
|
that it cannot or will not load a user for the given identity. |
|
""" |
|
|
Suggestion:
API Changes
~~~~~~~~~~~
- Removed ``UserLoadError`` from ``flask_jwt_extended.exceptions`` . Use ``UserLookupError`` instead.
Could we update the migration guide to include the exception name change:
https://github.com/vimalloc/flask-jwt-extended/blob/master/docs/v4_upgrade_guide.rst
Version 3.x.x uses
UserLoadErrorwhile version 4.x.x usesUserLookupError. This is a breaking change.Version 3.x.x uses
UserLoadErrorflask-jwt-extended/flask_jwt_extended/exceptions.py
Lines 59 to 64 in 12ead38
Version 4.x.x uses
UserLookupErrorflask-jwt-extended/flask_jwt_extended/exceptions.py
Lines 73 to 78 in d13dd8d
Suggestion: