Skip to content
New issue

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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dependency graph command #101

Closed
pepicrft opened this issue Aug 21, 2018 · 1 comment
Closed

Dependency graph command #101

pepicrft opened this issue Aug 21, 2018 · 1 comment
Labels
type:enhancement New feature or request
Projects

Comments

@pepicrft
Copy link
Contributor

What 馃尡

Since Tuist supports defining dependencies between targets and projects, and we have that information when we parse the manifests, we could offer a command that exports the dependency graph. Xcode doesn't provide such feature and I think it's very useful for modular projects where it can be hard to know what depends on what.

We can use the cocoapods-dependencies library as a reference, which does the same for CocoaPods dependencies.

Proposal 馃帀

Add a command that looks like:

tuist dependencies

And export the dependencies using the given format. The first implementation can export it as a JSON and we can add more formats in the future:

{
  "TargetA": {
    "project_path": "/xxx/xxx.xcodeproj",
    "product_type": "application",
    "dependencies": [
      "TargetB"
    ]
  },
  "TargetB": {
    "project_path": "/xx/xx.xcodeproj",
    "product_type": "framework",
    "dependencies": []
  }
}
@pepicrft pepicrft added the type:enhancement New feature or request label Aug 21, 2018
@pepicrft pepicrft added this to Backlog in Planning via automation Aug 21, 2018
@pepicrft
Copy link
Contributor Author

Dependency graph command

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:enhancement New feature or request
Projects
No open projects
Planning
  
Backlog
Development

No branches or pull requests

1 participant