Allow for Additional Problem Matchers to be defined in the settings #4077
Labels
enhancement
an enhancement to the product that is either not present or an improvement to an existing feature
Feature: UI
more votes needed
We currently are de-prioritizing this issue until more community up-votes are provided
Milestone
Brief Issue Summary
When using CMake, it is a common use case that you would integrate a linter like clang-tidy or PCLint Plus, or some processing scripts directly into your cmake build as prebuild commands with add_custom_command or add_custom_target.
These tools generate warnings that are not in the format that CMake Tools expects, and thus dont show up in the "Problems" output.
Currently, the only solution to this is to create a VSCode task that invokes CMake, and then apply your problem matchers there.
This is inconvenient, because you can no longer run the build through the CMake Tools menus, and need to use your custom task.
It would be wonderful if CMake Tools exposed a setting that allowed us to add additional problem matchers to its internal tasks, such that we can aggregate all of the errors from all of our tools without needing to run the build from outside of CMake Tools.
CMake Tools Diagnostics
Debug Log
Additional Information
N/A
The text was updated successfully, but these errors were encountered: