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
In the web3 target, the contract's events member specifies each event twice, with and without the optional options parameter first, followed by an allEvents item that has only the latter:
This threw me for a bit of a loop because I had a type definition matching the majority of those events and checked for events to be a string-indexed object collecting those, and allEvents broke this pattern so it failed typechecking. I think I was able to get a workaround by modifying the type definition to fit allEvents and the others fit that too, but it makes me wonder why that difference is there and if it really should be, or if an additional line should be emitted, just before the last of those: allEvents(cb?: Callback<EventLog>): EventEmitter;.
The text was updated successfully, but these errors were encountered:
In the web3 target, the contract's
events
member specifies each event twice, with and without the optional options parameter first, followed by anallEvents
item that has only the latter:This threw me for a bit of a loop because I had a type definition matching the majority of those events and checked for
events
to be a string-indexed object collecting those, andallEvents
broke this pattern so it failed typechecking. I think I was able to get a workaround by modifying the type definition to fit allEvents and the others fit that too, but it makes me wonder why that difference is there and if it really should be, or if an additional line should be emitted, just before the last of those:allEvents(cb?: Callback<EventLog>): EventEmitter;
.The text was updated successfully, but these errors were encountered: