From: "Lukas Wagner" <l.wagner@proxmox.com>
To: "Stefan Hanreich" <s.hanreich@proxmox.com>,
"Proxmox Datacenter Manager development discussion"
<pdm-devel@lists.proxmox.com>
Subject: Re: [pdm-devel] [PATCH proxmox-datacenter-manager 3/4] ui: pve: move node overview to a new overview tab
Date: Wed, 03 Sep 2025 11:48:07 +0200 [thread overview]
Message-ID: <DCJ2JU59DT4N.5RSBHJA84MHO@proxmox.com> (raw)
In-Reply-To: <8b20cc07-8c04-47e6-bc95-3547a40e07a7@proxmox.com>
On Wed Sep 3, 2025 at 11:10 AM CEST, Stefan Hanreich wrote:
> one small nit inline (pre-existing) I noticed while looking over the changes
>
>> +impl yew::Component for NodeOverviewPanelComp {
>> + type Message = Msg;
>> + type Properties = NodeOverviewPanel;
>> +
>> + fn create(ctx: &yew::Context<Self>) -> Self {
>> + ctx.link().send_message(Msg::ReloadRrd);
>> + ctx.link().send_message(Msg::ReloadStatus);
>> + Self {
>> + time_data: Rc::new(Vec::new()),> + cpu_data: Rc::new(Series::new("", Vec::new())),
>> + load_data: Rc::new(Series::new("", Vec::new())),
>> + mem_data: Rc::new(Series::new("", Vec::new())),
>> + mem_total_data: Rc::new(Series::new("", Vec::new())),
>
> pre-existing but this could profit from a Default implementation
>
Mhhm, does that make sense though? Default::default is off course
public, and it does not really make much sense to offer a second way to
instantiate the component that is not `create`... but maybe I'm missing
something here.
>> + rrd_time_frame: RRDTimeframe::load(),
>> + status: None,
>> + last_error: None,
>> + last_status_error: None,
>> + async_pool: AsyncPool::new(),
>> + _timeout: None,
>> + _status_timeout: None,
>> + }
>> + }
>> +
_______________________________________________
pdm-devel mailing list
pdm-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pdm-devel
next prev parent reply other threads:[~2025-09-03 9:48 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-02 15:14 [pdm-devel] [PATCH manager/proxmox{-api-types, -yew-comp, -datacenter-manager} 00/10] PVE node update view Lukas Wagner
2025-09-02 15:14 ` [pdm-devel] [PATCH manager 1/1] api: apt: add JSON schema for 'list_updates' endpoint Lukas Wagner
2025-09-03 8:25 ` [pdm-devel] applied: " Thomas Lamprecht
2025-09-03 8:25 ` [pve-devel] applied: [pdm-devel] " Thomas Lamprecht
2025-09-02 15:14 ` [pdm-devel] [PATCH proxmox-api-types 1/3] Schema2Rust: fix handling of non-optional params Lukas Wagner
2025-09-03 8:57 ` [pdm-devel] applied: " Wolfgang Bumiller
2025-09-02 15:14 ` [pdm-devel] [PATCH proxmox-api-types 2/3] generate: add bindings for various APT functions Lukas Wagner
2025-09-03 8:58 ` [pdm-devel] applied: " Wolfgang Bumiller
2025-09-02 15:14 ` [pdm-devel] [PATCH proxmox-api-types 3/3] refresh bindings Lukas Wagner
2025-09-03 8:59 ` Wolfgang Bumiller
2025-09-02 15:14 ` [pdm-devel] [PATCH proxmox-yew-comp 1/2] apt view: allow to set task_base_url Lukas Wagner
2025-09-02 15:14 ` [pdm-devel] [PATCH proxmox-yew-comp 2/2] apt view: reload if base urls have changed Lukas Wagner
2025-09-02 15:14 ` [pdm-devel] [PATCH proxmox-datacenter-manager 1/4] server: add api for getting available updates/changelogs for remote nodes Lukas Wagner
2025-09-03 8:42 ` Lukas Wagner
2025-09-03 9:02 ` Stefan Hanreich
2025-09-03 9:19 ` Stefan Hanreich
2025-09-03 9:23 ` Lukas Wagner
2025-09-02 15:14 ` [pdm-devel] [PATCH proxmox-datacenter-manager 2/4] ui: pve: promote node.rs to dir-style module Lukas Wagner
2025-09-02 15:14 ` [pdm-devel] [PATCH proxmox-datacenter-manager 3/4] ui: pve: move node overview to a new overview tab Lukas Wagner
2025-09-03 9:10 ` Stefan Hanreich
2025-09-03 9:48 ` Lukas Wagner [this message]
2025-09-03 9:52 ` Stefan Hanreich
2025-09-03 9:55 ` Lukas Wagner
2025-09-02 15:14 ` [pdm-devel] [PATCH proxmox-datacenter-manager 4/4] ui: pve: node: add update tab Lukas Wagner
2025-09-03 10:20 ` [pdm-devel] [PATCH manager/proxmox{-api-types, -yew-comp, -datacenter-manager} 00/10] PVE node update view Stefan Hanreich
2025-09-03 11:43 ` [pdm-devel] superseded: " Lukas Wagner
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=DCJ2JU59DT4N.5RSBHJA84MHO@proxmox.com \
--to=l.wagner@proxmox.com \
--cc=pdm-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.