Fix vs code global output coloring+links detection conflicts #1092
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
…1.66 (to fix ts errors)
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.
It fixes the conflicts generated by the extension in the output window (broken coloring and clickable link detection), also it allows to use output coloring extensions such as https://marketplace.visualstudio.com/items?itemName=IBM.output-colorizer and https://marketplace.visualstudio.com/items?itemName=SteveBushResearch.BuildOutputColorizer.
I updated the minimum vs code version to v1.66 and typescript to v4 to fix compiling errors due to the new vsc API used.