feat(rpc-types): add topic0 (alias event_signature
) getter to Log
#799
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
Currently there is not an elegant way of accessing the event signature in the
Log
as returned by theSubscriptionStream
, which is useful for matching against when one subscribes to all (or multiple) contract events.For context: https://github.com/alloy-rs/examples/blob/dbe65d8ca96348ffa64720ea566079e7c1e87fbf/examples/subscriptions/examples/subscribe_all_logs.rs#L45-L62
Solution
Adds simple getter for 0-indexing intotopics
, mirrors theevent_signature
syntax used for settingtopic0
on theFilter
instance. I don't see a good reason to add getters for the other topics.Adds simple getter for
topic0
, checking for existence.PR Checklist