[XC] Fix LogWarningOrError #22454
Merged
[XC] Fix LogWarningOrError #22454
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
|
this hopefully will report errors correctly in VSCode |
StephaneDelcroix
previously approved these changes
May 16, 2024
|
@StephaneDelcroix I noticed we're also not passing the |
simonrozsival
changed the title
StephaneDelcroix
approved these changes
May 17, 2024
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.
Description of Change
This will make sure we adhere to the correct format of warnings and errors in the MSBuild output (https://learn.microsoft.com/en-us/visualstudio/msbuild/msbuild-diagnostic-format-for-tasks?view=vs-2022)
There was also a problem with errors: when we logged error through
LogWarningOrError, the MSBuild task would still succeed, because the error wasn't added to the list of throw exceptions. This PR fixes this problem as well./cc @StephaneDelcroix