Trigger validation properly after file movement/rename

[honestbonsai]

I have the following folder structure:

hardhat.config.ts
node_modules
test
    folder1
        folder1.1
            Contract1.sol
        folder1.2
            Contract2.sol
    folder2
        Contract3.sol
        Contract4.sol

I'm doing import "hardhat/console.sol"; in all of the solidity files, however they only work in folder2, and do not work in folder1.1, folder1.2.

I get the following error for all solidity files in folder1.1 and folder1.2:

Source "hardhat/console.sol" not found: File not found. Searched the following locations: "".solidity(6275)

If I change the import for folder1.1 to ../../../node_modules/hardhat/console.sol, the error from VSCode goes away.

I also do import 'openzeppelin-contracts-06/math/SafeMath.sol'; in the solidity files in folder1 and get the error:

Source "openzeppelin-contracts-06/math/SafeMath.sol" not found: File outside of allowed directories.solidity(6275)

In my package.json, I have the alias for openzeppelin-contracts-06

{
    "devDependencies": {
        "openzeppelin-contracts-06": "npm:@openzeppelin/contracts@3.4.2",
    }
}

My tests still run fine and everything compiles, I just get the red underlines and errors from VSCode.

[honestbonsai]

Not sure why but when I open and closed VSCode again, it seems ok now?

But then when I move files around while I'm in VSCode, the error reappears?

[antico5]

@honestbonsai Hi! I noticed this issue happens only while moving files around (rename, move to different folder). In my case, just making a modification to the file removes the error lines (since it re-triggers validation). Can you validate that you get the same behavior? in that case, we can relabel the issue to something like "Trigger validation properly after file movement/rename".

The npm alias for packages e.g. @openzeppelin/contracts is working fine and is supported by the extension.

[honestbonsai]

@antico5 I can confirm what you just said. I did the following:

1. Deep nested file with import "hardhat/console.sol" showing no errors on a freshly opened VSCode
2. Rename the file
3. File shows errors with the import
4. Add a line to the file
5. Error disappears

I agree with your idea for the relabeling to "Trigger validation properly after file movement/rename". Thanks for the help!

[antico5]

@honestbonsai Thank you for reporting! we will address it as soon as possible.

[PaulRBerg]

Just bumped into this bug as well. It's quite a blocker when writing tests with Forge!

Source "forge-std/StdError.sol" not found: File not found. Searched the following locations: "".

Reloading the VSCode windows makes the bug go away, however.

[kanej]

@PaulRBerg are you encountering that error when you move/rename files or is it happening in another context?

[PaulRBerg]

@kanej hard to pin it down, but I know for certain that it also happened after updating my submodules.

[kanej]

@PaulRBerg we suspect we are not updating the foundry project metadata against new (#416) and renamed files (#417) within the foundry project (at least that is our current working theory). We will be looking into both those issues this week.