From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox Datacenter Manager development discussion
<pdm-devel@lists.proxmox.com>,
Dominik Csapak <d.csapak@proxmox.com>
Subject: Re: [pdm-devel] [PATCH proxmox 2/2] pve api types: add cluster options api call
Date: Tue, 2 Dec 2025 00:23:39 +0100 [thread overview]
Message-ID: <1dec5398-9619-4406-ad30-8506459a5f39@proxmox.com> (raw)
In-Reply-To: <20251128101848.1580111-3-d.csapak@proxmox.com>
Am 28.11.25 um 11:18 schrieb Dominik Csapak:
> so we can get e.g. the datacenter notes.
>
> The return schema for this is currently not defined and adding it in
> pve-manager is rather hard.
>
> The reason for this is that while we have defined the datacenter config
> schema for the update call, the properties are all property-strings. In
> the GET call however, we parse these and return a nested object.
>
> We'd either have to copy the whole schema and make sure it does not
> diverge, or find some more elegant way to modify the return schema to
That's not really different to now, nothing really protects us from the
schema changing and then a type not working for older APIs. As of now,
this needs explicit handling either way if anything changes.
And if we would add support for understanding this, then it would not
get really harder to start tracking different versions of the schema
(pve-api-v8.json) and diff them to see what types also need to be
generated in a v8 variant, like we plan for the long run, as that's
rather unrelated from the actual generation itself.
> include the parsed properties (for some properties this even happens
> nested, e.g. a list in a property string gets split into an actual
> array).
Having (optional) support for this would be nice though, and we do have
all the info required for that on the PVE side. As not having to do two
deserialization steps with two different formats for getting the actual
data (json + parse-property-string) can be easily seen as feature.
_______________________________________________
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-12-01 23:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-28 10:18 [pdm-devel] [PATCH datacenter-manager/proxmox/yew-comp 0/8] ui: add remote datacenter/node notes panels Dominik Csapak
2025-11-28 10:18 ` [pdm-devel] [PATCH proxmox 1/2] pve api types: add node config get api call Dominik Csapak
2025-12-01 23:31 ` [pdm-devel] applied: " Thomas Lamprecht
2025-11-28 10:18 ` [pdm-devel] [PATCH proxmox 2/2] pve api types: add cluster options " Dominik Csapak
2025-12-01 23:23 ` Thomas Lamprecht [this message]
2025-12-01 23:31 ` [pdm-devel] applied: " Thomas Lamprecht
2025-11-28 10:18 ` [pdm-devel] [PATCH yew-comp 1/1] notes edit: hide toolbar when editing is not possible Dominik Csapak
2025-12-02 10:52 ` [pdm-devel] applied: " Thomas Lamprecht
2025-11-28 10:18 ` [pdm-devel] [PATCH datacenter-manager 1/5] server: api: add nodes config api Dominik Csapak
2025-12-02 0:23 ` [pdm-devel] applied: " Thomas Lamprecht
2025-11-28 10:18 ` [pdm-devel] [PATCH datacenter-manager 2/5] server: api: pve: add cluster options api call Dominik Csapak
2025-12-02 0:23 ` [pdm-devel] applied: " Thomas Lamprecht
2025-11-28 10:18 ` [pdm-devel] [PATCH datacenter-manager 3/5] ui: pve: rename remote module Dominik Csapak
2025-12-02 0:23 ` [pdm-devel] applied: " Thomas Lamprecht
2025-11-28 10:18 ` [pdm-devel] [PATCH datacenter-manager 4/5] ui: pve: nodes: add panel for notes Dominik Csapak
2025-12-02 0:23 ` [pdm-devel] applied: " Thomas Lamprecht
2025-11-28 10:18 ` [pdm-devel] [PATCH datacenter-manager 5/5] ui: pve: datacenter: add remote notes panel Dominik Csapak
2025-12-02 0:23 ` [pdm-devel] applied: " Thomas Lamprecht
2025-12-02 0:24 ` [pdm-devel] [PATCH datacenter-manager/proxmox/yew-comp 0/8] ui: add remote datacenter/node notes panels 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=1dec5398-9619-4406-ad30-8506459a5f39@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=d.csapak@proxmox.com \
--cc=pdm-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