-
-
Notifications
You must be signed in to change notification settings - Fork 821
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: decodeEventLog topics mismatch #198
Conversation
🦋 Changeset detectedLatest commit: 07071cd The changes in this PR will be included in the next version bump. 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 |
@wighawag is attempting to deploy a commit to the wagmi Team on Vercel. A member of the Team first needs to authorize it. |
Thanks for the PR! Just added some refactors I've been meaning to do which will also close #180 as well. |
for (let i = 0; i < inputs.length; i++) { | ||
const param = inputs[i] | ||
const topic = argTopics[i] | ||
if (topic === null) args[param.name || i] = null |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removed as a topic on a log cannot be null
.
const topic = argTopics[i] | ||
if (topic === null) args[param.name || i] = null | ||
if (!topic) continue | ||
if (Array.isArray(topic)) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removed as a topic on a log cannot be an array.
ha yes was wondering about those topic values myself :) |
Fixes #197
Fixes #180