prefer-to-have-value having unintended effects

• eslint-plugin-jest-dom version: 3.5.0
• node version: 10.22.0
• npm version: 6.14.6

Relevant code or config

const gen = someGeneratorFunction();
expect(gen.next().value).toEqual(someYieldedValue);

What you did: ^

What happened: Prefer .toHaveValue() over other attribute checks

Problem description: The new rule prefer-to-have-value is causing unintended warnings when checking the value key on objects that are not DOM elements.

Suggested solution: I’m not sure if there’s a graceful solution that can allow for triggering warnings on element.value but not on obj.value (let me know if I’m wrong!). But I think a reasonable middle ground would be to allow a configuration option to only trigger a warning on expect(element).toHaveAttribute('value', 'someValue') so I don’t have to individually turn off the rule everywhere I’m testing generators.

[juzerzarif]

@benmonro That would be the best of both worlds, sounds like the way to go! I can mess around with it and see about a PR this weekend

[benmonro]

doh, yes it was a mis-click sorry