bsl-symbol-editing

To replace a BSL method body, the skill locates the module structure, verifies the current method source, and rewrites it using write_module_source. This ensures deterministic, symbol-anchored updates for 1C development in EDT.

Yes, you can insert new BSL code before or after a target procedure. The skill uses the target method's structural line bounds to accurately position and insert the new code into your EDT module.

Symbol-level editing changes method bodies or adds procedures by anchoring updates to code symbols rather than fragile line numbers. It involves module structure lookup, source verification, and rewriting to safely modify 1C BSL modules.

The skill automatically performs post-edit project error checks after rewriting a method body or inserting code. This validation catches syntax errors early, ensuring your EDT-based 1C project remains stable after refactoring.

Yes, this approach is specifically designed for EDT-based 1C development. It applies when you need to replace method bodies, insert code before a method, or insert code after a method in BSL modules.

Symbol-anchored updates prevent fragile manual line editing by locating methods through module structure lookup and verifying source before rewriting. This deterministic approach safely handles BSL refactoring without breaking surrounding code.