-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Rapyd: Add customer object and fix tests #4838
Conversation
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.
Nice! Just had some concerns about field state and some code repetition
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.
I like this, since it calls out the different use-cases directly, all in one place. I would just reconsider the naming with these changes.
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.
Refactor looks good 🎉 Just take care of the pry
line before merging.
The Rapyd gateway requires the Customer object on multiple payment types now and is optional on all. This commit adds the customer subhash to requests and updates the remote tests to pass since Rapyd has changed it's requirements. Remote: 31 tests, 88 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications 100% passed
The Rapyd gateway requires the Customer object on multiple payment types now and is optional on all. This commit adds teh customer subhash to requests and updates the remote tests to pass
Remote:
32 tests, 76 assertions, 7 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications 78.125% passed