From: Dominik Csapak <d.csapak@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH manager 1/3] ui: resource tree: fix order of types
Date: Tue, 12 Nov 2024 12:45:04 +0100 [thread overview]
Message-ID: <20241112114506.1970103-1-d.csapak@proxmox.com> (raw)
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.csapak@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
next reply other threads:[~2024-11-12 11:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-12 11:45 Dominik Csapak [this message]
2024-11-12 11:45 ` [pve-devel] [PATCH manager 2/3] ui: view selector: prepare filterfn to be more efficient Dominik Csapak
2024-11-12 13:23 ` [pve-devel] applied: " Thomas Lamprecht
2024-11-12 11:45 ` [pve-devel] [PATCH manager 3/3] ui: resource tree: show nodes/storages in pool/tag view by default Dominik Csapak
2024-11-12 13:38 ` Thomas Lamprecht
2024-11-12 15:04 ` Dominik Csapak
2024-11-12 13:23 ` [pve-devel] applied: [PATCH manager 1/3] ui: resource tree: fix order of types Thomas Lamprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20241112114506.1970103-1-d.csapak@proxmox.com \
--to=d.csapak@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox