Allow executing code after sign in and before sign out

[monfresh]

Why
In some cases, it might be necessary to run some code right after the user signs in, but before the OTP is sent, and also right before a user signs out.

For example, consider this scenario:

• The app requires the user to confirm their phone number before it gets saved. This confirmation is done by sending an OTP to the phone and asking the user to enter it.
• User mistypes the number, then closes the anonymous browser window, or signs out before confirming
• User signs back in, and OTP is sent to the mistyped number. User is now unable to fully sign in since the OTP is being sent to the wrong number

In order to prevent this scenario, we need to be able to reset the unconfirmed_mobile to nil before the OTP is sent, and before they sign out so that they can type it in again.

How
Allow the gem user to define an OtpSender class with a reset_otp_state method

[Houdini]

Thatnks,

one thing I doubt about is that OtpSender says nothing about object.
If you use otp for user and admin_user, otp all goes to OtpSender.

What do you think about this:

def reset_otp_state_for(user)
  klass_string = "#{user.class}OtpSender"
  return unless Object.const_defined?(klass_string)

  klass = Object.const_get(klass_string)

  otp_sender = klass.new(user)

  otp_sender.reset_otp_state if otp_sender.respond_to?(:reset_otp_state)
end

[Houdini]

So OtpSender would be like service object.

UserOtpSender
AdminUserOtpSender

etc

[monfresh]

Good point. That way, you can have different logic for different types of users. I'll make the change.

[monfresh]

I made the change. Let me know how it looks now. Thanks!