`id-denylist` breaks ESLint per Documentation

Currently, the documentation is ambiguous and should use a different syntax. When a user unknowingly removes the first "error" it causes an unexpected breakage.

Change the structure from this:

"id-denylist": ["error", "data", "err", "e", "cb", "callback"]

To something like this:

"id-denylist": ["error", ["data", "err", "e", "cb", "callback"]]

If not do-able, have it implicitly assigned as “error” or “warn” if neither is specified as the first argument.

Currently the only way to diagnose this issue is by linting via CLI. It goes unnoticed in Problems in VSCode.

[anikethsaha]

Thanks for the Issue.

Though in the docs, if you see the options, for incorrect and correct ,

Examples of correct code for this rule with sample "data", "callback" restricted identifiers:

/*eslint id-denylist: ["error", "data", "callback"] */

var encodingOptions = {...};

function processFileResult() {
    // ...
}

With this, I guess it is quite clear. Maybe we can update the docs by breaking down the options and explaining the options?

[eslint-deprecated[bot]]

Unfortunately, it looks like there wasn’t enough interest from the team or community to implement this change. While we wish we’d be able to accommodate everyone’s requests, we do need to prioritize. We’ve found that issues failing to reach accepted status after 21 days tend to never be accepted, and as such, we close those issues. This doesn’t mean the idea isn’t interesting or useful, just that it’s not something the team can commit to.

Thanks for contributing to ESLint and we appreciate your understanding.