Open j-ka11 opened 4 years ago
I think it will be a good idea to focus first on shrinking the list of clang-tidy rules used, otherwise we will have to make a lot of unnecessary changes to the code in order to get it through branch protections. Once that is done, we can focus on adding other tools.
Currently, the Lint Job for Travis is a simple check with
clang-tidy
and default options (which means all rules are evaluated). Since the list of all possible rules is very large, there have already been unnecessary rules that makeclang-tidy
checks fail. We need to shorten the list of rules thatclang-tidy
evaluates. Additionally,clang-tidy
only checks a narrow area of coding style and coding conventions. To enhance the Lint job, we need improvement in two areas:clang-tidy
rules we don't want to define and add it to the.travis.yml
file. Preferably, be conservative when deciding to not follow a rule as this will result in cleaner code in the end.