You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
V1 parity work is being done. I'd like us to agree on which columns the UI will be able to sort and how. If possible be able to sort by all columns the table has. Otherwise, make conscious decisions about why not.
V1 does not have a single column Sort. We didn't do Sorting in v1, I believe due to a design that limited us to do such thing but those limitations are solved now I think right?.
Sort by Name: Which is the REST query to achieve it?
Sort by Version: Which is the REST query to achieve it?
Sort by Type: Which is the REST query to achieve it?
Sort by Vulnerabilities: this column will render the total the count of vulnerabilities affecting the package. This might need a deeper discussion (we there are multiple advisories for the same package) but a brainstorm would be welcome.
Sort by SBOMs: this column will render the total count of SBOMs that contain the package. I believe we can not do that at the moment, then let's decide whether or not we are able to do it.
The text was updated successfully, but these errors were encountered:
V1 parity work is being done. I'd like us to agree on which columns the UI will be able to sort and how. If possible be able to sort by all columns the table has. Otherwise, make conscious decisions about why not.
V1 does not have a single column Sort. We didn't do Sorting in v1, I believe due to a design that limited us to do such thing but those limitations are solved now I think right?.
The text was updated successfully, but these errors were encountered: