Contract Deploy - Check for exact path segment when extracting contract path in artifacts #643
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Error
I ran into some problems when importing the open-zepline ERC721 contract.

Trying to import this:
Having this error when deploying at the moment it runs the 99_generateTsAbis.ts script:

Explication:
In these lines, it tried to look for ERC721 in available entries (sources), however, it found IERC721 before the actual ERC721.
So he resolved with the path of IERC721 instead.
Fix
Looking for the exact path segment using '/' as prefix for includes argument did the job:
E.g. Looking for
/ERC721
in[
"@openzeppelin/contracts/interfaces/IERC721.sol",
"@openzeppelin/contracts/token/ERC721.sol"
]
Only the second entry matched this time (expected one).
Additional Information
Your ENS/address: Gossman.eth