From: Dominik Csapak <d.csapak@proxmox.com>
To: Jonas Theisen <j.theisen@proxmox.com>, pve-devel@lists.proxmox.com
Subject: Re: [PATCH pve-manager] fix #5001: ui: add context menu with bulk actions for pools in resource tree
Date: Wed, 4 Nov 2026 12:19:50 +0100 [thread overview]
Message-ID: <d9d9b1ef-94b8-45c4-8138-e464981c9c06@proxmox.com> (raw)
In-Reply-To: <a64cd254-d2c5-4fd8-8381-663a4f250783@proxmox.com>
On 11/4/26 11:57 AM, Jonas Theisen wrote:
> On 11/3/26 14:37, Dominik Csapak wrote:
>> patch looks good to me, one high level thing and one
>> comment inline:
>>
>> if you send multiple patches, please number them, so it's easier to
>> apply the whole thread, e.g. with `b4 shazam`
>>
>> e.g. if you have both patches on the same branch,
>>
>> `git send-email` or `git format-patch` should do this for you
>
> I intentionally did not do that since i thought the two patches
> are only related by their targeted component but are not dependent
> on each other in any way.
> Will keep that in mind for v2.
that would also be ok, but then send them please as completely
independent patches, not within a single thread.
this makes it much clearer in most mail clients/tools that
they are separate
>>
>>
>>> <snip>
>>> +
>>> + me.title = `${gettext('Pool')} '${me.pool}'`;
>>> + if (PVE.ClusterName?.length) {
>>> + me.title += ` (${PVE.ClusterName})`;
>>> + }
>>> +
>>
>> i know this is copied from the other cmd menus here,
>> but does it really make sense?
>>
>> for the datacenter it makes (kinda) sense but for a pool
>> not really
>>
>> i'd just leave it out and use `Pool <name>` there
>
> Agreed and also applied that to the Tag menu in v2 as mentioned.
>>
>>> + me.extraHandlerArgs = {
>>> + prefilterPool: me.pool,
>>> + };
>>> +
>>> + me.callParent();
>>> + },
>>> +});
>>> diff --git a/www/manager6/window/BulkAction.js b/www/manager6/window/
>>> BulkAction.js
>>> index 2e3066a3..7e58fb3f 100644
>>> --- a/www/manager6/window/BulkAction.js
>>> +++ b/www/manager6/window/BulkAction.js
>>> @@ -557,6 +557,9 @@ Ext.define('PVE.window.BulkAction', {
>>> if (me.prefilterIncludeTag) {
>>> me.down('#includetagfilter').setValue(me.prefilterIncludeTag);
>>> }
>>> + if (me.prefilterPool) {
>>> + me.down('#poolfilter').setValue(me.prefilterPool);
>>> + }
>>> form.on('validitychange', function () {
>>> let valid = form.isValid();
>>
>
next prev parent reply other threads:[~2026-11-04 11:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 10:06 [PATCH pve-manager] fix #5001: ui: add context menu with bulk actions for pools in resource tree Jonas Theisen
2026-10-30 10:06 ` [PATCH pve-manager] ui: tag menu: show cluster name instead of undefined in title Jonas Theisen
2026-11-03 13:38 ` Dominik Csapak
2026-11-03 13:37 ` [PATCH pve-manager] fix #5001: ui: add context menu with bulk actions for pools in resource tree Dominik Csapak
2026-11-04 10:57 ` Jonas Theisen
2026-11-04 11:19 ` Dominik Csapak [this message]
2026-11-04 10:58 ` Jonas Theisen
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=d9d9b1ef-94b8-45c4-8138-e464981c9c06@proxmox.com \
--to=d.csapak@proxmox.com \
--cc=j.theisen@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