Fix: Prevent Multiple Comment API Requests When Switching Tabs

[nicktytarenko]

Issue: ResearchHub/issues#699

What?

When switching between tabs (Reviews, Conversation, Bounties) on the work details page, multiple /comments API requests were being sent unnecessarily. This caused:

• Increased server load
• Unnecessary network traffic
• Poor user experience with duplicate requests
• Potential race conditions

Why?

The handleTabChange callback in WorkDocument component was not memoized with useCallback. This caused the function reference to change on every render, which triggered the useEffect in WorkTabs that watches onTabChange in its dependency array.

Sequence of events:

1. User clicks tab (e.g., Reviews)
2. handleTabChange is called, updating activeTab state
3. Component re-renders with new activeTab
4. handleTabChange is recreated (new function reference)
5. WorkTabs receives new onTabChange prop reference
6. useEffect in WorkTabs triggers because onTabChange changed
7. This causes another tab change, repeating the cycle
8. Result: Multiple rapid tab switches -> Multiple comment fetches

How?

Wrapped handleTabChange in useCallback with an empty dependency array to maintain a stable function reference across re-renders.

[chatgpt-codex-connector]

Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits.
Credits must be used to enable repository wide code reviews.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
web	Ready	Preview, Comment	Jan 17, 2026 3:44pm

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud