feat: filter contract logs for events

[lcamargof]

Description of changes

Avoid No Matching event by only calling parseLog on the logs that correspond to the current contract called.

Notes:

I'm not sure if this is the best solution for the problem, ideally we should return the logs unparsed but that can be found in the transaction itself

[changeset-bot]

🦋 Changeset detected

Latest commit: f5408d3

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 3 packages

Name	Type
@usedapp/core	Minor
@usedapp/coingecko	Patch
@usedapp/example	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[quagliero]

Just stumbled across this as having the same error. Nice one.

[quagliero]

For anyone else arriving here, this error was introduced in the most recent relase (0.4.4), so if you fix to version 0.4.3 you're OK.

[Szymx95]

Maybe we should pass the filtering function as argument to useContractFunction

useContractFunction(..., filteringFunction?: (e:any) => boolean)

So that developers can have more control and as default it can be left filtering address of contract

[lcamargof]

Maybe we should pass the filtering function as argument to useContractFunction

useContractFunction(..., filteringFunction?: (e:any) => boolean)

So that developers can have more control and as default it can be left filtering address of contract

More than a filtering function I would say it's a parse function, where manually they read the logs and parse the event with the corresponding contract Abi, this could be an empty function to get the raw logs

[mirkopezo]

I still have this issue even after updating to [email protected], it only throws error when calling smart contract function that has emit keyword in it. In my case I am calling _mint function from OpenZeppelin ERC20.