This repository has been archived by the owner on Sep 4, 2018. It is now read-only.
Make -findXcodeprojPathForPlugin: a bit more flexible #461
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
Instead of searching only for a file named "PluginName.xcodeproj", take any xcodeproj if there is only one in the searched directory. If multiple xcodeprojs are found, try to find one named like the plugin, return nil for all other cases.
guillaumealgis
force-pushed
the
flexible-xcodeproj-searching
branch
from
7b21859
to
c69919e
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
-findXcodeprojPathForPlugin:to-findXcodeprojPathForPackage:@throw, use NSError insteadPluginName.xcodeproj, it will:nilThis will simplify the process of making a plugin work with Alcatraz, as the authors will no longer need to have the name displayed in the plugins list match the xcodeproj filename.
Fixes #452.