Guidance for address management when fork testing
If you want to fork test a single chain, hard coding your dependencies' addresses in the Solidity tests is a simple and effective approach. However, it doesn't scale well the more chains you want to support for fork testing.
It would be nice if users were given a few tips and tricks about this topic in the Fork Testing tutorial.
For instance, MakerDAO is using JSON configuration files (as per the discussion in https://github.com/foundry-rs/forge-std/pull/268).
adding a link to Uniswap's universal router usage as well (base deploy script inherited by other scripts which define the params)
Sharing Matt Solomon's insights from the Foundry Support group: