Repository navigation
Add custom config entries to Log Diagnostics #4826
Description
Type: LanguageService
The Log Diagnostics command prints out the current config, but doesn't list the "special" configurations like compile_commands.json and custom configs. We should be able to print out the entries for the active translation units as well as the "custom browse path" (if set).
Activity
sean-mcmanus commentedon Apr 24, 2020
Bob Brown (@bobbrow) I don't understand what this issue is about exactly -- what info should be added? Just the custom config browse path? What is there to print about the compile commands that isn't already printed?
bobbrow commentedon May 5, 2020
For translation units (e.g. Foo.cpp), we'd want to print out the verbatim compile commands entry for it (or the custom config we received for it). This allows us to check whether data was lost or misinterpreted before creating the TU for it.
For browse path, this should be relatively easy in the config provider scenario. For compile commands, you'd build on the work Elaheh Rashedi (@elahehrashedi) just did.
bobbrow commentedon Jul 10, 2020
The work for custom configurations is done. A new issue will be created for compile_commands.json logging
[-]Add compile commands/custom config entries to Log Diagnostics[/-][+]Add custom config entries to Log Diagnostics[/+]