Consider adding eslint-plugin-inclusive-language

[jdlrobson]

Would help with making our code more inclusive and the effort in https://phabricator.wikimedia.org/T279275
Thoughts?

---

ES: https://github.com/muenzpraeger/eslint-plugin-inclusive-language#readme

[jdforrester]

We could add this, but it's relatively more of an issue on the PHP side of the fence, I feel. The additional processing cost of using this would be pretty trivial, however, so I'm not against.

[edg2s]

It would probably be better implemented as a code-language-agnostic tool like https://github.com/wikimedia/grunt-tyops, otherwise we'll need to re-implement in stylelint, phplint etc.

[jdforrester]

It would probably be better implemented as a code-language-agnostic tool like https://github.com/jdforrester/grunt-tyops, otherwise we'll need to re-implement in stylelint, phplint etc.

Should we just add these as default 'typos' to that repo, then?

[edg2s]

Ideally yes, but there are many places where blacklist/whitelist still need to be mentioned as public or deprecated APIs, or references to 3rd party APIs, and can't be removed for some time.