-
Notifications
You must be signed in to change notification settings - Fork 3.7k
improvement(knowledge): make KB modals toast-only for errors #5349
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
Open
TheodoreSpeaks
wants to merge
2
commits into
staging
Choose a base branch
from
kb-modal-toast-errors
base: staging
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+17
−67
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
onSavedoesn't self-toastThe catch here now only logs — it relies on
onSavebeing backed byuseUpdateKnowledgeBase, whoseonErrorfires the toast before the error re-throws. That coupling is implicit:onSaveis typed as a generic(id, name, description) => Promise<void>, so any future caller that passes a plain async function (no mutationonError) will silently swallow the error with zero user feedback. The removedgetErrorMessageimport was the fallback that made this component self-sufficient regardless of caller. Adding a defensivetoast.error(getErrorMessage(err, 'Failed to update knowledge base'))in the catch is low-cost insurance and keeps the modal correct in isolation.Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Intentional — this is the established pattern in this codebase, not a new coupling introduced here. Server-error toasts are owned by the mutation hook's
onError, not the component:useUpdateKnowledgeBase.onErroralready toasted before this PR, and it's the shared surface for both callers of this modal (knowledge.tsx→handleUpdateKnowledgeBase) and the inline rename in[id]/base.tsx(kbRename→ same hook). Adding atoast.errorin this catch would double-toast every current caller.useCreateKnowledgeBaseto the same pattern, so both KB mutation hooks now own their error toasts.So the catch intentionally only logs — the toast has already fired from the hook. The hypothetical "future caller passes a non-toasting
onSave" would be introducing a caller that violates the hook-owns-errors convention; that caller would add its own handling. Leaving as-is.