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
As discussed during #4260 , assetId field in TransferRequest is not really needed, because the assetId can be obtained from the ContractAgreement targeted by the contractId.
Removing it the API will be easier and there won't be no need to validate it.
Which Areas Would Be Affected?
transfer process api
Why Is the Feature Desired?
cleanup
Solution Proposal
remove the field from TransferRequest, read it from ContractAgreement, deprecate the field on the API and print a deprecation warning when it's used
The text was updated successfully, but these errors were encountered:
Feature Request
As discussed during #4260 ,
assetId
field inTransferRequest
is not really needed, because theassetId
can be obtained from theContractAgreement
targeted by thecontractId
.Removing it the API will be easier and there won't be no need to validate it.
Which Areas Would Be Affected?
transfer process api
Why Is the Feature Desired?
cleanup
Solution Proposal
remove the field from
TransferRequest
, read it fromContractAgreement
, deprecate the field on the API and print a deprecation warning when it's usedThe text was updated successfully, but these errors were encountered: