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

plugins: sort plugins in the plugins-view #7601

Merged
merged 1 commit into from
Apr 22, 2020
Merged

Conversation

vince-fugnitto
Copy link
Member

What it does

I generally use the plugins-view when debugging features to quickly determine which plugins are currently being consumed, however on master the list of plugins are unsorted making their discovery more difficult. I thought I'd do a quick-fix to correctly sort them for end-users.

The following commit adds a comparator method to the plugins-view so that plugins are sorted based on name, and publisher if required.

How to test

  1. open the plugins-view and determine if plugins are successfully sorted by name (if the name is equal, verify that they are sorted by publisher name).

Review checklist

Reminder for reviewers

Signed-off-by: vince-fugnitto vincent.fugnitto@ericsson.com

The following commit adds a comparator method to the `plugins-view`
so that plugins are sorted based on `name`, and `publisher` if required.

Signed-off-by: vince-fugnitto <vincent.fugnitto@ericsson.com>
@vince-fugnitto vince-fugnitto added plug-in system issues related to the plug-in system ui/ux issues related to user interface / user experience labels Apr 17, 2020
Copy link
Contributor

@lmcbout lmcbout left a comment

Choose a reason for hiding this comment

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

Tested on Ubuntu 18.04
I have some plugins like: vscode-maven, vscode-java-debug, vscode-java-dependency, built-in java and redhat-java
I notice the builtin and redhat java are group together, but all the one starting with vscode-[...] are together at the end. Would it be nice to have all related one (JAVA) for example to get set in the same area. Since some plugins add the "vscode-" to their name and some just use a name (without vscode-)
Should we sort the name and remove the "vscode-" before the sorting ?
By the way, it looks nice this way too, but I would like them to be grouped together

@vince-fugnitto
Copy link
Member Author

Should we sort the name and remove the "vscode-" before the sorting ?
By the way, it looks nice this way too, but I would like them to be grouped together.

I don't think we should hardcode values such as vscode- and remove it from the search.
We may have other java related extensions such as eclipse-java, and because of only removing vscode- they would not be grouped either way. I think the intuitive sort would just be alphabetical (since your suggestion would only work in a subset of cases).

@vince-fugnitto
Copy link
Member Author

@lmcbout any objections to merging?

@lmcbout
Copy link
Contributor

lmcbout commented Apr 20, 2020

@vince-fugnitto It is already approved.
One thing before merging, can we just discuss at the today team meeting if there would be any other suggestions about grouping the plugins together! If no suggestions, then I am fine with merging :)

@vince-fugnitto
Copy link
Member Author

One thing before merging, can we just discuss at the today team meeting if there would be any other suggestions about grouping the plugins together! If no suggestions, then I am fine with merging :)

As previously mentioned I don't think there is a way to generically apply additional sorting, but you can bring it up if its important to you.

@vince-fugnitto vince-fugnitto merged commit 181707e into master Apr 22, 2020
@vince-fugnitto vince-fugnitto deleted the vf/sorted-plugins branch April 22, 2020 13:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
plug-in system issues related to the plug-in system ui/ux issues related to user interface / user experience
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants