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
Local path based dependencies are generally going to be represented as relative paths so that they're portable across different developers' machines. This has the issue that it relies on knowledge of where the path is relative to.
Currently when handling local dependencies we assume that the path starts from the root crate's root directory however this is unlikely to be the case in 2nd order dependencies (a dependency of a dependency)
Proposed solution
When resolving local dependencies of local dependencies we should modify the path pointing towards the package to account for the fact that it doesn't start from nargo's working directory.
Alternatives considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Problem
Local path based dependencies are generally going to be represented as relative paths so that they're portable across different developers' machines. This has the issue that it relies on knowledge of where the path is relative to.
Currently when handling local dependencies we assume that the path starts from the root crate's root directory however this is unlikely to be the case in 2nd order dependencies (a dependency of a dependency)
Proposed solution
When resolving local dependencies of local dependencies we should modify the path pointing towards the package to account for the fact that it doesn't start from nargo's working directory.
Alternatives considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: