modified exclude field in UserSerializer to only exclude the fields t… #132
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
…hat are part of the User model (default or otherwise).
eelectronn
changed the title
aalekhpatel07
approved these changes
Jan 14, 2021
|
This PR solves #137 |
|
Thanks for the update! |
st4lk
approved these changes
Jan 17, 2021
|
I made some changes here: |
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.
Hello, and thanks for creating this very useful project.
This is in response to issue #96
It raises this error when a field is excluded from
UserSerializerthat is not actually present in user model. Specifically, when a custom user model is implemented by extending theAbstractBaseUser.The fix involves only excluding the fields that are present in the user model.
Take care.