Releases: apragacz/django-rest-registration
Releases · apragacz/django-rest-registration
0.6.4
0.6.3
0.6.2
0.6.1
0.6.0
Changes:
- Add a check for SEND_RESET_PASSWORD_LINK_SERIALIZER_USE_EMAIL (#92)
- Remove typing ignores (#109)
- Deprecate DefaultRegisterEmailSerializer.get_email() method (#95)
- Add SEND_RESET_PASSWORD_LINK_USER_FINDER (#94)
- Add USE_NON_FIELD_ERRORS_KEY_FROM_DRF_SETTINGS (#125)
- Use get_user_public_field_names() instead of get_user_field_names()
- Add Brazilian Portuguese (pt_BR) translation (#122)
- Add LOGIN_AUTHENTICATOR function setting (#51)
- Move password validation to reset password serializer (#110)
0.5.6
0.5.5
0.5.4
0.5.3
Changes:
- Added
'RESET_PASSWORD_FAIL_WHEN_USER_NOT_FOUND'
setting key (issue #81) - Added login fields unique system check (issue #91)
- Limited Django to <3.0 (due to some incompatibility issues - limit will
be lifted in0.6.*
) - Added Makefile (issue #88)
- Added French message translation (pull request #85)
- Added Contributing Guidelines (issue #64)
- Various test code refactors
0.5.2
Changes:
- Resolve issue #77: Allow using DRR without templates setup
- Fix issue #79: do not create user when sending verification fails
- Fix issue #83: Support change to already existing e-mail in the DB
Detect whether user email field is unique. If yes, then send "e-mail
already exists" notification instead of verification one.
Also, perform a check just before changing the e-mail to avoid
integrity errors. - Fix issue #68
Add VERIFICATION_TEMPLATE_CONTEXT_BUILDER settings key - Fix invalid config in README