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
I noticed the api broke at this commit 6508a5f8939bab5fa6ca8df0e1d056585607c5e6 and after the described api call I could not decode json to valid ApiConstructionType.
Description
There are couple of new fields in ApiCoinSelection (which is part of the mentioned type ApiConstructTransaction) namely depositsTaken and depositsReturned which somehow don't end up being inside of the returned json (only deposits key exists which is part of the old api).
This is the complete response I get for the reference:
I am happy to provide more input or work on fixing this. From taking a glance at the code I didn't see immediately what is exactly off here since json instances are derived using generics, might be something is not correct in the client.
The text was updated successfully, but these errors were encountered:
Just checking...
cardano-wallet
bug.cardano-wallet
release.cardano-node
version for that release ofcardano-wallet
.Version
6508a5f
Platform
NixOs
Installation method
Built from source
Network configuration
testnet
Context
We have a http call to cardano-wallet api to construct a transaction (https://input-output-hk.github.io/cardano-wallet/api/edge/#operation/constructTransaction) and eventually end up with the correct
ApiConstructTransaction
type.I noticed the api broke at this commit
6508a5f8939bab5fa6ca8df0e1d056585607c5e6
and after the described api call I could not decode json to validApiConstructionType
.Description
There are couple of new fields in
ApiCoinSelection
(which is part of the mentioned typeApiConstructTransaction
) namelydepositsTaken
anddepositsReturned
which somehow don't end up being inside of the returned json (onlydeposits
key exists which is part of the old api).This is the complete response I get for the reference:
I am happy to provide more input or work on fixing this. From taking a glance at the code I didn't see immediately what is exactly off here since json instances are derived using generics, might be something is not correct in the client.
The text was updated successfully, but these errors were encountered: