Fix Example Debug compilation conditions - #883
Conversation
🤖 Augment PR SummarySummary: Aligns the Example Tuist-generated package target settings with the app targets so Debug builds define 🤖 Was this summary useful? React with 👍 or 👎 |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #883 +/- ##
===========================================
- Coverage 26.95% 13.78% -13.17%
===========================================
Files 678 638 -40
Lines 47144 41344 -5800
===========================================
- Hits 12706 5701 -7005
- Misses 34438 35643 +1205 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Agent Summary
This updates the Example Tuist package settings so generated package targets receive
DEBUGin Debug configurations, matching the app targets and allowing debug-only code paths to compile into the Example build.The change also makes
ViewRendererVendorprint as its raw vendor identifier, supports string literal initialization for the wrapper type, and prefixes the renderer diagnostic asOpenSwiftUI ViewRendererVendor: ...for easier console scanning.Root cause: the Example app targets had Debug compilation conditions, but the Tuist-generated package targets such as
OpenSwiftUICoreused separate package settings that only configured optimization and compilation mode.Validation:
mise exec -- tuist generate --no-openxcodebuild -workspace Example/Example.xcworkspace -scheme OSUI_Example -configuration OpenSwiftUIDebug -sdk iphonesimulator -destination 'generic/platform=iOS Simulator' CODE_SIGNING_ALLOWED=NO buildswift build --target OpenSwiftUICore