No explanation for jest/no-restricted-matchers

I can’t find any rationale for why these particular matchers are restricted.

d3a48e6a3fade2c8dba6b3adda395fec39365986

The jest/no-restricted-matchers rule can be configured to suggest an alternative to the restricted method. Please add some sort of explanation, even if there’s no alternative.

     {
        "jest/no-restricted-matchers": [
          "error",
          {
            "toMatchSnapshot": "Write a more targeted assertion instead of a snapshot",
            "toMatchInlineSnapshot": "Write a more targeted assertion instead of a snapshot",
            "toThrowErrorMatchingSnapshot": "Write a more targeted assertion instead of a snapshot",
            "toThrowErrorMatchingInlineSnapshot": "Write a more targeted assertion instead of a snapshot",

            "toBeTruthy": "use expect(x == true).toBeTrue() instead",
            "toBeFalsy":  "use expect(x == false).toBeTrue()  instead",
            "toBeDefined": "use .not.toBe(undefined)"
          }
        ]
      }

Or, preferably, remove these rules. Especially the toBeTruthy, toBeFalsy, and toBeDefined ones. IMHO the alternatives are much more error prone.

[pmcelhaney]

Okay, I’ll add some explanations and leave it at that.

I agree with you about snapshot testing. Didn’t even know the rule existed until I looked at the config. 😃

[EvgenyOrekhov]

Released in v24.4.0.