From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Christian Ebner <c.ebner@proxmox.com>
Subject: [pve-devel] applied: [PATCH widget-toolkit 2/3] DateTimeField: Extend and refactor to make field value bindable
Date: Tue, 6 Jun 2023 16:47:14 +0200 [thread overview]
Message-ID: <a915700a-f34e-7017-ce86-aebd217d3230@proxmox.com> (raw)
In-Reply-To: <20230323144205.1774772-3-c.ebner@proxmox.com>
Am 23/03/2023 um 15:42 schrieb Christian Ebner:
> Extends the date time field so that bindings are updated on value changes.
> Also adds a config to disable child components and avoid modification of
> current values by cloning the referenced object for min/max value calculation.
>
> Signed-off-by: Christian Ebner <c.ebner@proxmox.com>
> ---
> src/form/DateTimeField.js | 105 +++++++++++++++++++++++++++++---------
> 1 file changed, 81 insertions(+), 24 deletions(-)
>
>
applied, thanks!
next prev parent reply other threads:[~2023-06-06 14:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 14:42 [pve-devel] [PATCH 0/5] fix #4442: Firewall log filtering Christian Ebner
2023-03-23 14:42 ` [pve-devel] [PATCH widget-toolkit 1/3] DateTimeField: fix typo in xtype Christian Ebner
2023-06-06 14:47 ` [pve-devel] applied: " Thomas Lamprecht
2023-03-23 14:42 ` [pve-devel] [PATCH widget-toolkit 2/3] DateTimeField: Extend and refactor to make field value bindable Christian Ebner
2023-06-06 14:47 ` Thomas Lamprecht [this message]
2023-03-23 14:42 ` [pve-devel] [PATCH widget-toolkit 3/3] fix #4442: Extend LogView for firewall datetime filtering Christian Ebner
2023-03-23 14:42 ` [pve-devel] [PATCH pmg-gui 4/4] DateTimeField: fix typo in xtype Christian Ebner
2023-03-23 14:42 ` [pve-devel] [PATCH manager 5/5] fix #4442: Add date-time filtering for firewall logs Christian Ebner
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=a915700a-f34e-7017-ce86-aebd217d3230@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=c.ebner@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