https://bugs.kde.org/show_bug.cgi?id=513153
--- Comment #2 from Trần Nam Tuấn (Bill) <[email protected]> --- (In reply to Alexander Lohnau from comment #1) > Hmm, but why should clazy export warnings when the export option only > mentions fixes? > > Like this was a change to prevent clazy from generating those files even if > there was no fixit that could be applied. I'm currently maintaining a VSCode extension for Clazy [1] which derived from another extension for clang-tidy. From the original extension, it seemed that clang-tidy itself also exported warning along with fixes (though I have not yet tested this with more recent version of clang-tidy since clangd has already filled that role). And for a while Clazy also did the same until the new version. I have already adapted my extension to parse the warning from stderr in addition to the exported diagnostics. Though, that has its own limitation. The warnings from stderr do not provide accurate/easily-parsable ranges of the affected code. Only the starting line and column can be extracted from the warning message. This makes it difficult to provide highlighting with the editor. (Unless, there is a better way of doing this that I am not aware of.) I have elected to just reported only one character from the start position, which give a very cute and small yellow squiggly line in the editor. I do understand the reasoning that the option only mention fixes. I was just unsure if this was intended as, at the time, I didn't see it was mentioned in the changelog. [1] https://gitlab.com/TheBill2001/vscode-clazy -- You are receiving this mail because: You are watching all bug changes.
