Consider SARIF support for tool output -> MSBuild logs
- Dominant language
- C#
- Stars
- 5.5k
- Forks
- 1.5k
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 139
Description
The Microsoft C++ team is [considering](https://devblogs.microsoft.com/cppblog/the-future-of-c-compiler-diagnostics-in-msvc-and-visual-studio/) adding [SARIF](https://github.com/microsoft/sarif-tutorials/blob/main/docs/1-Introduction.md) support to the MSVC toolchain. That allows capturing much more information about errors/warnings than we currently support, through the [canonical error format](https://learn.microsoft.com/visualstudio/msbuild/msbuild-diagnostic-format-for-tasks).
MSBuild should consider extending the tool-output-scraping support to include SARIF output, and map the SARIF format to our error/warning structured events.
This might also help with issues like #8019 that primarily arise because an error cannot today have supplemental information.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.