when ordering items on the same level, we often sort first by type, but
do this via string comparison of the types.
this leads to weird results if we have e.g. lxc/node/qemu mixed in one
list, as nodes would sort in between lxc and qemu
this patch solves that issue by introducing a fixed order for types, so
we have direct control over the order when mixing types without having
to change the type names.
Signed-off-by: Dominik Csapak <d.csa...@proxmox.com>
---
www/manager6/tree/ResourceTree.js | 19 +++++++++++++++----
1 file changed, 15 insertions(+), 4 deletions(-)
diff --git a/www/manager6/tree/ResourceTree.js
b/www/manager6/tree/ResourceTree.js
index 7b0c5dc8..640ebbf9 100644
--- a/www/manager6/tree/ResourceTree.js
+++ b/www/manager6/tree/ResourceTree.js
@@ -45,6 +45,18 @@ Ext.define('PVE.tree.ResourceTree', {
useArrows: true,
+ // private
+ getTypeOrder: function(type) {
+ switch (type) {
+ case 'lxc': return 0;
+ case 'qemu': return 1;
+ case 'node': return 2;
+ case 'sdn': return 3;
+ case 'storage': return 4;
+ default: return 9;
+ }
+ },
+
// private
nodeSortFn: function(node1, node2) {
let me = this;
@@ -55,10 +67,9 @@ Ext.define('PVE.tree.ResourceTree', {
let n2IsGuest = n2.type === 'qemu' || n2.type === 'lxc';
if (me['group-guest-types'] || !n1IsGuest || !n2IsGuest) {
// first sort (group) by type
- if (n1.type > n2.type) {
- return 1;
- } else if (n1.type < n2.type) {
- return -1;
+ let res = me.getTypeOrder(n1.type) - me.getTypeOrder(n2.type);
+ if (res !== 0) {
+ return res;
}
}
--
2.39.5
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
