Open Diogo-Rossi opened 3 years ago
I assume the fix isn't too difficult (hence the good first issue
label), so would it be okay if I worked on this issue?
I worked on the issue and I managed to get syntax highlighting to work via VSCode's built-in Markdown engine, however there are two problems.
Sample code for a test message looks like this:
const markdownText = new MarkdownString().appendCodeblock(text, "python");
const message = new TestMessage(markdownText);
Now I tried using non-breaking spaces (
) and building the message manually without the MarkdownString.appendCodeblock
method, but none of that worked. Maybe there is an issue with the VSCode's Markdown renderer?
Kindly bump.
Please do tell me if this is rude. I'm still relatively new to open-source, so I'm not sure what's acceptable and what's not.
@ziebam Sorry for not to reply earlier. Sadly, I cant't help to develop extensions in VS Code. I just made the feature request. Maybe someone from the developers team could say something.
Can I be assigned this issue please?
Now that there will be a new announced built-in test tool for python, it will be good that some good details of an old test explorer extension become available, like the syntax highlighting in the output of failed test, as show bellow:
This is the floating output of the ""old"" Python Test Explorer for Visual Studio Code.
We can see syntax highlighting and monospace font.
Any output of the new tool does not show syntax highlighting:
Feature request
Show syntax highlighting in the output of failed tests in the new built-in tool of the tests.