Skip to content
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

DPK-2958 Support V20201031 in Customer Object SDK #205

Closed
wants to merge 2 commits into from

Conversation

xendit-aw007
Copy link

What? (You can share the JIRA Ticket here)

How? (Explain the Expected Outcome/Success criteria)

  • Feature: Update API for Customer Object
  • Unit Test: Update API for Customer Object

Testing?

  • Manually

Anything Else?

  • Test Customer Example

2023-08-09_17-42
2023-08-09_17-42_1
2023-08-09_17-42_2

  • Unit Tests are green

2023-08-09_17-45

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If this is the default customer API version now, should we just keep the file name instead of renaming the file to account for the version?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the default is the other one v20201031, let me rename that one

@@ -19,7 +65,7 @@ export = class Customer {
referenceID: string;
mobileNumber?: string;
email?: string;
givenNames: string;
givenNames?: string;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

shouldn't this field be mandatory?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

for v20200519, yes it's mandatory
but for v20201031, we don't have that field anymore, it will be under individualDetail

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants