From: Christian Ebner <c.ebner@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>,
Dominik Csapak <d.csapak@proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox-backup 0/6] sync job ui improvements
Date: Mon, 25 Nov 2024 12:30:15 +0100 [thread overview]
Message-ID: <377618fd-0ea9-46ba-9aec-a47387eca50d@proxmox.com> (raw)
In-Reply-To: <20241125111537.1504618-1-d.csapak@proxmox.com>
On 11/25/24 12:15, Dominik Csapak wrote:
> this series aims to improve the pull/push sync job ui a bit, by:
>
> * unifying both types into one list
Not sure if you are aware of this, but we decided early on [0] to
explicitly separate the list for both directions to reduce possible
misconfiguration for the user. That is also why the sync jobs in push
direction have their dedicated config type instead of having the
direction as property of the sync job.
[0]
https://lore.proxmox.com/pbs-devel/5be4c3d1-593f-4eec-b21b-33cb3afc9216@proxmox.com/
> * adding a helpful tooltip for local owner/user
> * adding a filter for the sync jobs
> * adding a 'all' mode for listing all jobs on the /admin/sync api
>
> Dominik Csapak (6):
> api: admin: sync: add direction to sync job status
> api: admin: sync: add optional 'all' sync type for listing
> cli: manager: sync: add 'sync-direction' parameter to list
> ui: sync jobs: revert to single list for pull/push jobs
> ui: sync jobs: change default sorting to 'store' -> 'direction' ->
> 'id'
> ui: sync jobs: add search box
>
> pbs-api-types/src/jobs.rs | 6 ++
> src/api2/admin/sync.rs | 65 ++++++++----
> src/api2/config/datastore.rs | 9 +-
> src/api2/config/notifications/mod.rs | 2 +-
> src/bin/proxmox_backup_manager/sync.rs | 6 +-
> www/Makefile | 1 -
> www/config/SyncPullPushView.js | 61 -----------
> www/config/SyncView.js | 134 ++++++++++++++++++++-----
> www/datastore/DataStoreList.js | 2 +-
> www/datastore/Panel.js | 2 +-
> 10 files changed, 178 insertions(+), 110 deletions(-)
> delete mode 100644 www/config/SyncPullPushView.js
>
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
next prev parent reply other threads:[~2024-11-25 11:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-25 11:15 Dominik Csapak
2024-11-25 11:15 ` [pbs-devel] [PATCH proxmox-backup 1/6] api: admin: sync: add direction to sync job status Dominik Csapak
2024-11-25 11:15 ` [pbs-devel] [PATCH proxmox-backup 2/6] api: admin: sync: add optional 'all' sync type for listing Dominik Csapak
2024-11-25 11:15 ` [pbs-devel] [PATCH proxmox-backup 3/6] cli: manager: sync: add 'sync-direction' parameter to list Dominik Csapak
2024-11-25 11:15 ` [pbs-devel] [PATCH proxmox-backup 4/6] ui: sync jobs: revert to single list for pull/push jobs Dominik Csapak
2024-11-25 11:15 ` [pbs-devel] [PATCH proxmox-backup 5/6] ui: sync jobs: change default sorting to 'store' -> 'direction' -> 'id' Dominik Csapak
2024-11-25 11:15 ` [pbs-devel] [PATCH proxmox-backup 6/6] ui: sync jobs: add search box Dominik Csapak
2024-11-25 11:30 ` Christian Ebner [this message]
2024-11-26 15:03 ` [pbs-devel] applied-series: [PATCH proxmox-backup 0/6] sync job ui improvements 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=377618fd-0ea9-46ba-9aec-a47387eca50d@proxmox.com \
--to=c.ebner@proxmox.com \
--cc=d.csapak@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