Populate more user informations on POST /auth/login #3723
Merged
Conversation
This file contains 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
Find user by email or identifier to get files and relations.
alexandrebodin
requested changes
Aug 5, 2019
alexandrebodin
changed the title
alexandrebodin
added
pr: 馃拝 Enhancement
source: core:content-manager
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.
Find user by email or identifier to get files and relations.
When user call /auth/login url, the "user" object must cointains entire user object (avatar picture, relations .... ) not default strapi data.
Related to this issue: #1980
My PR is a:
Main update on the:
Manual testing done on the following databases: