From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id AD51A1FF13E for ; Fri, 06 Mar 2026 12:20:52 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 2F3361F81F; Fri, 6 Mar 2026 12:21:59 +0100 (CET) From: Shannon Sterz To: yew-devel@lists.proxmox.com Subject: [PATCH yew-comp 13/15] qemu_hardware_pane/lxc_resources_panel: allow clippy::enum_variant_names Date: Fri, 6 Mar 2026 12:21:45 +0100 Message-ID: <20260306112148.208189-14-s.sterz@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260306112148.208189-1-s.sterz@proxmox.com> References: <20260306112148.208189-1-s.sterz@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1772796083166 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.102 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_MSPIKE_H2 0.001 Average reputation (+2) SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: VJLHJC6M6AYBFB2L3XPXV73QGCLJV7KY X-Message-ID-Hash: VJLHJC6M6AYBFB2L3XPXV73QGCLJV7KY X-MailFrom: s.sterz@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Yew framework devel list at Proxmox List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: these are publically exposed, so changing them could be an api break. however, it is unlikely that they are being used. in general yew component messages aren't always about disks, so keeping the "Disk" suffix here is fine as these enums may be extended with other variants. Signed-off-by: Shannon Sterz --- src/configuration/pve/lxc_resources_panel/mod.rs | 1 + src/configuration/pve/qemu_hardware_panel/mod.rs | 1 + 2 files changed, 2 insertions(+) diff --git a/src/configuration/pve/lxc_resources_panel/mod.rs b/src/configuration/pve/lxc_resources_panel/mod.rs index ecc9861..9de7add 100644 --- a/src/configuration/pve/lxc_resources_panel/mod.rs +++ b/src/configuration/pve/lxc_resources_panel/mod.rs @@ -24,6 +24,7 @@ use crate::form::typed_load; use crate::pending_property_view::{PvePendingConfiguration, PvePendingPropertyView}; use crate::{http_post, http_put, PropertyEditDialog}; +#[allow(clippy::enum_variant_names)] pub enum Msg { ResizeDisk(String), ReassignDisk(String), diff --git a/src/configuration/pve/qemu_hardware_panel/mod.rs b/src/configuration/pve/qemu_hardware_panel/mod.rs index 03ec910..9430c1c 100644 --- a/src/configuration/pve/qemu_hardware_panel/mod.rs +++ b/src/configuration/pve/qemu_hardware_panel/mod.rs @@ -27,6 +27,7 @@ use crate::{http_post, http_put}; use super::{move_disk_dialog, resize_disk_dialog}; +#[allow(clippy::enum_variant_names)] pub enum Msg { ResizeDisk(String), ReassignDisk(String), -- 2.47.3