Added event based phone verification support. We have 4 new events, all of them are in the PhoneVerificationEvents class:
PHONE_CHANGED: this event is triggered whenever an user's mobile phone is changed. A PhoneVerification object will be created and the PHONE_VERIFICATION_REQUESTED event will be triggered;
PHONE_VERIFICATION_REQUESTED: this is triggered whenever there is a need to send the verification code to the user's phone. It is the implementer's responsibility to listen for this event and do whatever is necessary to actually send the code;
PHONE_VERIFICATION_CODE_SENT: after the code is sent this event must be dispatched in order to a SentVerification object be created. This object will be responsible to flood-protect the phone verification system;
PHONE_VERIFIED: this is dispatched after the user's phone was verified. You can, for example, send a text message to the user's phone confirming the verification was successful.
Added event based phone verification support. We have 4 new events, all of them are in the
PhoneVerificationEventsclass:PHONE_CHANGED: this event is triggered whenever an user's mobile phone is changed. APhoneVerificationobject will be created and thePHONE_VERIFICATION_REQUESTEDevent will be triggered;PHONE_VERIFICATION_REQUESTED: this is triggered whenever there is a need to send the verification code to the user's phone. It is the implementer's responsibility to listen for this event and do whatever is necessary to actually send the code;PHONE_VERIFICATION_CODE_SENT: after the code is sent this event must be dispatched in order to aSentVerificationobject be created. This object will be responsible to flood-protect the phone verification system;PHONE_VERIFIED: this is dispatched after the user's phone was verified. You can, for example, send a text message to the user's phone confirming the verification was successful.