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

Improve attributes sorting in the resources tab #496

Open
mbiggio opened this issue Nov 29, 2023 · 0 comments
Open

Improve attributes sorting in the resources tab #496

mbiggio opened this issue Nov 29, 2023 · 0 comments
Labels
S-feature Severity: feature. This is adding a new feature.

Comments

@mbiggio
Copy link
Contributor

mbiggio commented Nov 29, 2023

What problem are you trying to solve?

Currently, attributes in the resources tab are just sorted according to the first attribute key, and attributes with the same key are ordered arbitrarily. So, attributes like ["duration", "=", "1001", "ms"] and ["duration", "=", "7", "ms"] would be ordered arbitrarily in the attributes column.

Moreover, a resource might actually have multiple attributes - currently only the first attribute is considered for sorting.

How should the problem be solved?

It would be nice to sort the attributes taking into account their semantics. For example, the two attributes above should probably be sorted in ascending order as:

  1. ["duration", "=", "7", "ms"]
  2. ["duration", "=", "1001", "ms"]

that is, with the attribute values sorted numerically instead of lexicographically. Other attributes whose value is truly a string might require lexicographical sorting instead.

Any alternatives you've considered?

No

How would users interact with this feature?

No response

Would you like to work on this feature?

maybe

@mbiggio mbiggio added the S-feature Severity: feature. This is adding a new feature. label Nov 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-feature Severity: feature. This is adding a new feature.
Projects
None yet
Development

No branches or pull requests

1 participant