[no-standalone-expect]: false positive for expect.any in __mocks__ file

[garyking]

I have a file in __mocks__ called twitch-js-api.js and I'm using the following:

const formatStreams = jest.fn().mockReturnValue([
  {
    channel: {
      logo: expect.any(String)
    }
  }
])

Yet this rule now warns on expect.any(String)? Isn't expect allowed in mock files? This code has worked for years.

[G-Rath]

Technically the rule is correct, and the fact that it wasn't erroring before was arguably a bug but I'm thinking maybe we should actually ignore except member calls except for hasAssertions and assertions as everything is valid to be used outside of test blocks 🤔

[G-Rath]

I'm going to close this as a duplicate of #1186

[github-actions]

🎉 This issue has been resolved in version 26.8.1 🎉

The release is available on:

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

Your semantic-release bot 📦🚀