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

Redirect logs/uncaught errors from webview to the main extension logger #621

Merged
merged 3 commits into from
Oct 14, 2024

Conversation

kmagiera
Copy link
Member

This PR adds a mechanism for redirecting logs and unhandled error from webview to the main extension.

The reason for this change is that we can see potential issues and logs in a unified log output that we create for the extension context. This way we provide better visibility of errors that happen in the webview. Without this change, we'd always need to check both the extension log output, and the vscode devtools panel. With this change, having everything in a single output is specifically helpful when receiving logs from the users, as we no longer need to ask them to check devtools console and can focus on a single log file they need to check or send as a part of the report.

How Has This Been Tested:

Add log statement and unhandled error to the main webview App.tsx. See that this gets included in the main log output.

Copy link

vercel bot commented Oct 14, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
radon-ide ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 14, 2024 11:15am

@kmagiera kmagiera changed the title Kmagiera/webview logging Redirect logs/uncaught errors from webview to the main extension logger Oct 14, 2024
@kmagiera kmagiera merged commit b0e114f into main Oct 14, 2024
3 checks passed
@kmagiera kmagiera deleted the kmagiera/webview-logging branch October 14, 2024 11:36
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.

2 participants