fix(typescript): improve internal MapFunction type

[ptomulik]

Redefines the MapFunction generic interface, such that it can be reused in a definition of all the overloads in PaginateInerface/ComposePaginateInterface. This shall also prevent further bugs such as #259.

[ptomulik]

By the way, I've seen this comment and I came across the following idea.

interface Overloads {
    0: (t1: number) => number;
    1: (t1: number, t2: number) => number;
}

interface Generate<Prepend extends []|[string]> {
    (...args: [...Prepend, ...Parameters<Overloads[0]>]): ReturnType<Overloads[0]>;
    (...args: [...Prepend, ...Parameters<Overloads[1]>]): ReturnType<Overloads[1]>;
}

type Normal = Generate<[]>; // Generate Overloads
type Prepended = Generate<[string]>; // Generate Overloads with leading argument of type string

const normal: Normal = (t1: number, t2?: number) => {
    return t1 + (t2 === undefined ? 0 : t2);
}

const prepended: Prepended = (s: string, t1: number, t2?: number) => {
    console.log(s);
    return t1 + (t2 === undefined ? 0 : t2);
}

console.log(normal(1));
console.log(normal(1, 2));
console.log(prepended("one", 1));
console.log(prepended("two plus three", 2, 3));

The problem is, however, that argument names are lost, together with docstrings.

[gr2m]

By the way, I've seen this comment and I came across the following idea.

this is great, could you please move it in a separate issue for further discussion?

[gr2m]

very nice, thank you!

[github-actions]

🎉 This PR is included in version 2.13.1 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)

Your semantic-release bot 📦🚀