feat: add brain missing message

[mamadoudicko]

Description

Screen.Recording.2023-08-16.at.10.42.07.mov

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
docs	🔄 Building (Inspect)	Visit Preview	Aug 16, 2023 8:46am
quivrapp	🔄 Building (Inspect)	Visit Preview	Aug 16, 2023 8:46am

[github-actions]

Risk Level 2 - /home/runner/work/quivr/quivr/frontend/app/chat/[chatId]/hooks/useChat.ts

The code changes are generally safe and follow good practices. However, there are a few areas that could be improved for better readability and error handling:

1. Error Handling: The error handling could be improved. Currently, the error is just logged to the console and a generic error message is shown to the user. It would be better to provide more specific error messages based on the type of error that occurred. This would help in debugging and also provide a better user experience.

   } catch (error) {
     const axiosError = error as AxiosError;
     if (axiosError.response?.status === 429) {
       publish({
         variant: \"danger\",
         text: t(\"limit_reached\", { ns: \"chat\" }),
       });
     } else {
       publish({
         variant: \"danger\",
         text: t(axiosError.message, { ns: \"chat\" }),
       });
     }
   }

2. Use of void: The use of void before track(\"QUESTION_ASKED\") is unnecessary and can be removed for cleaner code.

   track(\"QUESTION_ASKED\");

3. Use of useState: The useState hook is used to store the chatId and generatingAnswer states. However, it's not clear if these states are used elsewhere in the component. If they are not, it might be better to use regular variables instead of state variables to avoid unnecessary re-renders.

---

🔧💬🔄

---

Powered by Code Review GPT