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
Currently, the TS SDK decodes all logs from a transaction and stores them in an array under the logs property of the transaction result.
However, all decoded log values are grouped together in the same array. This makes it difficult to determine which log belongs to which contract in cases where a contract makes an inter-contract call and the called contract also produces logs.
As a result, users may struggle to identify the logs relevant to them.
To address this, we need to associate each log with its corresponding contract by using the contract ID during log decoding.
The text was updated successfully, but these errors were encountered:
Currently, the TS SDK decodes all logs from a transaction and stores them in an array under the logs property of the transaction result.
However, all decoded log values are grouped together in the same array. This makes it difficult to determine which log belongs to which contract in cases where a contract makes an inter-contract call and the called contract also produces logs.
As a result, users may struggle to identify the logs relevant to them.
To address this, we need to associate each log with its corresponding contract by using the contract ID during log decoding.
The text was updated successfully, but these errors were encountered: