🧪 testing improvement: add missing tests for API error paths

[sunnylqm]

🎯 What:
Added unit tests to tests/api.test.ts to cover the error path in the query method of src/api.ts (the codebase's modern equivalent of the doRequest function requested). It tests when runtimeFetch throws an exception, when the endpoint returns 200 with non-JSON text, and when the endpoint returns a non-200 HTTP status code.

📊 Coverage:

• Simulates network failure to verify RequestError formulation.
• Simulates a 200 status code with an invalid JSON body, verifying that the application correctly logs a warning.
• Simulates a non-200 error response (e.g. 500 status code) to verify that an error with the respective HTTP message and status code is correctly thrown.

✨ Result:

• The missing test coverage across try...catch handlers of runtimeFetch and JSON.parse is now adequately covered, improving testing reliability of API request edge cases.

---

PR created automatically by Jules for task 2537448418202619027 started by @sunnylqm

[google-labs-jules]

👋 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 @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[coderabbitai]

Warning

Rate limit exceeded

@sunnylqm has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 48 minutes and 21 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 2eedfbf3-60ec-4cec-b550-cb10fe8cac10

📥 Commits

Reviewing files that changed from the base of the PR and between 2be3698 and 8fd1031.

📒 Files selected for processing (1)

• tests/api.test.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch test-api-error-paths-2537448418202619027

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}