Closed nefrob closed 1 year ago
Alternatively I would suggest using UserModel.USERNAME_FIELD
here.
Thanks for the PR. but the API already exposes PASSWORD_RESET_CONFIRM_SERIALIZER
where folks can customize as they wish. I would prefer to support a custom serializer rather than making the default serializer customizable.
When resetting a password from an email link we may want the lookup field on the user to be something other than the primary key (ex. unique email address). To support easy overriding of the lookup field it is now set as an instance variable on the serializer class.