chore: fix truncated build issues in vscode #99
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fixed an issue with build issue filenames and messages being truncated in VS Code by passing the /consoleloggerparameters:ForceNoAlign option to dotnet build.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In VSCode (on Windows 11, with .NET 8), build issues are displayed in the "Problems" tab with truncated filenames and messages:
In addition, clicking the issue attempts to open the displayed (incorrect) filename:
The issue appears to be that VSCode's problem matcher can't handle line wrapping in the terminal output of the build task (see this C# extension issue and this VSCode issue):
This PR modifies the build task to pass the
/consoleloggerparameters:ForceNoAlignoption to dotnet build, recommended as a workaround in the above issues. This option prevents the terminal output from wrapping, and causes build issues to appear as expected: