Repository navigation
fix(web): show action errors as toasts - #75
Merged
TheGreatAxios merged 2 commits intoNov 2, 2026
Merged
TheGreatAxios merged 2 commits into
TheGreatAxios merged 2 commits into
Conversation
|
Triage: Pass No changes needed from you. A maintainer will review this pull request. |
Contributor
Author
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.


Closes CL-11948
Action failures that were a sentence-only error banner now use
toast.error, the same quiet treatment as an import failure. Starting a project from home no longer renders the inline bar between the headline and the prompt.Persistent page-state banners stay inline: the hub not answering, setup incomplete, a catalog or list that failed to load, and an invitation that could not be read. Connect-a-provider and import-approval stay inline because they carry a next step.
.banner.is-errorno longer sets a destructive border, so any remaining error banner is not a red outline.profiles.tsxandprofile-select.tsxwere not edited.Verified:
bun check --no-script(exit 0, 762 files)bun check --no-script -p packages/client(exit 0)bun check --no-script -p packages/zip(exit 0)bun check --no-script -p apps/web(exit 0)bun run lint(exit 0)bun run format:check(exit 0)bun test ./apps/web/src(22 pass, 0 fail, exit 0)