You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
## Description
closes#6861
`forc` was allowing dependency name being the same (through the use of
`package` alias and the declaration itself) as the project name.
The following two cases are now invalid and produces an error on the
forc-pkg side before going to the compiler.
```TOML
[project]
authors = ["Fuel Labs <[email protected]>"]
entry = "main.sw"
license = "Apache-2.0"
name = "lib_contract"
[dependencies]
lib_contract = { path = "../lib_contract_abi/", package = "lib_contract_abi" }
```
and
```TOML
[project]
authors = ["Fuel Labs <[email protected]>"]
entry = "main.sw"
license = "Apache-2.0"
name = "lib_contract_abi"
[dependencies]
lib_contract = { path = "../lib_contract_abi/", package = "lib_contract_abi" }
```
---------
Co-authored-by: Joshua Batty <[email protected]>
The compiler gets confused when the alias of a dependency is the same as the name of the package:
forc-pkg
should throw an error in this situation, but it doesn't.The text was updated successfully, but these errors were encountered: