Re: [PATCH proxmox-yew-comp 1/1] key value list: accept objects as data

[Dominik Csapak <d.csapak@proxmox.com>]

as it's already applied it does not matter for now, but
IMHO this is the wrong fix for the problem

Either the KVList assumes/accepts a list (vec<(string, value)>)
or it works with hashmap/btreemaps

it does not make sense really to enforce a list everywhere but
internally also accept a hashmap?

this will only cause confusion in the future when a user either
enters the same key twice (be it by accident or with intent)

or if someone needs to have multiple same keys in a different context.

Since the use-case for this for now seems to be only a hashmap,
I'd argue we should rework that widget so it works with hashmaps only

this could even improve the usability (e.g. checking if a key already 
exists)

if we do this we should rename it something appropriate e.g.
PropertyMap (suggestion by dietmar)

@Christoph, can you look at that after the release?
(Since you used it in the auto-installer ui part)
If not i can take a look too