-
-
Notifications
You must be signed in to change notification settings - Fork 9k
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
Update the Plugin Manager Updates View with more Info about incompatible dependencies and change CSS classes #4299
Update the Plugin Manager Updates View with more Info about incompatible dependencies and change CSS classes #4299
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! Just few minor comments
…lude a line brak at the end Co-Authored-By: Oleg Nenashev <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The new look is nice!
@@ -970,11 +970,25 @@ private static String getCategoryDisplayName(String category) { | |||
|
|||
public List<Plugin> getUpdates() { | |||
Map<String,Plugin> pluginMap = new LinkedHashMap<>(); | |||
Map<String, List<Plugin>> incompatiblePluginMap = new LinkedHashMap<>(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we would index this map with Plugin
instead of plugin name, we could avoid lookup in pluginMap
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you please explain this further to me?
If incompatiblePluginMap
would be indexed with Plugin
, how would I iterate through the pluginMap
later and add the incompatible plugins there?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good from the behavior/compatibility standpoint. I am not that concerned about performance for this page, but it definitely needs discussion with @zbynek to be finished before merging
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for checking the suggestions!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I find the new UI less aggressive and still more noticeable than the old one. Thanks!
thanks @andipabst ! I've added the ready for merge label. |
Thanks a lot for your contributions @andipabst ! It is much appreciated, and we invite you to keep contributing to the project. 👍 |
Thank you all for your help in this pull request. I would very much like to keep contributing! |
This is a hacktoberfest contribution.
Proposed changelog entries
Before:

After: