Properties in BankingTransactionDetail objects #414
Labels
Banking
Banking domain APIs
Proposal made
The DSB has proposed a specific change to the standards to address the change request
Comments
|
This appears to be a defect and it is proposed that it is simply fixed according to the Change Proposed section of the issue. |
CDR-API-Stream
added
the
Proposal made
|
This change has been staged for review: ConsumerDataStandardsAustralia/standards-staging@release/1.19.0...maintenance/414 |
|
This change has been updated to target v1.20.0: ConsumerDataStandardsAustralia/standards-staging@release/1.20.0...maintenance/414 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
The swagger JSON and the documentation of properties in the BankingTransactionDetail schema seem to be misaligned.
Area Affected
BankingTransactionDetail extendedData schema documentation and related Swagger objects.
Change Proposed
The
extendedDescriptionproperty shows asx-conditionalin theBankingTransactionDetail_extendedDataobject (but it's not present there), and also shows asrequiredin theBankingTransactionDetail_extendedData_x2p101Payloadobject (where the property is actually present).The standards documentation shows that field as
mandatory, but the Description includes a condition -An extended string description. Only present if specified by the extensionUType field
Can these details be clarified?
DSB Proposed Solution
The current DSB proposal for this issue is in this comment
The text was updated successfully, but these errors were encountered: