You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 5, 2020. It is now read-only.
They have a setting REST_AUTH_SERIALIZERS where custom serializer class names can be specified , and those serializers are loaded dynamically.
We could provide some similar setting NOPASSWORD_FORMS, those forms would be used both by the regular views and by the serializers.
This way providing a custom form + changing settings would be enough to integrate custom forms.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It is very hard to use a custom form, especially when using REST:
include
to include all nopassword urls, but instead include all urls seperately just to be able to use the new viewIt would be great if we would support dynamic loading of the used form classes, in the same way as django rest auth is doing it:
https://github.com/Tivix/django-rest-auth/blob/master/rest_auth/app_settings.py#L28
They have a setting
REST_AUTH_SERIALIZERS
where custom serializer class names can be specified , and those serializers are loaded dynamically.We could provide some similar setting
NOPASSWORD_FORMS
, those forms would be used both by the regular views and by the serializers.This way providing a custom form + changing settings would be enough to integrate custom forms.
The text was updated successfully, but these errors were encountered: