Editing and tests

Open a contract project#

Open the Foundry or Hardhat root and install its dependencies. In a .sol file, use completion, parameter hints, documentation, and Go to Declaration for imported contracts and members. Use Find Usages and Rename when changing declarations referenced across files.

Review pragma and compiler selection before interpreting errors. Code valid in one Solidity version may require migration in another. The plugin provides version-migration tooling, but its edits need a compiler run and tests.

Run Forge tests#

Open a *.t.sol test file and use the gutter action or a Forge test run configuration. Check the project directory and test filter. Inspect results and navigate back to failures, then rerun the focused test after a fix.

Work with Hardhat#

Use the Hardhat tool window and the project’s configured workflows. Retain the project’s package-manager lockfile and scripts. If compilation fails, reproduce the framework command outside the IDE before changing editor inspections.

Use imports safely#

Prefer IDE navigation and refactoring over broad string replacement. After Optimize Imports, inspect the diff and compile the project. Required imports should remain even when dependency directories are excluded from indexing.