From: Hannes Laimer <h.laimer@proxmox.com>
To: Dietmar Maurer <dietmar@proxmox.com>,
Yew framework devel list at Proxmox <yew-devel@lists.proxmox.com>
Subject: Re: [yew-devel] [PATCH proxmox-yew-comp v3 1/2] schema_validation: use Schema to populate field properties of number, check- and combobox
Date: Fri, 10 Oct 2025 14:43:55 +0200 [thread overview]
Message-ID: <83bc679c-8c56-476c-8910-6600e507056e@proxmox.com> (raw)
In-Reply-To: <a36aa906-0b5b-4be1-851e-5e0dd846b9a3@proxmox.com>
On 10/10/25 10:32, Dietmar Maurer wrote:
> partially applied.
>
> - setting placeholder is OK
>
> - setting tips from description is problematic, because those
> description are basically for developers and have no translations, so I
> think its not worth to do it.
>
> - setting field default values form schema default is most times not
> what you need (depends highly on your input form logic)
>
> - setting validator for Number makes no sense
> (schema.parse_simple_value() does not add any advantage, because values
> are already parsed - correct me if I am wrong)
>
> - auto-generating Combobox is usually not what we want, because we
> display translated, annotated items...
>
hmm, we can still do that though. for combobox items specifically I feel
like having it still adds some value. There are places where we don't,
and a later .items() does override whatever we took from the schema if
we want to set them ourself.
We don't for example for firewall logging levels or firewall policies
like DROP, REJECT, ACCEPT. Also having the default as a placeholder
automatically is, if nothing else, convenient. tbh, I'm not super sure
how often we do this, so may not be warranted to have a general thing if
only these two end up using it.
> - Dietmar
>
>
_______________________________________________
yew-devel mailing list
yew-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/yew-devel
next prev parent reply other threads:[~2025-10-10 12:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 13:31 [yew-devel] [PATCH proxmox{-yew-widget-toolkit, -yew-comp} v3 0/3] use Schema to populate field properties Hannes Laimer
2025-10-09 13:31 ` [yew-devel] [PATCH proxmox-yew-widget-toolkit v3 1/1] form: expose NumberTypeInfo Hannes Laimer
2025-10-10 8:18 ` [yew-devel] applied: " Dietmar Maurer
2025-10-09 13:31 ` [yew-devel] [PATCH proxmox-yew-comp v3 1/2] schema_validation: use Schema to populate field properties of number, check- and combobox Hannes Laimer
2025-10-10 8:32 ` Dietmar Maurer
2025-10-10 10:46 ` Thomas Lamprecht
2025-10-10 12:43 ` Hannes Laimer [this message]
2025-10-10 13:51 ` Dietmar Maurer
2025-10-09 13:31 ` [yew-devel] [PATCH proxmox-yew-comp v3 2/2] schema_validation: add translated description as tooltip to field and checkbox Hannes Laimer
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=83bc679c-8c56-476c-8910-6600e507056e@proxmox.com \
--to=h.laimer@proxmox.com \
--cc=dietmar@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 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.