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
What is the current behavior and expected behavior?
The return result of executing a smart contract of pallet-contracts via the RPC method call is of type ContractExecResult.
This type contains an entry of type ContractReturnFlags. This type is defined as
export interface ContractReturnFlags extends Set {
readonly isRevert: boolean;
}
However, the actual value returned changed between version 13.1.1 and version 13.2.1. Given a value flags of type ContractReturnFlags and executing the following line:
I'm submitting a ...
What is the current behavior and expected behavior?
The return result of executing a smart contract of pallet-contracts via the RPC method
call
is of typeContractExecResult
.This type contains an entry of type
ContractReturnFlags
. This type is defined asHowever, the actual value returned changed between version 13.1.1 and version 13.2.1. Given a value
flags
of typeContractReturnFlags
and executing the following line:results in the following output:
at version 13.1.1
[] undefined false
[ 'Revert' ] undefined true
On version 13.2.1 I get the output instead:
{ bits: '0' } 0 undefined
{ bits: '1' } 1 undefined
This suggests that the decoding has an unintended breaking change or the typings should be adapted. Possibly other bitflag types are affected as well.
Please tell us about your environment:
Version: 13.1.1 and 13.2.1
Environment:
Language:
The text was updated successfully, but these errors were encountered: