[Feature Request]: Fetch and Display LeetCode Contest Rating via Backend Sync

[Yashaswini-K-P]

Description

Currently, our leaderboard handles individual problem-solving metrics (Easy, Medium, Hard solved) and tracking for Global Ranking. However, for a complete competitive programming profile, Contest Rating is a highly important metric that is currently missing.

Since our current profile API endpoint (/:username) does not include contest data, I propose extending our backend sync script (scripts/sync-leaderboard.js) to fetch this data from a separate API endpoint or a direct LeetCode GraphQL query.

[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.

[jagdish-15]

I've extended the current API that the sync script uses to also return contest information in the response:

"contest": {
  "rating": 1964.51283909425,
  "globalRanking": 26108,
  "totalParticipants": 874367,
  "topPercentage": 3.1,
  "attendedContestsCount": 89,
  "badge": "Knight"
}

Since fetch-user-info.js already consumes the same API and returns the user's profile ranking, we can extend it to also include the contest data and expose it through /api/user/:username.

For this issue, please split the work into two PRs:

• A backend PR to extend fetch-user-info.js and the API response to include the contest data.
• A frontend PR to add a separate Contest section on the user profile page and render the contest information returned by the API.

Both PRs can remain linked to this same issue, there's no need to create a separate issue for the frontend portion.