The implementation of the functions inside the class TokenOperationsOutcomeParser expect transactions to have only one event of interest: "issue", "ESDTNFTCreate", "ESDTLocalBurn", etc.
However this condition is not true, especially for indirect events in smart contract calls.
Here is a reproducible example:
import {ProxyNetworkProvider} from "@multiversx/sdk-network-providers/out"
import {TokenOperationsOutcomeParser} from "@multiversx/sdk-core/out"
async function main() {
const provider = new ProxyNetworkProvider("https://gateway.multiversx.com")
const tx = await provider.getTransaction("8c972e4756c553f11ba5dbdb74d9152c6bd0305761cd675b8b3945977d1d2a1a")
const parser = new TokenOperationsOutcomeParser()
const result = parser.parseNFTCreate(tx)
console.log(result)
}
main()
The implementation of the functions inside the class
TokenOperationsOutcomeParser
expect transactions to have only one event of interest: "issue", "ESDTNFTCreate", "ESDTLocalBurn", etc.However this condition is not true, especially for indirect events in smart contract calls.
Here is a reproducible example: