We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
One of my forge installed libraries uses this import path for it's OZ dependency:
import "@openzeppelin/contracts/token/ERC721/ERC721.sol";
Another one of the contracts from a different library uses this import path:
import "openzeppelin-contracts/contracts/access/AccessControl.sol";
My OZ dependency lives in lib/openzeppelin-contracts
lib/openzeppelin-contracts
My remappings are as such:
@openzeppelin=lib/openzeppelin-contracts/ openzeppelin-contracts/=lib/openzeppelin-contracts/
Unfortunately, the hardhat preprocess does a sed which means that it does the following:
sed
@openzeppelin
lib/openzeppelin-contracts/
lib/lib/openzeppelin-contracts/
I was able to resolve the issue by changing the order of my remappings to avoid the overlap, but this issue may affect others
The text was updated successfully, but these errors were encountered:
yep, i added line = line.replace("lib/lib", "lib") into hardhat config, that fix the problem
line = line.replace("lib/lib", "lib")
Sorry, something went wrong.
No branches or pull requests
One of my forge installed libraries uses this import path for it's OZ dependency:
Another one of the contracts from a different library uses this import path:
My OZ dependency lives in
lib/openzeppelin-contracts
My remappings are as such:
Unfortunately, the hardhat preprocess does a
sed
which means that it does the following:@openzeppelin
withlib/openzeppelin-contracts/
lib/openzeppelin-contracts/
withlib/lib/openzeppelin-contracts/
I was able to resolve the issue by changing the order of my remappings to avoid the overlap, but this issue may affect others
The text was updated successfully, but these errors were encountered: