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 was thinking about how to improve pure SDK usage for contract calls and I think the JS-SDK is doing this quite will right now. it is converting the Sophia types.
Example calls that should be possible using the SDK:
there are now convenience methods in the SDK for contract creation and regular stateful calls where a ContractTxOptions object can be passed to that can contain different params.
for read-only (dry-run) calls there is also a specific convenience method in the SDK now where we don't need any additional params as we always use the zero-address in those read-only dry-runs.
marc0olo
changed the title
consider outsourcing default Sophia types & type-conversion
refactor contract calls: convenience methods in SDK and SophiaTypes in SDK
Jan 3, 2022
I was thinking about how to improve pure SDK usage for contract calls and I think the JS-SDK is doing this quite will right now. it is converting the Sophia types.
Example calls that should be possible using the SDK:
deploy(txOptions: ContractTxOptions)
call(contractId: String, entrypoint: String, txOptions: ContractTxOptions)
(for stateful and payable calls)callReadOnly(contractId: String, entrypoint: String)
(for read-only dry-run calls)I see following tasks in this issue:
The text was updated successfully, but these errors were encountered: