Open TomerAberbach opened 11 months ago
Realized that no-standalone-expect
has the same issue. It has the same configuration options
Indeed probably worth proposing that as an improvement of the eslint rules. š¤
By the way, while test.prop
seems more natural with Jest runner, I may have something Ć -la testProp (probably called fuzz) for vitest. The maintainers of vitest recommended to create a new name if I want to extend their runner.
Indeed probably worth proposing that as an improvement of the eslint rules. š¤
Did you want me to file the issue or did you want to do it? I'm good either way
I prefer if you open it. You have more context on what you tried
š Bug Report
I used to configure
eslint-plugin-jest
'sexpect-expect
rule like so:And it would work for
fast-check
'stestProp
function. However, now thattest.prop
is preferred andtestProp
is deprecated, I tried switching to:But unfortunately this doesn't work. Probably because with
test.prop
the test function is not actually contained within the parentheses oftest.prop(...)
and is instead contained within the parentheses of an anonymous function returned bytest.prop
.I understand that
test.prop
is attempting to matchtest.each
so maybe what we need to do is make a feature request foreslint-plugin-jest
to support configuringtest.each
-like functions.What do you think?