[pve-devel] applied: [PATCH common/widget-toolkit v4] implement oneOf schema

[Thomas Lamprecht]

Am 16/11/2023 um 16:21 schrieb Dominik Csapak:
> this series implementes the oneOf schema for the api, see the individual
> patches for more details and changelog
> 
> only change is the fixed test for pve-common 3/3
> (did accidentally include the wrong file when sending the patches)
> 
> pve-common:
> 
> Dominik Csapak (5):
>   section config: add test for the schemas
>   tools: add is_deeply
>   json schema: implement 'oneOf' schema
>   section config: allow separated property lists for plugins
>   section config: add tests for separated property lists
> 
>  src/PVE/CLIHandler.pm                 |   2 +-
>  src/PVE/JSONSchema.pm                 | 116 +++++-
>  src/PVE/RESTHandler.pm                |  82 ++++-
>  src/PVE/SectionConfig.pm              | 312 +++++++++++++---
>  src/PVE/Tools.pm                      |  31 ++
>  test/Makefile                         |   2 +
>  test/is_deeply_test.pl                | 142 ++++++++
>  test/section_config_separated_test.pl | 489 ++++++++++++++++++++++++++
>  test/section_config_test.pl           | 133 +++++++
>  9 files changed, 1239 insertions(+), 70 deletions(-)
>  create mode 100755 test/is_deeply_test.pl
>  create mode 100755 test/section_config_separated_test.pl
> 
> proxmox-widget-toolkit:
> 
> Dominik Csapak (1):
>   api-viewer: implement basic oneOf support
> 
>  src/api-viewer/APIViewer.js | 34 +++++++++++++++++++++++++++++++---
>  1 file changed, 31 insertions(+), 3 deletions(-)
> 


applied series, thanks!

As talked off-list, I did a few small squashes to ensure that the isolation (vs.
separated) terminology is used consistently, and changed the interface from passing
an, a bit opaque, "boolean" to enable the property isolation, to a more telling
property_isolation => 1 hash entry.