[clazy] [Bug 409986] New: clazy-standalone should emit supported checks (preferably with more meta data like level and categories)

[Nikolai Kosjar]

https://bugs.kde.org/show_bug.cgi?id=409986

            Bug ID: 409986
           Summary: clazy-standalone should emit supported checks
                    (preferably with more meta data like level and
                    categories)
           Product: clazy
           Version: unspecified
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: wishlist
          Priority: NOR
         Component: general
          Assignee: unassigned-bugs at kde.org
          Reporter: nikolai.kosjar at qt.io
                CC: smartins at kde.org
  Target Milestone: ---

Qt Creator supports only a single clazy version, the one Qt Creator is build
with.

Currently we read checks.json and generate a source file describing the checks
(https://code.qt.io/cgit/qt-creator/qt-creator.git/tree/src/plugins/cpptools/cpptools_clazychecks.h)
with the check name, level and categories. This is presented to the user in
Menu: Tools > Options > C++ > Code Model > "Manage..." and select Clazy tab.

To support multiple clazy versions (e.g. for using newer clazy than Qt Creator
was build against), it's desirable to query the clazy-standalone executable for
supported checks.


Some thoughts/observations:

clang-tidy can dump the supported checks (names) with
    $ clang-tidy "-checks=*" --list-checks

Clazy could do that, too, especially in the light of
https://bugs.kde.org/show_bug.cgi?id=407258

But to support the current clazy UI in Qt Creator, the check names are not
enough. We would also need the level and categories (and later maybe some
description of which checks support which settings).

Should clazy-standalone just dump it's checks.json (or some stripped version of
it) to stdout if requested?

-- 
You are receiving this mail because:
You are the assignee for the bug.