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

[FIX] Sorting add-ons in the alphabetical order #3013

Merged
merged 1 commit into from
May 11, 2018

Conversation

PrimozGodec
Copy link
Contributor

@PrimozGodec PrimozGodec commented Apr 20, 2018

Issue

Add-ons are in unpredictable order #3007

Description of changes

Sorting add-ons in the alphabetical order

Includes
  • Code changes
  • Tests
  • Documentation

@codecov-io
Copy link

codecov-io commented Apr 20, 2018

Codecov Report

Merging #3013 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #3013   +/-   ##
=======================================
  Coverage   82.12%   82.12%           
=======================================
  Files         334      334           
  Lines       57663    57663           
=======================================
  Hits        47354    47354           
  Misses      10309    10309

@@ -300,6 +300,7 @@ def set_items(self, items):

model.appendRow([item1, item2, item3, item4])

model.sort(1) # sorting list of add-ons in the alphabetical order
Copy link
Member

Choose a reason for hiding this comment

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

It does not work correctly. Have you tested if then the correct add-ons are also installed? If I added "pip" to the list and tried to upgrade it, it upgraded the wrong package.

Copy link
Contributor

Choose a reason for hiding this comment

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

@PrimozGodec Try self.__proxy.sort(1)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thank you @markotoplak and @ales-erjavec. I think that now it works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants