Repository navigation
Fix current Swift warning regressions - #8898
1 commit merged 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 (3)
📝 WalkthroughWalkthroughThree targeted Swift changes update main-actor isolation for window snapshot filtering, optional feature flag initialization with a shared fallback, and sidebar header full-apply detection based on stored action state. ChangesWindow dock concurrency
Content view configuration
Sidebar group header state
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 24 | ❌ 1❌ Failed checks (1 warning)
✅ 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 |
Greptile SummaryThree targeted fixes for Swift warning regressions that were blocking the speculative merge gate: a missing
Confidence Score: 5/5All three changes are minimal, mechanically correct fixes with no user-facing side effects and no new API surface introduced. Each change addresses the stated root cause — actor isolation annotation, default-argument isolation, and a wrong nil-comparison variable — without adding flags, side channels, or new state. The sidebar cell fix also closes a real reuse gap where cells after suspension never received a full model apply, but the scope is narrow and the existing suspension regression test covers the observable behavior. Files Needing Attention: No files require special attention; all three touch sites are small and self-contained. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A["omitsRemoteMirrorOnlyWindow\n(SessionWindowSnapshot extension)"]
B["@MainActor annotation added\n-> resolves Workspace.isRemoteTmuxMirror\nisolation warning"]
A --> B
C["ContentView.init\n(featureFlags: CmuxFeatureFlags = .shared)"]
D["Swift 6 warning:\n@MainActor expression\nas default argument"]
E["Fix: featureFlags: CmuxFeatureFlags? = nil\nself.featureFlags = featureFlags ?? .shared\n(evaluated inside @MainActor init body)"]
C --> D --> E
F["SidebarGroupHeaderTableCellView.configure\nrequiresFullApply = actions == nil"]
G["Bug: 'actions' parameter is non-optional\n-> comparison always false\n-> full-apply never triggered on reuse"]
H["Fix: self.actions == nil\n-> checks stored optional property\n-> full-apply on first configure after suspend"]
F --> G --> H
Reviews (1): Last reviewed commit: "Fix current Swift warning regressions" | Re-trigger Greptile |
Current
mainfails the speculative merge gate because three newly introduced warnings exceed the checked Swift warning budget.This isolates the remote-mirror snapshot helper to
MainActor, resolves the feature-flag singleton insideContentView.init, and restores the group-header reuse check to inspect stored presentation state. The existing suspension regression test covers the sidebar behavior.Verified by tagged cloud build
swbudon macOS 26. The build log contains none of the three failing warning signatures. No user-facing strings changed.Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.Summary by cubic
Restores main to within the Swift warning budget by fixing three new warnings. No functional or UI changes.
SessionWindowSnapshot.omitsRemoteMirrorOnlyWindowwith@MainActorto silence cross-actor access warnings.ContentViewinit to acceptCmuxFeatureFlags?and default to.sharedinside, removing the static default-arg warning.SidebarGroupHeaderTableCellView, computerequiresFullApplyfromself.actionsso reuse checks inspect stored presentation state.Written for commit 8ad567f. Summary will update on new commits.
Summary by CodeRabbit