Repository navigation
Conversation
UserInfo has no 'data' field, so a valid token raised AttributeError. Return the JSON of the '/api/users/me' response instead.
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Changelog Description
Fix
get_user_by_tokenraisingAttributeErrorfor any valid token. It returneduser_info.data, butUserInfohas nodatafield. It now returns the JSON of the/api/users/meresponse.Additional info
Noted in #374, not fixed there.
The alternative is to expose data on
UserInfo?Testing notes:
Run this with a valid token or API key. Before the fix it raises
AttributeError: 'UserInfo' object has no attribute 'data'; after, it prints the user name.An invalid token should still return
None.