public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Stefan Hanreich <s.hanreich@proxmox.com>
Subject: [pve-devel] applied: [PATCH pve-manager] fix #4393: ui: storage backup view: make pbs-specific columns sortable
Date: Mon, 16 Jan 2023 14:26:17 +0100	[thread overview]
Message-ID: <6004a5af-8619-26a7-bc0a-2b8e12483691@proxmox.com> (raw)
In-Reply-To: <20221216124506.316371-1-s.hanreich@proxmox.com>

Am 16/12/2022 um 13:45 schrieb Stefan Hanreich:
> The sort order is analogous to how it behaves in the datastore content
> overview in pbs.
> 
> This means sorting in ascending order behaves as follows:
> 
> Verify State
> * failed
> * none
> * ok
> 
> Encryption
> * no
> * yes
> 
> For the encryption state there is theoretically a distinction between
> signed and encrypted, but as far as I can tell we do not render this
> distinction in PVE, which is why I chose to not make this distinction
> for sorting as well.
> 
> Signed-off-by: Stefan Hanreich <s.hanreich@proxmox.com>
> ---
>  www/manager6/Utils.js              |  7 +++++++
>  www/manager6/storage/BackupView.js | 12 ++++++++++++
>  2 files changed, 19 insertions(+)
> 
> diff --git a/www/manager6/Utils.js b/www/manager6/Utils.js
> index 8c118fa2..3dd287e3 100644
> --- a/www/manager6/Utils.js
> +++ b/www/manager6/Utils.js
> @@ -1963,6 +1963,13 @@ Ext.define('PVE.Utils', {
>      },
>  
>      tagCharRegex: /^[a-z0-9+_.-]+$/i,
> +
> +    verificationStateOrder: {
> +	'failed': 0,
> +	'none': 1,
> +	'ok': 2,
> +	'__default__': 3,
> +    },

Not that your patch is really at fault here, but made me notice again that we really
need to make Utils go away, it's a real dump for so much stuff that it's just
becoming gross..

It should be split up and stuff moved either directly where its actually used,
to specialized classes, even if on the smaller side, or to more generic but
sensible "aggregative" classes like one for Schema stuff (but not utils, helper,
tools anymore).

>  },
>  
>      singleton: true,
>

applied, thanks!




      reply	other threads:[~2023-01-16 13:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-16 12:45 [pve-devel] " Stefan Hanreich
2023-01-16 13:26 ` Thomas Lamprecht [this message]

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=6004a5af-8619-26a7-bc0a-2b8e12483691@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=s.hanreich@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal