Display compiler warnings and build messages in the IDE Build Output instead of the test output panel

[tanmaythegreat]

I have a small feature request that I believe would improve the user experience.
When running a solution, compiler diagnostics (such as warnings and compilation errors) are displayed inside the plugin's output/test results panel.
This makes it harder to inspect compiler messages, especially when there are multiple warnings or when navigating between diagnostics.

Proposed Improvement

It would be very helpful if compiler output (warnings, errors, and other build messages) were forwarded to the IDE's Build Output tool window instead of (or in addition to) the plugin's output panel.

This would provide several benefits:
The Build Output window is designed for compiler diagnostics and offers better readability.
IDE features such as navigating to the corresponding source location would continue to work naturally.
The plugin's output panel could remain focused on test case execution and program output, making both views easier to use.

[dj258255]

Picking this up now — the testing-features PR (#37) is merged, and as suggested over in #36, this comes next before the debugging PR.

Plan: forward compiler diagnostics (errors/warnings) to the IDE's Build Output tool window with clickable source locations, in addition to the test panel — so the panel stays focused on test execution and program output. One note on scope: the plugin compiles into a temp directory, so diagnostics need mapping back to your real source file. stdin-style runs (Codeforces/SWEA) map 1:1 and will be clickable right away; wrapper-style runs (LeetCode/Programmers) will show in the Build window too, with click-through landing once the wrappers become line-preserving (that refactor ships with the debugging PR).

I'll update here as it lands.

[dj258255]

This is included in the v1.7.0 update, now available on the marketplace. Compiler warnings and errors now show up in the IDE's Build Output window with clickable file locations, instead of being mixed into the test output panel.

Could you give it a try and let me know if this works the way you expected? I'll close this once confirmed.