Implement Descending Sorting for Packages and Vulnerabilities in API and UI#1758
Implement Descending Sorting for Packages and Vulnerabilities in API and UI#1758NucleonGodX wants to merge 4 commits intoaboutcode-org:mainfrom
Conversation
9374f7e to
801ea0f
Compare
Signed-off-by: NucleonGodX <racerpro41@gmail.com>
801ea0f to
e0dec3c
Compare
|
Thanks! do you mind to add some tests? In particular we need to make sure that this does not impact performance badly so the perf there at scale need to be in a test. |
Signed-off-by: NucleonGodX <racerpro41@gmail.com>
0fadb20 to
c52d92a
Compare
Signed-off-by: NucleonGodX <racerpro41@gmail.com>
Hey @pombredanne, How can we perform those tests? |
|
Hey @NucleonGodX , I think @pombredanne wants you to add "Unit Test" for your changes. To make those unit tests you need to make a new test file at vulnerabilities/tests for your specific test for example as said above "to make sure that this does not impact performance badly". |
|
@NucleonGodX a gentle reminder, is this PR active ? |
|
Hi @TG1999, actually when I opened this PR, I discussed this with @keshav-space in the weekly meet regarding the performance test cases, and he informed me that they aren't necessarily required, so I didn't add anything else in this PR. |
#1754


Used aliases to sort vulnerabilities in descending order and implemented version-based sorting for packages in both the API and UI.