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

feat(plugin): Use product applicationName to return the value to plugins env.appName #7642

Merged
merged 1 commit into from
Apr 23, 2020

Conversation

benoitf
Copy link
Contributor

@benoitf benoitf commented Apr 21, 2020

What it does

Use product applicationName to return the value to plugins env.appName
Thus branding is applied everywhere.

How to test

Clone a java project and takes a plug-in using the appName like Red Hat vscode-java
https://github.com/redhat-developer/vscode-java/releases/download/v0.55.1/redhat.java-0.55.1.vsix

Starts the examples/browser and notice the new name
image

Now, remove theia element of examples/browser/package.json

"theia": {
    "frontend": {
      "config": {
        "applicationName": "Theia Browser Example",
        "preferences": {
          "files.enableTrash": false
        }
      }
    }
  },

and check default Theia value is used (which is also the name seen in about/dialog)
image

Review checklist

Reminder for reviewers

Change-Id: Ifdda9b5cd64ea34de8292bd16703b87d81700c39
Signed-off-by: Florent Benoit fbenoit@redhat.com

…ins env.appName.

Thus branding is applied everywhere.

Change-Id: Ifdda9b5cd64ea34de8292bd16703b87d81700c39
Signed-off-by: Florent Benoit <fbenoit@redhat.com>
Copy link
Member

@vince-fugnitto vince-fugnitto left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The changes look good to me and it's much better now that it picks up the appName.
I tested when a name is provided and when it is not (default name):

Screen Shot 2020-04-21 at 3 21 55 PM Screen Shot 2020-04-21 at 3 24 09 PM

@vince-fugnitto vince-fugnitto added vscode issues related to VSCode compatibility enhancement issues that are enhancements to current functionality - nice to haves labels Apr 21, 2020
@benoitf
Copy link
Contributor Author

benoitf commented Apr 22, 2020

thanks @vince-fugnitto

I will merge tomorrow to allow others to add their review.

@akosyakov
Copy link
Member

Should we update here:

to Eclipse Theia?

Copy link
Member

@akosyakov akosyakov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@benoitf
Copy link
Contributor Author

benoitf commented Apr 22, 2020

Should we update here:

to Eclipse Theia?

@akosyakov we could yes, maybe in a different PR ?

@akosyakov
Copy link
Member

@benoitf sounds good

@benoitf
Copy link
Contributor Author

benoitf commented Apr 23, 2020

merging this one and I've opened #7656 as per comments.

@benoitf benoitf merged commit 66dd2bc into eclipse-theia:master Apr 23, 2020
@benoitf benoitf deleted the branding-plugin branch April 23, 2020 07:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement issues that are enhancements to current functionality - nice to haves vscode issues related to VSCode compatibility
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants