Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

refactor: improve MoveItemToTrash error description #23589

Merged
merged 1 commit into from
May 18, 2020

Conversation

codebytere
Copy link
Member

Description of Change

Very mild refactor to MoveItemToTrash on macOS - when failure occurred we would LOG that a failure occurred but not make the failure's underlying cause available to the user, which would help them better diagnose that failure. This improves that experience by ensuring that the localized error description is included in the log.

cc @ckerr @jkleinsc

Checklist

Release Notes

Notes: Improved error logging on moveItemToTrash failures on macOS.

@electron-cation electron-cation bot added the new-pr 🌱 PR opened in the last 24 hours label May 14, 2020
@codebytere codebytere requested review from ckerr and jkleinsc May 14, 2020 15:47
@codebytere codebytere force-pushed the better-trash-description-macos branch from 3303490 to cfc899b Compare May 14, 2020 15:48
@electron-cation electron-cation bot removed the new-pr 🌱 PR opened in the last 24 hours label May 15, 2020
@codebytere codebytere merged commit 75fd9a3 into master May 18, 2020
@release-clerk
Copy link

release-clerk bot commented May 18, 2020

Release Notes Persisted

Improved error logging on moveItemToTrash failures on macOS.

@trop
Copy link
Contributor

trop bot commented May 18, 2020

I have automatically backported this PR to "9-x-y", please check out #23628

@trop
Copy link
Contributor

trop bot commented May 18, 2020

I have automatically backported this PR to "8-x-y", please check out #23629

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants