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
Hi, currently you can customize DPV by extending BaseBackend. Would it be possible to allow PhoneVerificationService to check whether the backend wants to supply the message directly, instead of having it only pull from settings.PHONE_VERIFICATION['MESSAGE']?
Specifically, allow the backend to replace this logic:
Hi, to be honest I don't recall the exact use case since this was 6 months ago. But in general, it would be useful to be able to customize the message since currently the only variables allowed are app and security_code, and the rest of the message has to be determined at import time, not runtime. So you can't say for example 'Hello, {user_name}, your code is {security_code}`.
This should be straightforward enough if the BaseBackend can call an optionally-defined function, or allow the message generation function to be overridden by a subclass.
Hi, currently you can customize DPV by extending
BaseBackend
. Would it be possible to allowPhoneVerificationService
to check whether the backend wants to supply the message directly, instead of having it only pull fromsettings.PHONE_VERIFICATION['MESSAGE']
?Specifically, allow the backend to replace this logic:
The text was updated successfully, but these errors were encountered: