🤖 fix: Prevent unhandled promise rejection in web force delete #389
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
When using force delete in web/server mode, an unhandled promise rejection occurs, causing the error to be logged but not properly handled in the UI.
Root Cause: The browser API client's
invokeIPCfunction throws errors for string error messages, while Electron'sipcRenderer.invoke()returns error objects. This inconsistency meant that force delete errors in web mode were thrown as exceptions instead of being returned as{ success: false, error: '...' }.Solution
src/browser/api.tsto return error objects instead of throwing, matching Electron's behaviorremoveWorkspaceandrenameWorkspacein try-catch blocks for extra safety against network/parsing errorssrc/browser/api.test.tsto verify error handling behavior and prevent regressionsTesting
Generated with
cmux