public inbox for yew-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Hannes Laimer <h.laimer@proxmox.com>
To: yew-devel@lists.proxmox.com
Subject: [yew-devel] [PATCH yew-comp] pending_property_view: rename QemuPendingConfigValue to PendingConfigValue
Date: Wed, 26 Nov 2025 11:41:52 +0100	[thread overview]
Message-ID: <20251126104152.81771-1-h.laimer@proxmox.com> (raw)

Adapt to the renaming in pve-api-types [1].

[1] c0d8370 ("pve-api-types: rename QemuPendingConfigValue to PendingConfigValue")

Signed-off-by: Hannes Laimer <h.laimer@proxmox.com>
---
 src/pending_property_view/mod.rs | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/src/pending_property_view/mod.rs b/src/pending_property_view/mod.rs
index 2747bc5..e10d99b 100644
--- a/src/pending_property_view/mod.rs
+++ b/src/pending_property_view/mod.rs
@@ -22,7 +22,7 @@ use pwt::AsyncAbortGuard;
 use pwt::{prelude::*, AsyncPool};
 
 use crate::{http_get_full, ApiLoadCallback, EditableProperty, PropertyEditDialog};
-use pve_api_types::QemuPendingConfigValue;
+use pve_api_types::PendingConfigValue;
 
 /// Pending configuration data
 ///
@@ -45,7 +45,7 @@ impl PvePendingConfiguration {
         }
     }
 
-    pub fn from_config_array(data: Vec<QemuPendingConfigValue>) -> Self {
+    pub fn from_config_array(data: Vec<PendingConfigValue>) -> Self {
         let (current, pending, keys) = pve_pending_config_array_to_objects(data);
         Self {
             current,
@@ -77,7 +77,7 @@ pub fn pending_typed_load<T: DeserializeOwned + Serialize>(
 
 /// Note: PVE API sometime return numbers as string, and bool as 1/0
 pub fn pve_pending_config_array_to_objects_typed<T: DeserializeOwned + Serialize>(
-    data: Vec<QemuPendingConfigValue>,
+    data: Vec<PendingConfigValue>,
 ) -> Result<PvePendingConfiguration, Error> {
     let (current, pending, keys) = pve_pending_config_array_to_objects(data);
 
@@ -376,7 +376,7 @@ pub fn render_pending_property_value(
 /// Returns 2 Objects, containing current and pending configuration,
 /// and the set of contained configuration keys.
 pub fn pve_pending_config_array_to_objects(
-    data: Vec<QemuPendingConfigValue>,
+    data: Vec<PendingConfigValue>,
 ) -> (Value, Value, HashSet<String>) {
     let mut current = serde_json::Map::new();
     let mut pending = serde_json::Map::new();
-- 
2.47.3



_______________________________________________
yew-devel mailing list
yew-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/yew-devel


             reply	other threads:[~2025-11-26 10:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-26 10:41 Hannes Laimer [this message]
2025-11-26 20:54 ` [yew-devel] applied: " 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=20251126104152.81771-1-h.laimer@proxmox.com \
    --to=h.laimer@proxmox.com \
    --cc=yew-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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal