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
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:
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:
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:
The text was updated successfully, but these errors were encountered: