Support xcodebuild passthrough args on app install, debug, and diagnose - #325
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
app install,app debug, andapp diagnoseall build but had no way to take xcodebuild arguments, so--worked onapp runand nowhere else in the lifecycle. They take it now, and a project that always needs the same argument can write it insweetpad.toml's new[xcodebuild] argsinstead of typing it each time. Along the way the-derivedDataPathwarning was stale since the locator started following it, the install-side app locator is now the same code as the build's, and the project-discovery note stopped printing twice.Closes #313.