fix: makeEventFunctions take an array of parameters

[mofojed]

• Previously every emit required exactly one parameter, which is not the case
• Allow zero or more parameters

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 46.65%. Comparing base (a257296) to head (61f0c15).
Report is 6 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2186      +/-   ##
==========================================
- Coverage   46.66%   46.65%   -0.02%     
==========================================
  Files         692      692              
  Lines       38629    38583      -46     
  Branches     9814     9845      +31     
==========================================
- Hits        18028    18000      -28     
+ Misses      20548    20530      -18     
  Partials       53       53              

Flag	Coverage Δ
unit	46.65% <100.00%> (-0.02%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[mattrunyon]

Not entirely sure where you'd want to put it or how to incorporate it, but you can use conditional types to support a non-array type as a single param, array/tuple

type MyFunc<P = []> = (...params: P extends unknown[] ? P : [P]) => void;

Also an interesting thing I saw was you can label tuples for argument signatures. See here for more info, but the gist is you could do makeEventFunctions<[count: number, title: string]>(...) and TS should then show the params as count and title in autocomplete instead of arg0 and arg1