bug(`config`): file paths not resolved if submodule specifies root path remappings

[mds1]

Component

Forge

Describe the feature you would like

Steps to reproduce:

1. Clone this repo and run forge install
2. Run forge build, it fails with the below error
3. In lib/forge-test-my-dep, open foundry.toml and comment out the remappings
4. Run forge build, it passes

[⠊] Compiling...
Error: 
Failed to resolve file: "/Users/mds/Documents/projects/forge-test-my-proj/lib/forge-test-my-dep/script/BaseScript.sol": No such file or directory (os error 2).
    --> "/Users/mds/Documents/projects/forge-test-my-proj/script/Counter.s.sol"
        "script/BaseScript.sol"
    Check configured remappings.

Additional context

No response

[dalechyn]

suffering from the same exact issue.
importing @thirdweb contracts and OZ in the project breaks remappings.
I have the latest foundry and foundry-std versions

[mattsse]

this is a general problem with absolute import paths.

you can fix this by using relative paths for contracts you import from folders like script or test, or simply overwrite the remapping.

I'd recommend against remappings for folders in the same project.

[mattsse]

ref #1855

[PaulRBerg]

Just bumped into this issue while installing @mds1's library solidity-generators.

I also have absolute import paths, and I want to counter @mattsse's suggestion from above that we should simply use relative paths.

Relative paths can get really ugly and hard to maintain in complex projects; several Foundry users use absolute paths because of the aforementioned reason.