-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DEVEXP-520: E2E Verification/Start #128
Conversation
identity: { | ||
type: 'number', | ||
endpoint: '+17813334444', | ||
}, | ||
method: 'sms', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
⭐
const verificationInitResponse: Verification.InitiateVerificationResponse | ||
= await verificationService.verifications.start(requestData); | ||
const startVerificationResponse: Verification.StartSmsVerificationResponse | ||
= await verificationService.startVerifications.startSms(requestData); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not fan of renaming verificationService.verifications
to verificationService.startVerifications
It could have sense ( with a major breaking change), but it start to drift with other SDK's provided implementation and ID <> SDKs function mapping
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Indeed, I generated from the OAS tag, I'll update according to the confluence page
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
On top of the implementation of the e2e steps, this PR starts the refactoring for the new naming convention regarding the "phone call" and "data" verifications.
I tried to make the code backward compatible by deprecating the references to the "callout" and "seamless" interfaces.
The refactoring for the reportVerification endpoint will take place with the DEVEXP-521 user story