Repository navigation
Fix mobile feature flag isolation warning - #9013
lawrencecchen wants to merge 1 commit into
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughSwift actor-isolation annotations are updated for feature-flag definitions and the mobile workspace changes cached default and flag, enabling non-main-actor access without changing flag values or semantics. ChangesFeature flag isolation
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related PRs
Suggested reviewers: Important Pre-merge checks failedPlease resolve all errors before merging. Addressing warnings is optional. ❌ Failed checks (1 error)
✅ Passed checks (24 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
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. Comment |
Summary
Unblocks the speculative merge gate for #8850.
Testing
mobileWorkspaceChangesFlagactor-isolation warningNeed help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.Summary by cubic
Fixes the Swift concurrency actor-isolation warning for the mobile workspace feature flag. Removes the
mobileWorkspaceChangesFlagwarning and unblocks the merge for #8850.CmuxFeatureFlagDefinitionas nonisolated andSendable.mobileWorkspaceChangesFlagand its defaults nonisolatedstatic let.MainActor-isolated; no behavior changes.Written for commit 355bb3f. Summary will update on new commits.
Summary by CodeRabbit