Fix xcconfig override issue

[Kyle-Ye]

Summary by CodeRabbit

• Chores
  • Updated build configuration files to improve management of preprocessor and Swift compilation condition settings.
  • Introduced shared configuration settings for easier maintenance across debug and release builds.
  • Improved scoping of build flags for OpenSwiftUI and debug configurations.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This update restructures the Xcode build configuration files to centralize and modularize the handling of preprocessor and Swift compilation condition flags. New include directives for a shared common.xcconfig file are added to several configuration files, enabling shared logic. The definitions for OpenSwiftUI and debug-specific flags are moved to more granular, suffixed variables, and the aggregation of these variables is now handled in common.xcconfig. The changes do not affect any exported or public code entities.

Changes

File(s)	Change Summary
Configurations/Shared/OpenSwiftUI-debug.xcconfig Configurations/Shared/OpenSwiftUI-release.xcconfig Configurations/Shared/SwiftUI-debug.xcconfig Configurations/Shared/SwiftUI-release.xcconfig	Added an include directive for basic/common.xcconfig to share configuration logic across multiple build configurations.
Configurations/Shared/basic/OpenSwiftUI.xcconfig	Renamed generic preprocessor and Swift condition keys to _OPENSWIFTUI suffixed keys; removed inherited values.
Configurations/Shared/basic/common.xcconfig	Introduced aggregation of preprocessor and Swift condition variables from OpenSwiftUI and Debug-specific definitions.
Configurations/Shared/basic/debug.xcconfig	Removed inclusion of common.xcconfig; moved debug flags to suffixed variables for explicit configuration.

Poem

🐇
In the warren of configs, we hop and we weave,
Centralizing flags, so no settings will leave.
With common includes, our builds now align,
Debug and release, all settings combine.
OpenSwiftUI’s flags, now tidy and neat—
This rabbit declares: our configs are complete!
🥕

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between defe00d and 35e95df.

📒 Files selected for processing (7)

• Configurations/Shared/OpenSwiftUI-debug.xcconfig (1 hunks)
• Configurations/Shared/OpenSwiftUI-release.xcconfig (1 hunks)
• Configurations/Shared/SwiftUI-debug.xcconfig (1 hunks)
• Configurations/Shared/SwiftUI-release.xcconfig (1 hunks)
• Configurations/Shared/basic/OpenSwiftUI.xcconfig (1 hunks)
• Configurations/Shared/basic/common.xcconfig (1 hunks)
• Configurations/Shared/basic/debug.xcconfig (1 hunks)

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 20.94%. Comparing base (defe00d) to head (35e95df).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #265      +/-   ##
==========================================
- Coverage   20.96%   20.94%   -0.02%     
==========================================
  Files         337      337              
  Lines       15486    15486              
==========================================
- Hits         3246     3244       -2     
- Misses      12240    12242       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.