Open markst opened 1 year ago
@markst Thanks for opening the issue. Can you provide a sample Package.swift file to reproduce this?
I've put together a project to reproduce: DependencyDemo.zip
Does seem that it may be due to the location of the package being nested with a directory. For instance if I move the package up a level:
my output is as follows:
digraph g {
layout=dot
rankdir=LR
subgraph cluster_package_MyLibrary {
label="MyLibrary"
packageProduct_MyLibrary [label="MyLibrary", shape=ellipse]
target_MyLibrary [label="MyLibrary", shape=box]
target_MyLibraryTests [label="MyLibraryTests", shape=box]
}
subgraph cluster_project_DependencyDemoxcodeproj {
label="DependencyDemo.xcodeproj"
target_DependencyDemo [label="DependencyDemo", shape=box]
}
packageProduct_MyLibrary -> target_MyLibrary
target_MyLibraryTests -> target_MyLibrary
target_DependencyDemo -> packageProduct_MyLibrary
}
What happened?
What are the steps to reproduce?
Use local Swift Packages with dependencies on other local packages
What is the expected behavior?
Dependency graph should interpret local package nodes.