feat: error toasts #368
Open
feat: error toasts #368
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Wiz Scan Summary
To detect these findings earlier in the dev lifecycle, try using Wiz Code VS Code Extension. |
joshsny
approved these changes
Dec 19, 2025
jonathanlab
commented
Dec 19, 2025
Contributor
Author
There was a problem hiding this comment.
Maybe we should just render the error in the screen instead of a toast if it triggers the error boundary.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This makes handling errors and warnings easier for our setup.
In development, we now render toasts for uncaught exceptions and unhandled rejections in both renderer and main, preload errors, and trpc query/mutation errors.
We can now also send any toast to the user from the main process via the
user-notificationsservice.I added a react error boundary, not sure if we want to keep this around.