subsystem-validate

To validate 1C subsystem XML, run the provided PowerShell and Python scripts to parse MetaDataObject structures, check required properties, and verify content item formats against the official schema. The validator catches structural and semantic errors early in development or deployment.

1C subsystem XML validation checks required properties including Name, Synonym, Comment, IncludeHelpInContents, UseOneCommand, Explanation, Picture, and Content. It also verifies boolean values, content item formatting, and ChildObjects entries for single- and multi-subsystem configurations.

Yes, cross-file consistency validation checks ChildObjects entries, detects duplicates, verifies existence of referenced Subsystem files, and optionally validates CommandInterface.xml. This covers both single- and multi-subsystem configurations across the 1C metadata structure.

Yes, lxml is a required dependency for validating 1C subsystem XML structures. The Python scripts rely on lxml to perform XML parsing, property checks, content validation, and cross-file existence checks during the validation process.

1C subsystem XML fails validation when root structure is malformed, required properties like Name or Synonym are missing, content item formats are incorrect, or cross-file references to ChildObjects and Subsystem files are broken. The validator identifies these errors before packaging or deployment.

Validate 1C subsystem XML when creating or modifying a subsystem before packaging or deployment. Early validation catches structural errors, missing required properties, malformed content items, and cross-file inconsistencies before they cause deployment failures.