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 improve extension management
- Add new Troubleshooting tab to settings with system/network extension controls
- Implement extension uninstallation and granular state management
- Add "Stop VPN on Quit" setting to control VPN behavior when app closes
- Improve error handling for extension operations
- Add comprehensive status reporting for troubleshooting
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <[email protected]>
Change-Id: Id8327b1c9cd4cc2c4946edd0c8e93cab9a005315
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