Foundry

Is there a clean way to resolve mismatched dependency versions between a parent project and dependencies (via git submodules)? 

When compiling, `forge` seems to use the parent project's dependencies when compiling a dependency, which often causes problems. 

e.g. the parent project has a git submodule for OpenZeppelin v4.9.0, but the parent project has a dependency (e.g. G-UNI) that depends on OpenZeppelin v4.1.0. When I build the parent project, it also builds G-UNI, but uses the parent project's OpenZeppelin submodule (v4.9.0), which causes errors.

Does Soldeer fix this?

Full-stack and Solidity dev @ Axis Finance, OlympusDAO. Formerly: GuardianUI

Smart Contract Engineer at M^0 Labs
pierrickgt.twitter
https://pierrick.turelier.com

In this case, only one (parent project or dependency) would build, as the conflict was with a file that was in different locations in different versions.

How is the parent project building then? Sounds like the parent project wouldn’t be able to build either if you encounter the issue.