Skip to content

Sayali: add Show/Hide Trackers button to Dashboard Tasks tab header#5321

Merged
one-community merged 2 commits into
developmentfrom
Sayali-ShowTrackers-Final-v2
Jun 6, 2026
Merged

Sayali: add Show/Hide Trackers button to Dashboard Tasks tab header#5321
one-community merged 2 commits into
developmentfrom
Sayali-ShowTrackers-Final-v2

Conversation

@sayali-2308
Copy link
Copy Markdown
Contributor

@sayali-2308 sayali-2308 commented Jun 4, 2026

Description

Implements the Show Trackers and Hide Tasks buttons in the Dashboard Tasks Tab header as requested.
Implements #2 (Priority Medium)

##Main changes explained:
Added "Show Trackers" button to the left of "Hide Tasks" in the Tasks Tab header — trackers hidden by default, clicking expands all users' tracker lists at once
Added "Hide Tasks" button — tasks shown by default, clicking hides the task list for all users
Both buttons toggle their label based on current state (Show Trackers ↔ Hide Trackers, Hide Tasks ↔ Show Tasks)
Updated Warnings.jsx to accept showTrackers prop and sync internal toggle state with the global button

##How to test:
Check into current branch
Do npm install and npm run start to run this PR locally
Clear site data/cache
Log in as admin user
Go to Dashboard → Tasks tab
Verify "Show Trackers" button appears to the left of "Hide Tasks" button below the clock icons
Click "Show Trackers" — all users' tracker lists should expand and button should change to "Hide Trackers"
Click "Hide Trackers" — all tracker lists should collapse
Click "Hide Tasks" — all task lists should hide and button should change to "Show Tasks"
Click "Show Tasks" — all task lists should reappear
Verify this new feature works in dark mode

##Screenshots or videos of changes:
image
image
image
image

##Note:
Both buttons are placed below the clock icons in the Tasks Tab header. "Show Trackers" is on the left, "Hide Tasks" is on the right.

##Additional Notes (Performance Investigation)
Tried to fix the lag with 2447 users. Approaches tried:
Staggered API calls (0-5000ms delay per user) — reduced crashes but still caused freezes
Batch API to reduce 2447 calls to 1 — backend built and working but React re-render freeze remained
React startTransition to prevent UI freeze — not sufficient
The proper fix requires virtual scrolling (react-window) which renders only visible rows (~15 at a time). This would eliminate both the API flood and React freeze but would take 10+ hours to implement.
If this PR causes lag on production, the recommended fix is virtual scrolling. The staggered delay (index % 5000) spreads API calls over 5 seconds to prevent browser crashes.

@netlify
Copy link
Copy Markdown

netlify Bot commented Jun 4, 2026

Deploy Preview for highestgoodnetwork-dev ready!

Name Link
🔨 Latest commit 5b2d5fc
🔍 Latest deploy log https://app.netlify.com/projects/highestgoodnetwork-dev/deploys/6a2104ff312ac80008727833
😎 Deploy Preview https://deploy-preview-5321--highestgoodnetwork-dev.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud Bot commented Jun 4, 2026

@one-community one-community merged commit ec1bad1 into development Jun 6, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants