Rule proposal: prefer-textcontent

[sindresorhus]

Idea from: refined-github/refined-github#1088 (comment)

Prefer node.textContent over node.innerText.

See: https://stackoverflow.com/a/35213639/64949

With ESLint, we can't know the type, but I guess we can safely assume .innerText refers to a DOM element, and if not, you can always disable it. Maybe it would be possible if env is browser and only validate then.

Thoughts?

alexzherdev earned $60.00 by resolving this issue!

• Checkout the Issuehunt explorer to discover more funded issues.
• Need some help from other developers? Add your repositories on Issuehunt to raise funds.

[IssueHuntBot]

@issuehuntfest has funded $60.00 to this issue. See it on IssueHunt

[alexzherdev]

@sindresorhus I'm willing to work on this 👍Do you have a preferred way of determining we're in a browser?
Opened #223 for now.

[IssueHuntBot]

@alexzherdev has submitted a pull request. See it on IssueHunt

[sindresorhus]

Do you have a preferred way of determining we're in a browser?

There's no way to know that. We'll just have to assume .innerText means the node property.

[alexzherdev]

Oh you're right, I confused with runtime detection 🤦‍♂️

[IssueHuntBot]

@sindresorhus has rewarded $54.00 to @alexzherdev. See it on IssueHunt

• 💰 Total deposit: $60.00
• 🎉 Repository reward(0%): $0.00
• 🔧 Service fee(10%): $6.00