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

chore: show underlying stack in errors in remote module #17851

Merged
merged 1 commit into from Apr 19, 2019

Conversation

nornagon
Copy link
Member

Description of Change

When calling a remote method throws an error, the remote module returns the underlying error's message, but not the stack information, which is useful for debugging. This adds the stack info to the error message.

Checklist

Release Notes

Notes: Added additional error information to errors thrown when using the remote module.

@electron-cation electron-cation bot added the new-pr 🌱 PR opened in the last 24 hours label Apr 18, 2019
Copy link
Member

@codebytere codebytere left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nornagon i think this might be better as a chore perhaps?

@nornagon nornagon changed the title feat: show underlying stack in errors in remote module chore: show underlying stack in errors in remote module Apr 18, 2019
@electron-cation electron-cation bot removed the new-pr 🌱 PR opened in the last 24 hours label Apr 19, 2019
@codebytere codebytere merged commit 841e31b into master Apr 19, 2019
@release-clerk
Copy link

release-clerk bot commented Apr 19, 2019

Release Notes Persisted

Added additional error information to errors thrown when using the remote module.

@codebytere codebytere deleted the remote-error-stack branch April 19, 2019 00:38
kiku-jw pushed a commit to kiku-jw/electron that referenced this pull request May 16, 2019
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

3 participants