WalletCallReceipt type improvements (parseEventLogs, etc) #4429
Unanswered
Drewsapple
asked this question in
Idea / Feature Request
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Maybe I'm just missing stuff, but it seems like using
getCallsStatus(and the receipts) requires some type mangling to passreceipts?.[number]["logs"]intoparseEventLogs, despitedecodeEventLogonly needing the topics and data. If the logtopicstype was constrained to[signature: Hex, ...args: topics] | []it would be easier to directly use with decodeEventLog, but I would suggest thatparseEventLogsalso just allowlogsto be(Log | RPCLog)[] | WalletCallReceipt["logs"], so that this utility function can be used for 5792 batches.Happy to make a PR if this is something that makes sense (although I'm sure an agent can knock it out immediately).
Beta Was this translation helpful? Give feedback.
All reactions