Replace isExternal to distinguish a source of the project
#22
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
6 tasks
woin2ee
force-pushed
the
supplement-project-model
branch
from
7783f00
to
5c83961
Compare
|
@woin2ee I suggest that we merge this one once we have the changes working on the tuist side |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It's related to tuist/tuist#6436
So far, we've distinguished a project generated from
Package.swiftwithisExternal, but in order to take one step further, we need to separate local from remote packages.In current Tuist version, it already distinguishing them in several points. However we're aware of that assuming with the path is not ideal so, I propose this changes. Does it look fine?