https://bugs.kde.org/show_bug.cgi?id=513153
Sergey Katunin <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #6 from Sergey Katunin <[email protected]> --- Clazy no longer export diagnostics (warnings) that doesn't have fixits since v1.16 (https://invent.kde.org/sdk/clazy/-/commit/941406ecdb809dc739425c4b9465d0bc5b1297bb). This leads to the fact that now Qt Creator does not display these warnings. Moreover, looks like that many warnings should to have a fix-it, for example, `clazy-empty-qstringliteral`, but they do not have a fix-it, and therefore they are also not displayed now. At the same time, Clazy continues to output these warnings in the stderr log. Apparently, the Clazy plugin in Qt Creator now has to parse these warnings in some other way in order to display all warnings as before. I created a bug report in Qt about it here: https://qt-project.atlassian.net/browse/QTCREATORBUG-34068 -- You are receiving this mail because: You are watching all bug changes.
