context-map

A codebase context map identifies all relevant files, dependencies, and tests before implementing Protheus ADVPL or TLPP changes. It surfaces direct dependencies and reference patterns to prevent risky modifications and reduce regressions.

To map impacted files before modifying an ADVPL codebase, analyze the task scope to search related files, identify direct dependencies, locate affected tests, and find reference patterns matching established conventions.

Yes, you can use context mapping to identify test impact for TLPP codebases by discovering likely affected tests during the pre-implementation analysis phase. This dependency discovery reduces the risk of regressions.

The best way to plan Protheus code changes is generating a context map that identifies files to modify, dependencies, tests, and reference patterns. This structured risk assessment ensures incomplete modifications are caught before implementation.

Yes, context mapping includes a risk assessment checklist that prompts you to consider breaking changes, migrations, and configuration impacts. This assessment must be structured for reviewer approval before any code modifications begin.

You should analyze reference patterns before implementing TLPP code to locate similar existing implementations and follow established conventions. This matching process ensures new changes align with the current codebase structure.