Should deleted and experimental plugins be linted?

[nexushoratio]

While manually playing around with some stuff, I noticed that some non-mainstream plugins are flagged with lint issues.

For example:
eqeqeq:

ingress-intel-total-conversion/plugins/deleted/highlight-infrastructure.js

Line 31 in c64ca0e

color = color == 'red' ? 'orange' : 'yellow';

spaced-comment:

ingress-intel-total-conversion/plugins/experimental/marker-canvas-icon-data.js

Line 20 in c64ca0e

marker.bringToFront = function(){}; //TEMP - until the rest of IITC code is changed to take account of non-path markers

I looked for, and could not find, a setting that explicitly disabled those directories.

Granted, I am using an old version of eslint for $REASON, but I was still surprised by a few things.

Maybe a document on how to run eslint from the CLI? I am looking at adding it to post_build in my localbuildsettings.py.

[McBen]

Should deleted and experimental plugins be linted

in fact they should be removed or moved to a experimental branch.
its dead code.

how to run eslint from the CLI

npx eslint <filename>
example: npx eslint ./core/total-conversion-build.js
(replace npx by yarn if you're using yarn package manager)

[nexushoratio]

I've been doing eslint <directory>. As in eslint plugins, or more generally eslint .

I take it that is not how others typically run it?