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
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:
["duration", "=", "7", "ms"]
["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
The text was updated successfully, but these errors were encountered:
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:
["duration", "=", "7", "ms"]
["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
The text was updated successfully, but these errors were encountered: