Preserve generated Swift flags in Example projects - #962
Conversation
🤖 Augment PR SummarySummary: Removes Why: Avoids dropping the availability macro flags and keeps 🤖 Was this summary useful? React with 👍 or 👎 |
There was a problem hiding this comment.
Risk Analysis 🛡️ · Low Risk
✅ Approved — Low-Risk Change
Details
Both edits only remove a target-level OTHER_SWIFT_FLAGS override that lives inside the #if TUIST block, so they affect only Tuist Example-project generation — not swift build, the shipped library, or its consumers.
The OpenSwiftUICore SPM target still sets -module-abi-name OpenSwiftUI directly via .unsafeFlags, so the ABI name is preserved; dropping the override lets Tuist use the package-generated flags that also restore the AvailabilityMacro features.
No executable code paths, tests, schemas, auth, or dependencies change, and the author validated that the workspace regenerates with both flag sets present.
|
/uitest ios |
Summary
Remove the target-level
OTHER_SWIFT_FLAGSoverrides from both Example package manifests.Why
The overrides replaced the Swift flags generated from the package target settings. This dropped the
AvailabilityMacrofeature flags when generating the Example project after the OpenSwiftUI ABI namespace flag was added.Allowing Tuist to use the package-generated settings preserves both the availability feature flags and
-module-abi-name OpenSwiftUIforOpenSwiftUICore.Validation
The Example workspace regenerates successfully, and the resolved
OpenSwiftUICorebuild settings contain both the availability macro flags and the OpenSwiftUI module ABI name.