bsl-refactoring-workflow

To safely rename a BSL method across multiple modules, use a symbol-first workflow that classifies the change, runs a dry-run plan, applies confirmed changes, and reports affected files. This prevents broken references and incomplete renames.

The best way to plan BSL refactoring changes is using dry-run planning for symbol renames. This analyzes the impact across modules and forms, allowing you to confirm changes and review affected files before committing them to the project.

Yes, you can use EDT-MCP to verify BSL code refactoring results. After applying symbol-aware edits or renames, post-change validation through EDT-MCP ensures the structural integrity of modules and forms remains intact without breaking the project.

When automation cannot safely process dynamic calls or form handlers, use manual fallback guidance. This provides alternative paths for uncertain symbols, ensuring refactoring continues safely even when full automation is not viable.

Yes, BSL refactoring supports cross-file changes and form handler updates. The workflow classifies these complex tasks separately from small edits, applying symbol-anchored strategies to manage dependencies across multiple files safely.