cfe-validate

To validate a 1C configuration extension, run validation checks against the Configuration.xml file to verify structural correctness, metadata properties, and ChildObjects ordering before pre-commit or CI workflows. This prevents broken extension metadata before running 1C.

XML validation for 1C configuration extensions checks the root element, required Configuration node, expected namespaces, UUID formats, and the presence of InternalInfo and Properties to ensure structural correctness and metadata validity.

Yes, you can check borrowed object consistency by validating borrowed objects like Attribute, TabularSection, EnumValue, and Form, along with their internal dependencies including BaseForm and referenced style elements.

1C configuration extension metadata consistency checks fail when ChildObjects entries violate canonical ordering rules, when expected directory layouts for child metadata types are missing, or when referenced language files are absent from the repository.

No specific 1C environment is needed to run preflight checks on Configuration.xml. The validation process applies schema expectations, enforces required elements, and checks UUID patterns independently as a pre-commit or CI validation step.