-
Notifications
You must be signed in to change notification settings - Fork 0
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
Feature/acp 4656/master adjust event status payment history #27
Feature/acp 4656/master adjust event status payment history #27
Conversation
…and PaymentUpdated messages.
…e structure used on SCCOS side.
</transfer> | ||
|
||
<transfer name="PaymentStatusHistoryCollection" strict="true"> | ||
<property name="paymentStatusHistory" type="PaymentStatusHistory[]" singular="paymentStatusHistory"/> |
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.
<property name="paymentStatusHistory" type="PaymentStatusHistory[]" singular="paymentStatusHistory"/> | |
<property name="paymentStatusHistoryItems" type="PaymentStatusHistory[]" singular="paymentStatusHistoryItem"/> |
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 was also thinking about a different name here. "Item" reminds me too much of an order item. How about using just PaymentStatus
and PaymentStatusHistory
? The latter is the collection and the first is an "item" in the history.
I will go for it.
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.
Applied, looks much more natural now. The PaymentStatusHistory implies already that it is a collection that contains PaymentStates aka PaymentStatusTransfer's.
SCCOS Sales Detail Page with changes down below: