fix: too many toast errors in no project access state

[a-lider]

Problem

Users with no access to any project get flooded with error toasts.

Changes

• Suppress toast errors for 403 responses coming from loaders. Rely on the existing Access Denied UI states (ErrorProjectUnavailable / ErrorAccessDenied).
• This seems more maintainable and consistent than adding try/catch 403 handling in every logic

How did you test this code?

Manually

[github-actions]

Size Change: 0 B

Total Size: 2.68 MB

ℹ️ View Unchanged

Filename	Size
frontend/dist/toolbar.js	2.68 MB

_{compressed-size-action}

[greptile-apps]

Greptile Summary

This PR fixes a UX issue where users with restricted project access were being overwhelmed with toast error notifications. The change modifies the global error handler in frontend/src/initKea.ts to suppress toast notifications for 403 (Forbidden) responses that come specifically from loader actions (methods starting with "load", "get", or "fetch").

The implementation adds a regex pattern /^(load|get|fetch)[A-Z]/ to identify loader actions and excludes them from showing toast errors when they receive 403 status codes. Instead of displaying multiple error toasts, the application relies on existing dedicated UI error states like ErrorProjectUnavailable and ErrorAccessDenied components to handle access denied scenarios.

This centralized approach is more maintainable than adding individual try/catch blocks throughout the codebase for every potential 403 error. The change follows the existing pattern where specific error types (like 401 for authentication) are handled by dedicated systems rather than generic toast notifications. The regex specifically targets loader actions because these are the primary operations that fail with 403 when users lack project access, while preserving toast notifications for 403 errors from other types of operations where they might still be appropriate.

Confidence score: 5/5

• This PR is safe to merge with minimal risk as it addresses a specific UX issue with a targeted solution
• Score reflects a well-thought-out centralized approach that maintains consistency with existing error handling patterns
• No files require special attention as the change is localized and follows established conventions

_{1 file reviewed, no comments}

_{Edit Code Review Bot Settings | Greptile}