pimcore-studio-ui-error-handling

Centralize error handling in Pimcore Studio UI by standardizing the use of trackError with ApiError, GeneralError, and ErrorBoundary to ensure consistent reporting and deduplicated alerts across render-time and non-API failures.

The best way to handle RTK Query errors is using a useEffect-based pattern to process error state, avoiding the unwrap approach to ensure consistent UX and centralized tracking via trackError.

Avoiding unwrap with RTK Query prevents inconsistent error states and bypassed tracking, enabling a useEffect-based pattern that deduplicates alerts and centralizes error reporting through trackError.

You do not need to wrap the widget root with an ErrorBoundary because the container already provides one, but explicit ErrorBoundary components are required for isolated UI components to catch render errors.

Use ApiError to wrap API-related failures and GeneralError for non-API failures, routing both through trackError to maintain a consistent user experience and deduplicate alerts across the application.

Pimcore Studio UI error handling supports isolated component render errors by requiring explicit ErrorBoundary wrappers around specific components, preventing render-time failures from crashing the entire application.