Fix: Add user feedback via popup for Groq API fetch failures

[dhaarypravi]

Description

This PR improves the user experience by showing a proper error popup when the Groq API fetch fails due to network issues, missing API key, or rate limits.

Changes Made

• Removed console.error() from translateText() and explainText()
• Allowed errors to bubble up so that contextMenus.onClicked() can display user-facing error via showErrorPopup()

Issue

Fixes #11

Summary by CodeRabbit

• Bug Fixes
  • Improved error handling for translation and explanation features, providing clearer error messages when issues occur with API responses.

[coderabbitai]

Walkthrough

The code refactors the translateText and explainText functions in background.js by removing their try-catch blocks. Error handling is now performed by checking the fetch response status and explicitly throwing errors with parsed messages, allowing errors to propagate naturally without internal logging.

Changes

File(s)	Change Summary
background.js	Refactored translateText and explainText: removed try-catch, added explicit error throwing and response checks.

Assessment against linked issues

Objective	Addressed	Explanation
Graceful error handling for API failures in background.js (Issue #11)	❌	Errors are now thrown with messages, but there is still no mechanism to provide UI feedback to users.

Poem

A hop and a skip, the errors now fly,
No more logs to catch the eye.
If trouble brews and fetches fail,
The code throws errors without detail.
But users still wait, with puzzled stare—
UI feedback? It isn’t there!
🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c0e19b8 and 536a1f9.

📒 Files selected for processing (1)

• background.js (3 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• background.js

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.