From: Dominik Csapak <d.csapak@proxmox.com>
To: Hannes Laimer <h.laimer@proxmox.com>, pbs-devel@lists.proxmox.com
Subject: Re: [PATCH proxmox-backup v5 1/9] ui: show empty groups
Date: Tue, 24 Mar 2026 11:28:05 +0100 [thread overview]
Message-ID: <2ef0f52f-af26-41f2-ab77-36beec3014ba@proxmox.com> (raw)
In-Reply-To: <20260319161325.206846-2-h.laimer@proxmox.com>
Hi,
high level comments:
the verify button is disabled for empty groups (good!) but the
prune button is not, better to disable that too
also the 'verify state' column shows 'all ok', while technically
not wrong, I think it would be better to don't render anything
at all there if the groups does not have any snapshots,
but this could be done as a follow up / extra patch.
one comment inline
On 3/19/26 5:12 PM, Hannes Laimer wrote:
[snip]
> @@ -232,6 +241,29 @@ Ext.define('PBS.DataStoreContent', {
>
> let groups = this.getRecordGroups(records);
>
> + for (const item of groupList) {
> + let btype = item['backup-type'];
> + let group = btype + '/' + item['backup-id'];
> + if (groups[group] !== undefined) {
> + continue;
> + }
> + let cls = PBS.Utils.get_type_icon_cls(btype);
> + if (cls === '') {
> + continue;
> + }
> + groups[group] = {
> + text: group,
> + leaf: true,
> + iconCls: 'fa ' + cls,
> + expanded: false,
> + backup_type: btype,
> + backup_id: item['backup-id'],
> + comment: item.comment,
> + owner: item.owner,
> + children: [],
> + };
> + }
> +
this hunk is more or less a 1:1 copy of 'getRecordGroups'
(minus the comment/owner column)
I think we should reuse that (maybe with a flag to set the comment/owner
when we know it's from the group, or factor out the inner part of the
loop and add the comment/owner manually after calling that)
> let selected;
> let expanded = {};
>
> @@ -399,7 +431,7 @@ Ext.define('PBS.DataStoreContent', {
> );
> }
>
> - this.updateGroupNotes(view);
> + this.updateGroupNotes(view, groupList);
>
> if (selected !== undefined) {
> let selection = view.getRootNode().findChildBy(
> @@ -985,7 +1017,7 @@ Ext.define('PBS.DataStoreContent', {
> flex: 1,
> renderer: (v, meta, record) => {
> let data = record.data;
> - if (!data || data.leaf || data.root) {
> + if (!data || (data.leaf && data.ty !== 'group') || data.root) {
> return '';
> }
>
> @@ -1029,7 +1061,7 @@ Ext.define('PBS.DataStoreContent', {
> },
> dblclick: function (tree, el, row, col, ev, rec) {
> let data = rec.data || {};
> - if (data.leaf || data.root) {
> + if ((data.leaf && data.ty !== 'group') || data.root) {
> return;
> }
> let view = tree.up();
next prev parent reply other threads:[~2026-03-24 10:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 16:13 [PATCH proxmox-backup v5 0/9] fixes #6195: add support for moving groups and namespaces Hannes Laimer
2026-03-19 16:13 ` [PATCH proxmox-backup v5 1/9] ui: show empty groups Hannes Laimer
2026-03-24 10:28 ` Dominik Csapak [this message]
2026-03-19 16:13 ` [PATCH proxmox-backup v5 2/9] datastore: add namespace-level locking Hannes Laimer
2026-03-24 13:00 ` Fabian Grünbichler
2026-03-19 16:13 ` [PATCH proxmox-backup v5 3/9] datastore: add move_group Hannes Laimer
2026-03-24 13:00 ` Fabian Grünbichler
2026-03-25 6:20 ` Hannes Laimer
2026-03-19 16:13 ` [PATCH proxmox-backup v5 4/9] datastore: add move_namespace Hannes Laimer
2026-03-24 13:00 ` Fabian Grünbichler
2026-03-25 6:32 ` Hannes Laimer
2026-03-25 8:55 ` Fabian Grünbichler
2026-03-19 16:13 ` [PATCH proxmox-backup v5 5/9] api: add PUT endpoint for move_group Hannes Laimer
2026-03-19 16:13 ` [PATCH proxmox-backup v5 6/9] api: add PUT endpoint for move_namespace Hannes Laimer
2026-03-19 16:13 ` [PATCH proxmox-backup v5 7/9] ui: add move group action Hannes Laimer
2026-03-24 10:41 ` Dominik Csapak
2026-03-19 16:13 ` [PATCH proxmox-backup v5 8/9] ui: add move namespace action Hannes Laimer
2026-03-24 10:56 ` Dominik Csapak
2026-03-19 16:13 ` [PATCH proxmox-backup v5 9/9] cli: add move-namespace and move-group commands Hannes Laimer
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=2ef0f52f-af26-41f2-ab77-36beec3014ba@proxmox.com \
--to=d.csapak@proxmox.com \
--cc=h.laimer@proxmox.com \
--cc=pbs-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