Closed jackalcooper closed 4 years ago
Yeah, I can add some log some information.
Could you please provide some more detail about the problem you ran into? Directory layout, filenames of problematic files, any other information you think may be relevant.
I'm logging the clang-tidy command invocation and the raw clang-tidy output now, see #2. It's available in master, but not released yet. Let me know if there's any other info you'd like to see in the logs.
Released in version 0.2.0.
I just found out that the official clangd vscode extension by LLVM now integrates clang tidy and clang format altogether if you are using LLVM 9.
Yeah, I've seen that. I love the idea of clang-tidy being part of language servers. Unfortunately, clangd doesn't work as well as other language servers for me. It has been a little while since I've tried it, though.
For now, I think there's still plenty of value in this extension.
I see. I also found the integration not that useful since it didn't give me any useful information about my code.
First, thanks for your work on this extension. Is it possible to add some log information in VS Code's output panel (View -> Output)? I could only get the diagnostics from limited files. It would be great if there is some logging so it is easier to figure out what goes wrong.
Thanks again.