From: Dominik Csapak <d.csapak@proxmox.com>
To: Erik Fastermann <e.fastermann@proxmox.com>, pbs-devel@lists.proxmox.com
Subject: Re: [PATCH proxmox-backup v2 2/5] ui: datastore: fix content search empty list
Date: Wed, 6 May 2026 17:10:57 +0200 [thread overview]
Message-ID: <070bb10d-8991-4562-9752-e9fd45f700ac@proxmox.com> (raw)
In-Reply-To: <20260506121332.21896-3-e.fastermann@proxmox.com>
two things here:
in general it would be good that the commit message explains why
the code does something (done here) but also explain any
non-obvious relation to the code (i.e. how does the change
have this effect)
i say this because to me it's not super obvious how this change
can have this effect. I looked at the surrounding code a bit
and IMO this part should not even be called when one clears
the search (since we should return early in that case before
the setTimeout)
so i think the real fix is probably something else and the
fact that this change fixes it for you is probably just a
side effect...
On 5/6/26 2:11 PM, Erik Fastermann wrote:
> Display items again when searching by a non existing value and
> clearing the search bar.
>
> Signed-off-by: Erik Fastermann <e.fastermann@proxmox.com>
> ---
> www/datastore/Content.js | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/www/datastore/Content.js b/www/datastore/Content.js
> index e963d62f9..54e93bd3c 100644
> --- a/www/datastore/Content.js
> +++ b/www/datastore/Content.js
> @@ -961,7 +961,6 @@ Ext.define('PBS.DataStoreContent', {
> // we do it a little bit later for the error mask to work
> setTimeout(function () {
> store.clearFilter();
> - store.getRoot().collapseChildren(true);
>
> store.beginUpdate();
> store.getRoot().cascadeBy({
next prev parent reply other threads:[~2026-05-06 15:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 12:13 [PATCH proxmox-backup v2 0/5] fix #6691: allow search by comment in datastore content Erik Fastermann
2026-05-06 12:13 ` [PATCH proxmox-backup v2 1/5] " Erik Fastermann
2026-05-06 14:08 ` Shan Shaji
2026-05-06 15:06 ` Dominik Csapak
2026-05-06 12:13 ` [PATCH proxmox-backup v2 2/5] ui: datastore: fix content search empty list Erik Fastermann
2026-05-06 15:10 ` Dominik Csapak [this message]
2026-05-06 12:13 ` [PATCH proxmox-backup v2 3/5] ui: datastore: update code formatting with biome Erik Fastermann
2026-05-06 15:11 ` Dominik Csapak
2026-05-06 12:13 ` [PATCH proxmox-backup v2 4/5] ui: datastore: disable remove action for namespaces Erik Fastermann
2026-05-06 15:13 ` Dominik Csapak
2026-05-06 12:13 ` [PATCH proxmox-backup v2 5/5] ui: datastore: disable browse action for root ns Erik Fastermann
2026-05-06 15:13 ` Dominik Csapak
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=070bb10d-8991-4562-9752-e9fd45f700ac@proxmox.com \
--to=d.csapak@proxmox.com \
--cc=e.fastermann@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