Becoming ESLint-like

Just to get the discussion rolling, I was wondering if it might make sense to conform to some of ESLint’s CLI and options given how this project uses a lot of the great ideas that have come out of ESLint.

Some ideas (that may be better as separate issues if agreed upon):

• Change solhint.json to solhintrc.json (we could use cosmiconfig for this)
• Change init-config to --init
• Add support for using 0, 1, and 2 as severity levels (or state that you can only use “off”, “warn”, “error”) (see also #43)
• Add --quiet to only report errors
• Add support for a .ignores-type file
• Add support for custom rulesets, and inheriting from them
• Add support for custom plugins, and moving the security rules into a solhint-plugin-security-type package

A lot of these features are either present or coming via solium@1, but I don’t see much of a point in having both when solhint seems like a cleaner implementation already using antlr4.

[GopherJ]

I’m finding actually a perfect vim support for solhint and come across this. Feel it brings lots of value to be eslint-like so that solhint can benefit from eslint’s ecosystem. Solhint can even become a plugin of eslint if possible.

I use coc-eslint (https://github.com/neoclide/coc-eslint) and did some search this morning to see if it’s possible for coc-eslint to support solhint but seems not possible

[fvictorio]

None of the items listed was done, so I don’t see why would we close it, except maybe to open a separate issue for each item.