Related to the above, be able to run it in the terminal not just on Windows, but also on Linux and Mac.Besides IDE integration, be able to also execute it in our CI-builds, and make the build fail if there are linting errors.Preferably have integration for both Visual Studio and Visual Studio Code.
So I decided to take a look at the options available today to do linting for. Recently having worked on JavaScript and TypeScript projects, I really started to appreciate how straightforward and established the process of linting is in those communities: it seems to be almost universal that every project in the JS and TS ecosystem is using eslint and tslint respectively, and the way to specify the linting rules is very straightforward. I sporadically experimented with StyleCop, FxCop, or the code style rules of ReSharper, but never ended up using them extensively, or introducing and distributing a maintained configuration in the organization I was working in. I haven’t been using automated code style checking in. Automated, portable code style checking in.
