fix(dashboard): connecting one social identity shows loading on all provider buttons
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 82/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- nextjs, react, typescript
- Domain
- frontend
Research direction
Start in apps/dashboard/app/(main)/settings/account/page.tsx around lines 780-782, where both social Connect buttons pass the shared linkSocial.isPending flag. Follow the per-item loading pattern the same file already uses for app disconnects, and check the Button loading handling in packages/ui/src/components/button.tsx around lines 228-239. Done when only the clicked provider shows a spinner with aria-busy, the other stays idle but disabled until the flow resolves, and the error toast path is unchanged.
Written by the indexing model from the issue text.
Description
Repro: /settings/account\ -> Connected identities -> click Connect on Google -> both the Google and GitHub buttons show a loading spinner. Root cause: both Connect buttons bind \loading={linkSocial.isPending}\ (one shared mutation, \pps/dashboard/app/(main)/settings/account/page.tsx:780-782), so a single click flips the global flag and every provider button renders its spinner (\packages/ui/src/components/button.tsx:228-239). The same file already scopes per-item loading for app-disconnects via \ ariables; the social buttons missed that pattern. Acceptance: only the clicked provider shows the spinner (\ria-busy); the other stays visibly idle while remaining disabled until the flow resolves; error-toast path unchanged.
Image
https://github.com/user-attachments/assets/a1aafeb5-6504-4fa6-9727-630c35ba1d6e
- Dominant language
- TypeScript
- Stars
- 1.2k
- Forks
- 225
- Avg merge
- 12h 42m
- Merged PRs (30d)
- 288
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from databuddy-analytics/Databuddy
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
databuddy-analytics/Databuddy#1131 · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 86/100
databuddy-analytics/Databuddy#1126 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
databuddy-analytics/Databuddy#1124 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
databuddy-analytics/Databuddy#1108 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
databuddy-analytics/Databuddy#1104 ·
Maintainers usually reply within 1 day
All issues in databuddy-analytics/Databuddy
Similar issues
-
area:security documentation effort:S priority:P2
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
app:web meta:ops
Difficulty 2/5 Half a day Newbie friendliness 78/100
osu-tournament-rating/otr#1113 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
typegoose/mongodb-memory-server#1040 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 92/100