You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: add troubleshooting tab and fix extension management issues
- Add troubleshooting tab to settings with system and network extension controls
- Address review feedback related to extension management:
- Replace custom notifications with direct method calls for reconfiguration
- Restore proper encapsulation for session state management
- Improve extension uninstallation with proper state monitoring
- Fix deregistration to use existing delegate pattern
- Enhance error handling for network extension operations
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <[email protected]>
Change-Id: I947bae1bc7680bd1f670245e4541a95619ab41ee
Signed-off-by: Thomas Kosiewski <[email protected]>
- Run specific test class: `xcodebuild test -project "Coder Desktop/Coder Desktop.xcodeproj" -scheme "Coder Desktop" -only-testing:"Coder DesktopTests/AgentsTests"`
9
+
- Run specific test method: `xcodebuild test -project "Coder Desktop/Coder Desktop.xcodeproj" -scheme "Coder Desktop" -only-testing:"Coder DesktopTests/AgentsTests/agentsWhenVPNOff"`
10
+
- Generate Swift from proto: `make proto`
11
+
- Watch for project changes: `make watch-gen`
12
+
13
+
## Code Style Guidelines
14
+
- Use Swift 6.0 for development
15
+
- Follow SwiftFormat and SwiftLint rules
16
+
- Use Swift's Testing framework for tests (`@Test`, `#expect` directives)
17
+
- Group files logically (Views, Models, Extensions)
18
+
- Use environment objects for dependency injection
19
+
- Prefer async/await over completion handlers
20
+
- Use clear, descriptive naming for functions and variables
21
+
- Implement proper error handling with Swift's throwing functions
22
+
- Tests should use descriptive names reflecting what they're testing
0 commit comments