prevent-abbreviations should check all-uppercase variable names

[ehmicky]

a.js:

const opts = []

$ eslint a.js
/home/user/a.js
  1:7  error  The variable `opts` should be named `options`. A more descriptive name will do too  unicorn/prevent-abbreviations

✖ 1 problem (1 error, 0 warnings)
  1 error and 0 warnings potentially fixable with the `--fix` option.

b.js:

const OPTS = []

$ eslint b.js

b.js does not report any error but it should.

Configuration

.eslintrc.json:

{
  "parserOptions": {
    "ecmaVersion": 2019
  },
  "plugins": ["unicorn"],
  "rules": {
    "unicorn/prevent-abbreviations": "error"
  }
}

Environment

$ npm ls eslint eslint-plugin-unicorn
desktop@1.0.0 /home/user/Desktop
├── eslint@5.15.3 
└── eslint-plugin-unicorn@8.0.0

$ node --version
v11.12.0

$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 18.10
Release:	18.10
Codename:	cosmic

[sindresorhus]

It was an intentional choice to ignore those:

• Add prevent-abbreviations rule #237 (comment)
• 7503555

[ehmicky]

Reading up the comment, it seems that the reason was to prevent reporting environment variables, since they are almost always uppercase, and user might not decide on them considering they come from the calling process.

This makes sense.

However, it's too bad because some users (like me) like to name constants with uppercase letters. Those variables cannot be linted. Is there a way this could be done without getting issues with environment variables?

[fregante]

Closing for now, no movement in 3+ years