-
Notifications
You must be signed in to change notification settings - Fork 106
Allow client to customize buildFor
in custom Xcode schemes
#901
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow client to customize buildFor
in custom Xcode schemes
#901
Conversation
profilingDisabled
b1649b5
to
b5010fc
Compare
@brentleyjones The integration test does not seem to be kicking-off in CI. Any thoughts? |
Let's see if it fixes itself after your next push. If not I'll debug. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't this PR have changed the generator scheme to not have tests
have the running
buildFor
?
Good catch. I ran fixtures update and it did update the settings. Do we need to update the tests to detect changes in scheme files? |
@brentleyjones It looks like Integration Test is not reporting back to GitHub. Thoughts don't how to debug? Also, I realized that I never update the Starlark to support the new build targets. I am creating a PR for that now. |
They should detect changes already, as it simply diffs the whole bundle folder. If they aren't for some reason, yes, we need to fix that.
It's a bug on the Workflows side. We are looking into it. |
Related to #573.
XcodeScheme.BuildTarget
values toXcodeScheme.BuildAction
. The build target provides a means for specifying individualbuildFor
settings.XcodeScheme.withDefautls
. This computed property returns a copy of theXcodeScheme
with the appropriate defaults applied (e.g. default actions, relevantbuildFor
settings).XcodeScheme
,XcodeScheme.BuildAction
, andXcodeScheme.TestAction
.