1c-cfe-validate

You can validate 1C CFE extension XML files by running a script against your extension folder to check XML well-formedness, required fields, and cross-references, generating a validation report to catch structural issues before deployment.

1C CFE configuration validation checks InternalInfo entries, language references, borrowed objects, form dependencies, and extension-specific properties like ObjectBelonging and NamePrefix to ensure consistent metadata and safe deployment.

Yes, you can use this validation in CI pipelines for pre-release checks by running the cfe-validate script against your extension folder to automatically identify structural and configuration issues in your 1C CFE metadata.

Yes, the 1C CFE validator requires the lxml library to parse and enforce XML well-formedness, validate required metadata fields, and verify cross-references across configuration extension files.

The best way to check borrowed objects and form dependencies is applying validation to extension XMLs, which verifies ChildObjects completeness, BaseForm checks, and sub-item consistency across all metadata directories.