Improvement: Decouple Live API Reliability from Profile Loading

[Yashaswini-K-P]

Description

Currently, fetchUserInfo treats the external LeetCode API as a mandatory dependency. If the live API returns a non-200 status code (e.g., 500 Server Error or 429 Too Many Requests), the livePromise throws an error. Because this error propagates, it prevents the entire function from completing, meaning the UI fails to display even the cached historical data and badges stored in your repository.

Proposed Solution

Make the Live API fetch "graceful" (optional). If fetchWithTimeout for the live API fails, the function should catch the error locally, log it, and allow the function to proceed by returning the already-fetched historical data with ranking and contest set to null.

Implementation Details

• Update the livePromise logic to use a .catch() block that handles errors locally.
• Prevent the error from throwing/propagating to the main fetchUserInfo flow.
• Ensure the function returns a consistent object structure even when the live data is unavailable.

Benefits

• Improved UX: Students will still be able to view their profile, history, and badges even if the external LeetCode API is temporarily experiencing downtime.
• Resilience: Decouples the platform's core dashboard functionality from the health of an external, third-party service.

---

Reference: This addresses the single-point-of-failure in data fetching within fetchUserInfo.js.

[github-actions]

Thank you for opening an issue.

Please review our CONTRIBUTING.md guidelines before getting started.

A maintainer will review this issue shortly. If you would like to work on the issue yourself, please leave a comment requesting assignment.

Issue Assignment Policy

• The issue creator is given the first priority to work on their issue.
• If the creator declines or does not request assignment, the issue will be assigned to others in the order of requests received.
• Please do not submit PRs or begin work until you are officially assigned.

Note: This project is currently maintained by a solo maintainer, so reviews, assignments, and responses may sometimes take a little time. Thanks for your patience.