Not for a long just few days.
It could be too strict , probably that why they rejected PR ,
but it depends of callback definition.
I proposed it as a flag because it is breaking change by default turn it off.
But as they rejected PR in my fork
I remove flag and in latest version is always on.No flag.
I change one my repo to use it and need to patch some lib definition of
callback to be more strict also build with typescript "skipLibCheck": true,
If I do not want to change existing code to add parameters for each callback
I use trick bellow :
type JavaScriptCallback<
T extends (...args: any) => any,
P = Parameters<T>
> = P extends [...infer Rest, infer _Last]
? ((...args: Rest) => ReturnType<T>) | JavaScriptCallback<T, Rest>
: T;
interface Array<T> {
forEach(
callbackfn: JavaScriptCallback<(value: T, index: number, array: T[]) => void>,
thisArg?: any
): void;
map<U>(
callbackfn: JavaScriptCallback<(value: T, index: number, array: T[]) => U>,
thisArg?: any
): U[];
}
and then is more like standard TypeScript would not complain about
parseInt because I redefined typedef of map
to accept 0 or 1 or 2 or 3 parameters .
But I am in control.
Only edge cases in some callbacks I notice tsc complains that type is any with strict option turn on
then I add a type .
It is experimental, would prefer if they add it as option.
Change is just in checker emitted JavaScript is still same.
As always there are some trades of.
But for me it works so far so good ;-)