There are a couple places that I know of in the UI where it would be nice if node interfaces were sorted by ifIndex. It's a minor issue, but we do get a fair number of user complaints about this.
What I mean is where something like 'ethernet1/123' comes before 'ethernet1/2'.
The two places are 'Choose | Resource Graphs' page, and the 'Node Interfaces' table on each node's home page.
One possible solution would be to look for a pattern /[0-9]+ or /[0-9]+/ and if the characters after the / or between the /'s were purely numeric, sort them by numeric order and not ascii order.
Acceptance / Success Criteria
None
Lucidchart Diagrams
Activity
Show:
Seth Leger June 29, 2016 at 11:49 AM
It sounds like we need a regex check to see if the string conforms to a particular pattern and then we could apply a different comparator to the strings.
If anyone has any more ideas of places to apply this and examples of strings that need to be ordered, please append them to this issue.
Minor
There are a couple places that I know of in the UI where it would be nice if node interfaces were sorted by ifIndex. It's a minor issue, but we do get a fair number of user complaints about this.
What I mean is where something like 'ethernet1/123' comes before 'ethernet1/2'.
The two places are 'Choose | Resource Graphs' page, and the 'Node Interfaces' table on each node's home page.
One possible solution would be to look for a pattern /[0-9]+ or /[0-9]+/ and if the characters after the / or between the /'s were purely numeric, sort them by numeric order and not ascii order.