prefer-to-be considers RegExp literal notation as a literal

[amikheychik]

The literal notation of a regular expression in JavaScript is still a RegExp object. But The prefer-to-be rule treats literal notation as a literal. So it auto-fixes .toStrictEqual into .toBe, causing tests to fail.

For example, given two tests that pass:

it('is an example', () => {
  const token: RegExp = new RegExp('[abc]+', 'gu');

  expect(token).toStrictEqual(/[abc]+/gu);
  expect(token).toStrictEqual(new RegExp('[abc]+', 'gu'));
});

Is changed into:

it('is an example', () => {
  const token: RegExp = new RegExp('[abc]+', 'gu');

  expect(token).toBe(/[abc]+/gu);
  expect(token).toStrictEqual(new RegExp('[abc]+', 'gu'));
});

And the .toBe test fails

[G-Rath]

Ah good catch! thanks

[github-actions]

🎉 This issue has been resolved in version 24.5.1 🎉

The release is available on:

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

Your semantic-release bot 📦🚀

[github-actions]

🎉 This issue has been resolved in version 25.0.0-next.6 🎉

The release is available on:

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

Your semantic-release bot 📦🚀