Skip to content

fix: add accountId support to languages, pr-breakdown, weekly-summary, issues routes and components#1339

Open
ionfwsrijan wants to merge 1 commit into
Priyanshu-byte-coder:mainfrom
ionfwsrijan:fix/issue-1310-multi-account
Open

fix: add accountId support to languages, pr-breakdown, weekly-summary, issues routes and components#1339
ionfwsrijan wants to merge 1 commit into
Priyanshu-byte-coder:mainfrom
ionfwsrijan:fix/issue-1310-multi-account

Conversation

@ionfwsrijan
Copy link
Copy Markdown

@ionfwsrijan ionfwsrijan commented May 27, 2026

Description

Fixes #1310

Adds \accountId\ support to 4 API routes and 4 frontend components that were ignoring the selected GitHub account, causing half the dashboard to show data for the wrong account when switching accounts.

API Routes Fixed

  • /api/metrics/languages\ — resolves account-specific token and \github_login\
  • /api/metrics/pr-breakdown\ — resolves account-specific token (@me\ follows the token)
  • /api/metrics/weekly-summary\ — resolves account-specific token and login
  • /api/metrics/issues\ — resolves account-specific token

Components Fixed

  • \IssueMetrics\ — reads \selectedAccount\ from \useAccount(), passes \�ccountId\ in fetch URL
  • \WeeklySummaryCard\ — reads \selectedAccount\ from \useAccount(), passes \�ccountId\ in fetch URL
  • \LanguageBreakdown\ — reads \selectedAccount\ from \useAccount(), passes \�ccountId\ in fetch URL
  • \PRBreakdownChart\ — reads \selectedAccount\ from \useAccount(), passes \�ccountId\ in fetch URL

Pattern Used

Follows the same pattern as existing \contributions\ and \streak\ routes: when \�ccountId\ query param is provided and differs from the session's \githubId, the route resolves the app user, fetches the linked account's token (and login where needed) from \user_github_accounts\ via \getAccountToken, and uses those credentials for GitHub API calls.

@vercel
Copy link
Copy Markdown

vercel Bot commented May 27, 2026

@ionfwsrijan is attempting to deploy a commit to the PRIYANSHU DOSHI's projects Team on Vercel.

A member of the Team first needs to authorize it.

@github-actions github-actions Bot added gssoc26 GSSoC 2026 contribution type:bug GSSoC type bonus: bug fix type:feature GSSoC type bonus: new feature labels May 27, 2026
@github-actions
Copy link
Copy Markdown

GSSoC Label Checklist 🏷️

@Priyanshu-byte-coder — please apply the appropriate labels before merging:

Difficulty (pick one):

  • level:beginner — 20 pts
  • level:intermediate — 35 pts
  • level:advanced — 55 pts
  • level:critical — 80 pts

Quality (optional):

  • quality:clean — ×1.2 multiplier
  • quality:exceptional — ×1.5 multiplier

Validation (required to score):

  • gssoc:approved — counts for points
  • gssoc:invalid / gssoc:spam / gssoc:ai-slop — does not score

Type labels (type:*) are auto-detected from files and title. Review and adjust if needed.
Points formula: (difficulty × quality_multiplier) + type_bonus

Copy link
Copy Markdown

@github-actions github-actions Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for your first PR on DevTrack! 🎉

A maintainer will review it within 48 hours. While you wait:

  • Make sure CI is passing (type-check + lint)
  • Double-check the PR description is filled out and the issue is linked
  • Feel free to ask questions in Discussions if you need help

If you find DevTrack useful, a ⭐ star on the repo is always appreciated — it helps the project grow and attract more contributors!

@ionfwsrijan ionfwsrijan force-pushed the fix/issue-1310-multi-account branch from 52190f1 to 758b16e Compare May 27, 2026 19:51
@ionfwsrijan
Copy link
Copy Markdown
Author

@Priyanshu-byte-coder You may review and merge

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

gssoc26 GSSoC 2026 contribution type:bug GSSoC type bonus: bug fix type:feature GSSoC type bonus: new feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Multi-Account Switching Silently Breaks Half the Dashboard

1 participant