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 UI problems #344

Closed
7 of 8 tasks
sbs2001 opened this issue Feb 10, 2021 · 2 comments
Closed
7 of 8 tasks

FIx UI problems #344

sbs2001 opened this issue Feb 10, 2021 · 2 comments

Comments

@sbs2001
Copy link
Collaborator

sbs2001 commented Feb 10, 2021

Changes:-

  • 1. Make Packages -> Package . The columns should have singular name.
  • 2. Eliminate whitespace from search result view.
  • 3. Don't forget what user searched for.
  • 4. Correct sequencing in package search view. expectec -> Vulnerabilities| Patched Vulnerabilities
  • 5. Unrelated to UI : Forget fixes, remember vulnerable packages only, while keeping track of first fix.
  • 6. Have setting, to enable/disable curation. Set it to disabled by default.
  • 7. Add qualifiers, subpath in package view. Increase info density for package detail view. #535
  • 8. Rename Package Details -> Packageurl
@sbs2001 sbs2001 mentioned this issue Mar 11, 2021
@sbs2001
Copy link
Collaborator Author

sbs2001 commented Mar 12, 2021

In the vulnerability view, for displaying vulnerable packages we need to avoid using discrete versions. Instead a expandable version range would be better, that will increase information density.

Here's a repaste from gitter chat on how to create version ranges from discrete version ranges

For eg. Given a list of versions like [1.1.2, 1.1.3, 1.2.3, 1.2.4, 2.5.6]
We can convert it into version ranges having a lowest common denominator of either the MAJOR, MINOR . In this case let it be the MINOR part.
Then we split the version list into smaller lists, each of the list having same lowest common denominator and parts greater than it.
[1.1.2, 1.1.3, 1.2.3, 1.2.4, 2.5.6] -> [1.1.2, 1.1.3,], [1.2.3, 1.2.4], [2.5.6]
Now each of this smaller list can be coverted into version ranges of the format
<=max(version_list) , >=min(version_list)
In this case that will be <=1.1.3, >=1.1.2 etc

@pombredanne
Copy link
Collaborator

See #535 for a follow up. I am closing this for now otherwise.

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

No branches or pull requests

2 participants