Syntax highlighting in the output of tests explorer #17411

Activity

1. Diogo (diogo-rossi)

   added

   triage-neededNeeds assignment to the proper sub-teamNeeds assignment to the proper sub-team

   feature-requestRequest for new features or functionalityRequest for new features or functionality

   on Sep 14, 2021
2. Karthik Nadig (karthiknadig)

   added

   area-testing

   good first issue

   needs PR

   and removed

   triage-neededNeeds assignment to the proper sub-teamNeeds assignment to the proper sub-team

   on Sep 14, 2021
3. pralkarz commented on Sep 14, 2021

   

   pralkarz

   on Sep 14, 2021

   More actions

   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?
4. pralkarz commented on Sep 17, 2021

   

   pralkarz

   on Sep 17, 2021

   More actions

   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.

   1. You can't select (and, consequently, copy) the code unless you open it in the editor via the button in the top-right, which might be a bit inconvenient.
   2. For some reason the code blocks don't get rendered as-is and the whitespace is squashed similarly to the regular HTML, so the code isn't indented properly.
      

   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?
5. pralkarz commented on Sep 26, 2021

   

   pralkarz

   on Sep 26, 2021

   More actions

   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.
6. diogo-rossi commented on Oct 8, 2021

   

   Diogo (diogo-rossi)

   on Oct 8, 2021

   Author

   More actions

   @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.
7. github-actions

   removed

   needs PR

   on Aug 9, 2022
8. Kartik Raj (karrtikr)

   added

   needs PRReady to be worked onReady to be worked on

   on Aug 9, 2022
9. pasumarty08 commented on Sep 16, 2022

   

   Venkata Pratyusha Pasumarty (pasumarty08)

   on Sep 16, 2022

   More actions

   Can I be assigned this issue please?
10. Luciana Abud (luabud)

    assigned

    Venkata Pratyusha Pasumarty (pasumarty08)

    on Sep 16, 2022
11. Luciana Abud (luabud)

    unassigned

    Venkata Pratyusha Pasumarty (pasumarty08)

    on Sep 8, 2023
12. Luciana Abud (luabud)

    removed

    good first issue

    on Sep 8, 2023
13. Eleanor Boyd (eleanorjboyd)

    self-assigned this

    on Dec 4, 2023