-
-
Notifications
You must be signed in to change notification settings - Fork 321
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
fix: add missing BuildSettingsProvider for visionOS #898
fix: add missing BuildSettingsProvider for visionOS #898
Conversation
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.
Thanks @alexanderwe
I think that makes sense. Thoughts @fortmarek ? |
I'm aligned with that as well 👍 |
In that case let's propagate your changes as suggested by @kwridan and we can then merge the PR. Thanks a lot @alexanderwe for this one 🚀 |
Add new test cases for additional visionOS mappings Add tests for missing watchOS cases
@kwridan @pepicrft @fortmarek I have rechecked the cases and added visionOS where needed. In addition I have now also added unit tests for these new cases. While doing that I also saw that the |
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.
Thanks! Looks good 🙂
These minor fly-by changes are fine – thanks for improving that! |
@fortmarek Thanks for merging ! |
Short description 📝
Tuist
introducedXcodeGraph
at version 0.19.4 with this PR tuist/tuist#7083. This in fact caused this PR to take effect tuist/XcodeGraph#79. This then ultimately caused this codepath https://github.com/tuist/tuist/blob/main/Sources/TuistGenerator/Settings/DefaultSettingsProvider.swift#L115 to not includevisionOS
related default settings.Solution 📦
I added the mapping of
visionOS
to theBuildSettingsProvider
in order to also correctly set the settings forvisionOS
.Implementation 👩💻👨💻
visionOS
mappings toBuildSettingsProvider
BuildSettingProviderTests
to test the newly added mappingsQuestions
CODE_SIGN_IDENTITY
on thevisionOS
platform in order to be aligned with theiOS
one - what do you think ?