Wrong TypeScript typing for toBeDateString (and possibly toBeHexadecimal)

[AudunWA]

Bug

• package version: 1.1.0
• node version: v14.17.0
• npm (or yarn) version: npm 7.24.1

The type for toBeDateString expects a string argument; see the example below:

it("Demonstrates the wrong typing", () => {
    const validDateString = new Date().toISOString();

    // TS2554: Expected 1 arguments, but got 0.
    expect(validDateString).toBeDateString();

    // Works
    (expect(validDateString).toBeDateString as any)();

    const validDateStringInObject = { validDateString };

    // The .not prefix does not work in cases like this
    expect(validDateStringInObject).toEqual({
        // TS2339: Property 'toBeDateString' does not exist on type 'InverseAsymmetricMatchers'.
        validDateString: expect.not.toBeDateString(),
    });
});

I suspect this issue might affect toBeHexadecimal as well.

[SimenB]

PR welcome 🙂

[dharkness]

Sorry for the churn. I accidentally pushed changes for a new PR to the branch. I deleted the PR and branch and started over.