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
When i make a contract call e.g.:
tx1 = cc.secured_asset.execute({"secure_asset": {}}, acc_admin)
and then view the events in the response:
tx1.response.events["wasm"]
I expect the results to be accessible in a list form as they are in cosmjs (though the current dictionary form is useful when making simple calls - so should not be removed)
Current Behavior
The result comes back as a dictionary of key value pairs. This is unhelpful when the contract call has made other contract calls as all the results come back munged into the same dictionary. this means:
A - You don't know which keyvalue pairs have come from which contracts
B - If two pairs have the same key then one overwrites the other.
Prerequisites
Expected Behavior
When i make a contract call e.g.:
tx1 = cc.secured_asset.execute({"secure_asset": {}}, acc_admin)
and then view the events in the response:
tx1.response.events["wasm"]
I expect the results to be accessible in a list form as they are in cosmjs (though the current dictionary form is useful when making simple calls - so should not be removed)
Current Behavior
The result comes back as a dictionary of key value pairs. This is unhelpful when the contract call has made other contract calls as all the results come back munged into the same dictionary. this means:
A - You don't know which keyvalue pairs have come from which contracts
B - If two pairs have the same key then one overwrites the other.
To Reproduce
Get and build this project:
https://github.com/fetchai/atomix_contracts/tree/develop
start up a jenesis shell like this;
DT_MODE=stepped jenesis shell --profile local
Paste in this:
See how the events pairs are printed out - the proxy user contract makes lots of calls to other contracts and it is all mungd together
Context
Max OS
Failure Logs
No response
The text was updated successfully, but these errors were encountered: