Skip to content
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

Latest Java test runner extension fails in displaying tree icons #8981

Closed
sunix opened this issue Jan 22, 2021 · 8 comments
Closed

Latest Java test runner extension fails in displaying tree icons #8981

sunix opened this issue Jan 22, 2021 · 8 comments
Labels
monaco issues related to monaco vscode issues related to VSCode compatibility

Comments

@sunix
Copy link
Contributor

sunix commented Jan 22, 2021

Bug Description:

Hello, I tried the latest Java test runner extension and there is a regression in Theia in the tree:

  • The green passed icon is not displayed
  • The red failed icon is not red

Maybe caused by microsoft/vscode-java-test#1099
Related to #8267

CAN NOT reproduce with Java test runner 0.24.2
CAN reproduce with Java test runner 0.27.0

Steps to Reproduce:

With Che:

  1. Start any Java workspace from Che.
  2. Edit the devfile and add the custom registry url for the quarkus or java plugin for instance:
     - id: redhat/quarkus-java11/latest
       type: chePlugin
       registryUrl: 'https://sunix-che-plugin-registry-java-test-runner-0-27-0.surge.sh/v3'
  3. Start the workspace and run the test

With Gitpod:

  1. Start the petclinic sample
  2. install the Java test runner extension
  3. Run the test

Selection_170

Same one in vscode:
Selection_171

@vince-fugnitto
Copy link
Member

vince-fugnitto commented Jan 22, 2021

@sunix I believe it is the same issue as #8905 (comment), they are new codicons which are supported in the newer version of monaco. An update of monaco is most likely required: #8969.

Update: I verified that the pass icon is not in our codicons file from @theia/monaco-editor-core.

@vince-fugnitto vince-fugnitto added monaco issues related to monaco vscode issues related to VSCode compatibility labels Jan 22, 2021
@sunix
Copy link
Contributor Author

sunix commented Jan 22, 2021

@vince-fugnitto yep maybe let's see how the new monaco updates goes

@vince-fugnitto
Copy link
Member

@vince-fugnitto yep maybe let's see how the new monaco updates goes

I was hoping we could directly consume vscode-codicons as an icon font, rather than have to rely on a monaco upgrade (which requires significantly more effort): #6115 (comment). Perhaps it is something we can consider for the future (https://github.com/microsoft/vscode-codicons) and will allow us to update icons more easily.

@TomHermanSAP
Copy link

Hi @vince-fugnitto @sunix,
Several points:

  1. Is there a planned schedule regarding updating monaco and vscode-icons? (when and how long would it take)
    Here are some related issues I found:
    Update VSCode Icons #6115: Update VSCode Icons (Open since Sep. 2019)
    Icons are missing in Java Projects Panel #8905: Missing "Export" icon in "Project Manager for Java" extension

  2. Is there a way I can help with the process of updating them?

Thank you!

@vince-fugnitto
Copy link
Member

  1. Is there a planned schedule regarding updating monaco and vscode-icons? (when and how long would it take)
    Here are some related issues I found:
    Update VSCode Icons #6115: Update VSCode Icons (Open since Sep. 2019)
    Icons are missing in Java Projects Panel #8905: Missing "Export" icon in "Project Manager for Java" extension

@TomHermanSAP are you looking into replacing the icons present in the application to those of codicons? If so then you can update the existing icons to codicons using the codicon syntax. Codicons are contributed through the monaco-editor dependency. For plugins there should not be anything to do to make use of the icons, only that certain icons are present in newer versions of monaco which require an update (like java).

  1. Is there a way I can help with the process of updating them?

You can provide a pull-request to update icons if you like. We can essentially continue the work of #6993 but there is no need to copy icons into our sources, we have them already available.

@TomHermanSAP
Copy link

TomHermanSAP commented Feb 28, 2021

@vince-fugnitto To be honest I do not know and could not understand which and where icons from monaco and from vscode-icons are used, and I am not planning on changing any icons in any plugins / extensions.

Based on your answer, I understand that once #8969 will be merged the missing icons described in #8981 & #8905 will be seen.

Then, I will wait for #8969 to be merged.

Thank you again.

@vince-fugnitto
Copy link
Member

The following should be fixed if someone wants to test it out 👍

@vince-fugnitto
Copy link
Member

@sunix still an issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
monaco issues related to monaco vscode issues related to VSCode compatibility
Projects
None yet
Development

No branches or pull requests

3 participants