1c-cfe-diff

To identify borrowed objects and interceptors in a 1C configuration extension, you can analyze the extension XML and read .bsl code. This process detects adopted components and interceptor patterns like &Перед, &После, and &Вместо embedded in modules.

Checking #Вставка block transfer completeness in a 1C extension involves comparing these blocks against corresponding base configuration modules. This transformation check verifies that all necessary modifications were successfully migrated from the original configuration.

Yes, you can detect form, event, and command interceptors in 1C .bsl files automatically by parsing extension XML. The tool locates and summarizes specific interceptor patterns such as &ИзменениеИКонтроль and #Вставка blocks within the code.

The best way to compare a 1C CFE extension against its base configuration is to parse the extension XML and diff the contents. This reveals the composition, borrowed objects, and migration status to understand exactly what the extension changes.

Yes, you need the lxml dependency to parse 1C extension XML files for borrowed object analysis. The library is required to read the XML structures and extract configuration data needed to identify adopted objects and interceptor patterns.

1C extension analysis might miss event interceptors during migration checks if the parser does not fully read Form.xml or fails to detect specific patterns like &Вместо in .bsl code. Ensure all extension modules are correctly parsed against the base configuration.