-
Notifications
You must be signed in to change notification settings - Fork 5
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
Add support for AdminRequest
Sessions
#25
Conversation
Hi @amcalgates, Thank you so much for taking the time to contribute to our repository. Regards, |
- Add `OperationVariant` enum - Add comment stubs for inits to match rest of code base - Fix spacing in variable declarations - Capitalize first word in comments
I've made all requested changes, except for one comment I was unsure on (see my inline replies). |
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.
Thanks for updating the PR. I made a few small comments.
Could you also make sure the headers in every file have the following format
//
// {FILENAME}.swift
// TerminalAPIKit
//
// Copyright (c) 2023 Adyen N.V.
//
I've made most of the requested changes, and left comments in areas I need more clarification on. |
@kaphacius - any follow-up on my comments? |
hey @amcalgates |
Summary
Adds support for
AdminRequest
Begin/End session as seen in Create a session documentation.All added classes/additions mirror the naming found in that documentation, however I had to introduce a new class which I named
SessionContainer
to combine theSession
and[Operation]
objects for JSON serialization, which can then be base64 encoded to a string and used forAdminRequest.ServiceIdentification
Please let me know if you'd prefer a different name for
SessionContainer
- I couldn't find a similar concept in adyen-terminal-api-ios to base the naming off of.Tested scenarios
I've tested this with both Begin and End session calls using an AMS1 device.