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, each abi-generated event class has an EventFactory, which provides a filter function that returns a subclass of EventFilterBase. For each Event we know which fields are indexed and what type they are.
We should generate a specific subclass of EventFilterBase for each event, where each subclass contains its topics' type-specific filter methods that encode the specific type (e.g. BigInteger for uint256) into Hash and sets it on the internal LogFilter.
Module
ABI
📝 Description
Currently, each abi-generated event class has an
EventFactory
, which provides afilter
function that returns a subclass ofEventFilterBase
. For each Event we know which fields are indexed and what type they are.We should generate a specific subclass of
EventFilterBase
for each event, where each subclass contains its topics' type-specific filter methods that encode the specific type (e.g.BigInteger
foruint256
) intoHash
and sets it on the internalLogFilter
.For example, we have the following event:
Abigen would generate something like this:
The text was updated successfully, but these errors were encountered: