Is your feature request related to a problem? Please describe.
CommitPulse already includes a reusable useRecentSearches hook that supports storing, persisting, removing, and clearing recent searches. However, this functionality currently appears to be limited to the Landing Page search experience.
Several other search-driven workflows, such as Repository Comparison, Achievements, Contributors Search, and the Burnout Analyzer, require users to repeatedly enter GitHub usernames or repository names even when they have searched for them previously.
This creates an inconsistent user experience across the application and reduces the value of the existing search history infrastructure.
Describe the solution you'd like
Extend recent search history support to additional search-based tools throughout CommitPulse by reusing the existing useRecentSearches hook.
Suggested improvements:
Display recent searches below relevant search inputs.
Allow users to re-run a previous search with a single click.
Allow removal of individual search entries.
Allow clearing all stored searches.
Maintain a consistent search history experience across all repository analysis workflows.
Potential areas that could benefit include:
Repository Comparison
Achievements
Contributors Search
Burnout Analyzer
Other GitHub username/repository search interfaces
This enhancement would build upon existing infrastructure rather than introducing a new search-history implementation.
Describe alternatives you've considered
An alternative approach would be to keep each search workflow independent and require users to manually re-enter usernames and repository names whenever they revisit a feature.
Another option would be to implement separate search-history logic for each page, but this would duplicate functionality that already exists through the reusable useRecentSearches hook and increase long-term maintenance effort.
Reusing the existing hook provides a more consistent and maintainable solution.
Is your feature request related to a problem? Please describe.
CommitPulse already includes a reusable useRecentSearches hook that supports storing, persisting, removing, and clearing recent searches. However, this functionality currently appears to be limited to the Landing Page search experience.
Several other search-driven workflows, such as Repository Comparison, Achievements, Contributors Search, and the Burnout Analyzer, require users to repeatedly enter GitHub usernames or repository names even when they have searched for them previously.
This creates an inconsistent user experience across the application and reduces the value of the existing search history infrastructure.
Describe the solution you'd like
Extend recent search history support to additional search-based tools throughout CommitPulse by reusing the existing useRecentSearches hook.
Suggested improvements:
Display recent searches below relevant search inputs.
Allow users to re-run a previous search with a single click.
Allow removal of individual search entries.
Allow clearing all stored searches.
Maintain a consistent search history experience across all repository analysis workflows.
Potential areas that could benefit include:
Repository Comparison
Achievements
Contributors Search
Burnout Analyzer
Other GitHub username/repository search interfaces
This enhancement would build upon existing infrastructure rather than introducing a new search-history implementation.
Describe alternatives you've considered
An alternative approach would be to keep each search workflow independent and require users to manually re-enter usernames and repository names whenever they revisit a feature.
Another option would be to implement separate search-history logic for each page, but this would duplicate functionality that already exists through the reusable useRecentSearches hook and increase long-term maintenance effort.
Reusing the existing hook provides a more consistent and maintainable solution.