You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This introduces a breaking change making calls that were working in version 2.0 incompatible with version 2.2. Is that an intentional change? I was a bit surprised to see breaking changes with a minor version.
Thanks for clarification
--Bruno Ritz (ZKB)
The text was updated successfully, but these errors were encountered:
This breaking change was not introduced intentionally. The intention was, and still is, that the accounts property of the requestedAllocation is an array type, as the property implies.
This will be fixed before this version is released.
Best
Thomas
thanks a lot for your quick response. I will therefore (at least as an intermediate fix) manually restore the array type so I can continue with the development and then use the fixed version once it has been released.
Hi,
In Order Placement v2.0.x the
accounts
property of therequestedAllocation
is an array type (see https://github.com/swissfintechinnovations/ca-wealth/blob/main/OrderPlacement.yaml#L354 and https://github.com/swissfintechinnovations/ca-wealth/blob/main/OrderPlacement.yaml#L304) where in version 2.2 it has become a single object (see https://github.com/swissfintechinnovations/ca-wealth/blob/Update-order-placement-api-to-2.2.0/OrderPlacement.yaml#L660). The nameaccounts
of the property still implies plural.This introduces a breaking change making calls that were working in version 2.0 incompatible with version 2.2. Is that an intentional change? I was a bit surprised to see breaking changes with a minor version.
Thanks for clarification
--Bruno Ritz (ZKB)
The text was updated successfully, but these errors were encountered: