✨ Quality: maintenance - improve AbortError handling consistency in AI hooks - #84
Conversation
…I hooks This change ensures that all AI-related hooks (useAIPrompt, useAISummarize, useAIWrite, useAIRewriter, useTranslator) correctly transition their status to 'idle' when an AbortError is caught. Previously, the status could remain in a loading/active state after cancellation. Changes: - Updated catch blocks in useAIPrompt, useAISummarize, useAIWrite, useAIRewriter, and useTranslator. - Added test cases for AbortError handling in all corresponding test files. - Verified that all 442 tests pass.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
Improved consistency and robustness of AI hooks by ensuring status resets to 'idle' on AbortError. Added corresponding unit tests for each affected hook.
PR created automatically by Jules for task 16138426460876216808 started by @galiprandi