What problem does it solve? Exported 1C managed form files (Form.xml) can contain structural defects such as duplicate element IDs, missing companion elements, broken DataPath references, or commands without handlers. Manually inspecting large XML dumps for these errors is slow and error-prone, and defects often surface only at runtime in the 1C platform. ## Core Features & Use Cases - Structural validation: Checks root element and version, AutoCommandBar presence, ID uniqueness across separate element/attribute/command pools, and MainAttribute count. - Reference integrity: Verifies DataPath attributes exist, button CommandName references resolve to declared commands, events have handler names, and commands define an Action. - Companion element checks: Ensures InputField, Table, Button, and other element types include required companions like ContextMenu and ExtendedTooltip. - Use Case: After exporting a document form from Configurator to src/, run the validator on Form.xml to catch a duplicate element ID and a missing ExtendedTooltip before committing the change. ## Quick Start Ask the assistant to run 1c-form-validate against the exported Form.xml file path to check the managed form for structural errors.
