api-error-handling

To handle API errors consistently in uniapp Vue3, use a global interceptor in src/http/alova.ts to map HTTP and business codes to user-friendly messages and severity levels. This prevents duplicated error UI and incorrect try/catch patterns across components.

API error severity is classified into fatal, severe, normal, and light levels. Each level maps to matched UI actions like modal, toast, warning, or silent, ensuring users receive appropriate feedback based on the error's impact.

No, you should not wrap useRequest send() in try/catch. Instead, enforce immediate:false and use onError callbacks for business recovery and state restoration, letting the global interceptor handle the actual error messaging.

Yes, silent requests can disable automatic toasts by leveraging the error classification system. By mapping specific errors to the light severity level, the request processes silently without triggering standard UI warnings.

The best way to standardize form submission error handling is enforcing useRequest with onError callbacks alongside a global responded interceptor. This ensures consistent severity mapping and user feedback without duplicated error UI logic.

Your useRequest onError callback may not trigger if immediate is not set to false or if send() is wrapped in try/catch. Ensure immediate:false is enforced and rely on the interceptor for error mapping.