List of settings¶
These settings can be used to configure how verification should work
(for things like registration, password reset, email change).
You should add them as keys (with values)
No description available, please add it here!
The builder function receives the
signer object and construct
the url using
signer.get_signed_data(). The default url builder will use
the base url and append the signed data as HTTP GET query string.
It is be solely up to the implementer of custom builder function
to encode the signed values properly in the URL.
The builder function receives these parameters as positional arguments:
user- the user which is to be notified.
user_address- the user address, which can be the user e-mail, phone number, etc.
data- dictionary; in most cases it contains only one entry, which is the
'param_signer'key. The implementer of the custom builder function should be aware that the contents of the dictionary are dynamic and write defensive code to account that.
and these parameters as keyword arguments:
notification_type- value of
notification_method- value of
rest_registration.notifications.enums.NotificationMethodenum. Currently there is only one choice which is
It is possible that in the future, additional keyword arguments
may be added. Therefore the implementer
of the custom builder function should take account of that,
for instance by adding
**kwargs in the signature
of the function.