[pve-devel] [PATCH pve-common v1 20/23] sectionconfig: note that a prop must be defined through a JSONSchema
Max R. Carrara
m.carrara at proxmox.com
Fri Dec 19 20:44:55 CET 2025
... in the docstring for the `properties()` method, to make things a
little more obvious for readers less acquainted with
PVE::SectionConfig.
Signed-off-by: Max R. Carrara <m.carrara at proxmox.com>
---
src/PVE/SectionConfig.pm | 3 +++
1 file changed, 3 insertions(+)
diff --git a/src/PVE/SectionConfig.pm b/src/PVE/SectionConfig.pm
index 71a0019..a584e0c 100644
--- a/src/PVE/SectionConfig.pm
+++ b/src/PVE/SectionConfig.pm
@@ -299,6 +299,9 @@ See below for details on L<the different modes|/MODES>.
This method doesn't need to be overridden if no new properties are necessary.
+A property's definition must always be a valid JSON Schema. See
+C<L<PVE::JSONSchema>> for more information on how to define such a schema.
+
sub properties() {
return {
path => {
--
2.47.3
More information about the pve-devel
mailing list