`no-useless-undefined`: `undefined` removed from jest function matchers

test('function called with different parameters that could be undefined', () => {
	expect(someFunction).toHaveBeenCalledWith(1, 2, 3);
	expect(someFunction).toHaveBeenCalledWith(1, undefined, 3);
	expect(someFunction).toHaveBeenCalledWith(1, 2, undefined);
});

This is breaking as jest toHaveBeenCalledWith (and other similar matchers) explicitly checks for nth argument to be undefined

Would be better if this rule would accept and array of “acceptable” functions that have undefined?

[silverwind]

Essentially it’s a unsolvable problem but I guess a allowlist of common usages of undefined is a bandaid fix that might ease the pain in some cases. Still I have the rule disabled and would not recommend enabling it 😉.

[fisker]

Yap, the simplest way to fix this is add this name to that list.