[bug] useContractEvent callback args does not behave like ethers contract.on(<event>, callback)

[the-vampiire]

Is there an existing issue for this?

• I have searched the existing issues

Package Version

0.4.3

Current Behavior

either case

• callback receives all event params as an array in a single arg

when specifying the contract type in the generic

• does not allow EventFilter as arg for event (requires it to be a string event name)

Expected Behavior

• callback receives the args spread in event parameter order (like calling contract.on(eventName/eventFilter, callback)
• providing the contract type allows either string or EventFilter arg

Steps To Reproduce

// this is accepted by ts compiler
  useContractEvent(
    contractConfig,
    filterForEvent, // EventFilter 
    console.log, // gives all event args as a single array [param1, ...paramN, eventObject]
  );

// not behaving same as
contract.on(filterForEvent, console.log);
// in this one the callback receives each event param as an argument, the final arg being the entire event object, (param1, ...paramN, eventObject)

// this is not accepted by ts compiler
  useContractEvent<ContractType>(
    contractConfig,
    filterForEvent, // EventFilter, only accepts string event name
    console.log, // gives all event args as a single array
  );

the latter typing issue appears to be due to overloading in the typechain defs:

// ContractType def (class) gen by typechain
  on<EventArgsArray extends Array<any>, EventArgsObject>(
    eventFilter: TypedEventFilter<EventArgsArray, EventArgsObject>,
    listener: TypedListener<EventArgsArray, EventArgsObject>
  ): this;

  on(eventName: string, listener: Listener): this;

when i comment out the string overload it stops complaining.

Link to Minimal Reproducible Example (CodeSandbox, StackBlitz, etc.)

No response

Anything else?

No response