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
Is your feature request related to a problem? Please describe
In the "Networks" tab, when sorting by IPv4 (both IPV4 IPAM Subnet and IPV4 IPAM Gateway), the sort order is using a standard string sort instead of taking into account the logic of IP numbering.
Currently, an ascending sort on IPV4 IPAM Subnet is outputting:
172.20.1.0/24
172.20.10.0/24
172.20.11.0/24
172.20.2.0/24
172.20.3.0/24
I have not checked sort behavior for IPV6.
Describe the solution you'd like
I would rather have a sort behavior that is respecting IP numbering structure:
172.20.1.0/24
172.20.2.0/24
172.20.3.0/24
172.20.10.0/24
172.20.11.0/24
This sort logic is the one being used right now in the "Containers" table, "IP Address" field.
Describe alternatives you've considered
It remains a minor annoyance, so I accept it as it is.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Is your feature request related to a problem? Please describe
In the "Networks" tab, when sorting by IPv4 (both IPV4 IPAM Subnet and IPV4 IPAM Gateway), the sort order is using a standard string sort instead of taking into account the logic of IP numbering.
Currently, an ascending sort on IPV4 IPAM Subnet is outputting:
I have not checked sort behavior for IPV6.
Describe the solution you'd like
I would rather have a sort behavior that is respecting IP numbering structure:
This sort logic is the one being used right now in the "Containers" table, "IP Address" field.
Describe alternatives you've considered
It remains a minor annoyance, so I accept it as it is.
Additional context
Portainer Business edition 2.19.5
Beta Was this translation helpful? Give feedback.
All reactions