-
Notifications
You must be signed in to change notification settings - Fork 269
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] Log Viewer Extension Conflict #1868
Comments
Hey @myagizmaktav , thanks for reaching us, you can try on nightly preview version and let me know if you still can see this issue. We have logic to highlight some specific keywords in output log, but have some incompatibility issues to other extensions. |
@EzioLi01 Same problem still continues. |
@myagizmaktav As far as I know, vscode not support config highlight for specific log channel, so it might overwrite or conflict with any 2 colorize extension, I will disable our colorize feature since we need to fix some other issues. |
emilast.LogFileHighlighter extension Then I disabled and open IBM.output-colorizer and I disabled all extensions and try again @EzioLi01 might be you are not close to this feature I think. |
Hey @myagizmaktav , this is the latest version for nightly preview. Now RNT should not have any logic to change output log, it should not overwrite or conflict other extension highlight. Could you please try this again rather than prod version(maybe you can delete RNT extension folder in |
Fixed @EzioLi01 Thanks. |
🐛 What is the bug? How can we reproduce it?
View problem this extension is conflict with
emilast.LogFileHighlighter extension
Please put here any steps, code or any information that can help us
reproduce the error on our side so we can fix it:
Expected behavior
Do not conflict with this extension.
The text was updated successfully, but these errors were encountered: