Repository navigation
feat(errors): reportError, one helper that logs and tells the user (#1761, part 1) - #1794
Merged
Merged
Conversation
This was referenced Oct 25, 2026
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
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.
Part of #1761 (epic #1764).
reportError(context, error, where:, action:)(lib/shared/report_error.dart): writes the failure and its stack toQueryaLogand shows an error toast<action>. <reason>. The reason isdescribeDatabaseError(plain message and hint for driver errors, the error's own text for anything else) with credentials removed. When the context is gone the log is still written and the toast is skipped.saveNewConnectionand the edit path inConnectionsPaneluse it; the text of the toast is unchanged.reportError) for a failed user action,TreeLoadErrorfor a lazy load inside a tree,QueryErrorViewfor a query. Documented onreportError.Not in this PR: replacing the ~46 raw
'$e'messages inlib/features(Redis, Mongo, workspace, ...); they go in follow-up PRs per folder. Not run locally, CI will.