Raise pinned waves limit to 20

[simo6529]

Summary by CodeRabbit

Release Notes

• Improvements
  • Increased the maximum number of waves that can be pinned from 10 to 20, enabling broader content curation
  • Enhanced pinned waves feature with improved data management and lifecycle handling for greater stability
  • Pinned waves are now properly cleared upon logout to maintain data consistency

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

The PR increases the maximum pinned waves limit from 10 to 20 across implementation and test files while enhancing the server hook with improved query lifecycle management, explicit type parameters, a new refetch return type, logout data clearing, and refined optimistic update logic.

Changes

Cohort / File(s)	Summary
Configuration Updates hooks/usePinnedWaves.tsx, __tests__/hooks/usePinnedWaves.test.tsx	Increased MAX_PINNED_WAVES constant from 10 to 20 in both the hook implementation and its corresponding test, adjusting loop bounds and assertions.
Server Hook Enhancements hooks/usePinnedWavesServer.ts	Expanded MAX_PINNED_WAVES to 20; updated refetch return type to Promise<QueryObserverResult<ApiWave[], Error>>; added query lifecycle options (enabled, staleTime, gcTime, refetchInterval); improved logout handling via queryClient.setQueryData; refined optimistic update traversal logic for WAVES_OVERVIEW queries; added explicit type parameters for query data access; standardized error message formatting.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

• Pinned sync #1669: Introduces periodic refetch behavior via refetchInterval in query lifecycle, directly related to the query configuration enhancements in this PR.

Suggested reviewers

• ragnep
• prxt6529

Poem

🐰 The waves now dance in numbers grand,
Twenty strong across the land,
With queries swift and data clear,
The pinned collection holds them dear! 📌✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The pull request title 'Raise pinned waves limit to 20' directly and clearly summarizes the main change across all modified files: increasing MAX_PINNED_WAVES from 10 to 20.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[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