one additional comment to the ux: the match field could use a bit of improvement:
the docs describe the current fields, but for users that don't deep dive into the docs first it may be confusing having a simple text input field for that at least when the type is 'exact' we could offer a dropdown for the 'type' value (can still be editable) in the mid/long term i think having a backend generated list of those somehow would make sense (i.e. some kind of 'registering' and an endpoint that lists the types, or other metadata) but i think that was planned by you anyway (or something along those lines?) also it would be good to have a link to the docs on the filter edit panel to the relevant section (e.g. for such things as the types/metadata/etc.) _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
