Ref : Strictly type error handling in try-catch blocks #2079

[hrx01-dev]

🛑 STOP: Assignment & File Scope Check

• I am assigned to this issue.
• I verified that this PR ONLY touches the required files.

Warning

PRs with unrelated files will not be reviewed and may be closed.

📋 PR Summary & Link

• **Closes [Refactor] Strictly type error handling in try-catch blocks #2079 **
• Summary:
• Updated the catch blocks in both handleSave and handleOptOut methods to use catch (err: unknown).
• I used an if (err instanceof Error) check before accessing err.message to set the error message safely.
• Updated the catch block in the sendMessage callback to use catch (err: unknown).
• Added a ternary check (err instanceof Error ? err.message : ...) to safely access err.message without breaking TypeScript's strict rules.

📸 Proof of Work (Screenshots / Logs)

Important

No Pull Request will be merged without proof of testing!

• Frontend/UI changes: You MUST attach screenshots or screen recordings (GIFs/Videos) showing the UI changes.

Please drag & drop your screenshots/GIFs here:

🏷️ PR Type

• 🐛 type: bug
• ✨ type: feature
• 📖 type: docs
• 🧪 type: testing
• 🔒 type: security
• ⚡ type: performance
• 🎨 type: design
• ♻️ type: refactor
• 🛠️ type: devops
• ♿ type: accessibility

✅ Checklist

• My PR has a linked issue (Closes #123)
• I have pulled the latest main and resolved any conflicts

[github-actions]

🎉 Congratulations @hrx01-dev! Your Pull Request "Ref : Strictly type error handling in try-catch blocks #2079" has been successfully merged by @dipexplorer.

Thank you for your valuable contribution to SahiDawa! 🇮🇳
If this was for GSSoC 2026, your work is officially merged and valid. Keep up the great work and feel free to claim other open issues. 🚀

Follow us on LinkedIn: https://www.linkedin.com/company/ratloopz/ to get shoutout