The jasmine/prefer-toBeUndefined rule produces an Assertion error when any spec file is found that contains a hit (e.g. expect(undefined).toBe(undefined) with {"jasmine/prefer-toBeUndefined": "error"} config).
The error only occurs on versions 4.x.x and did not occur on 3.0.0.
To Reproduce
Set the jasmine/prefer-toBeUndefined config to "error" and produce an error in any spec file. Afterwards, lint that file. This produces the following error and crashes eslint:
Describe the bug
The
jasmine/prefer-toBeUndefined
rule produces an Assertion error when any spec file is found that contains a hit (e.g.expect(undefined).toBe(undefined)
with{"jasmine/prefer-toBeUndefined": "error"}
config).The error only occurs on versions 4.x.x and did not occur on 3.0.0.
To Reproduce
Set the
jasmine/prefer-toBeUndefined
config to"error"
and produce an error in any spec file. Afterwards, lint that file. This produces the following error and crashes eslint:Expected behaviour
Eslint should report the error as usual and should not crash.
Context