Saved searches

[arnabnandy7]

Summary

Allow users to save frequently used issue searches.

Motivation

Many contributors repeatedly search for the same technology, label, and filter combinations. Saved searches reduce friction.

Proposed Scope

• Add a save action for the current search.
• Store search parameters per user.
• Provide a saved searches list.
• Allow users to rerun and delete saved searches.

Acceptance Criteria

• Users can save the active search configuration.
• Saved searches can be reopened later.
• Users can delete saved searches.
• Search parameters are restored accurately.

[ShashankShekhar31]

Hi! I’d like to work on #13.

I’d like to add a focused saved-search flow that lets users save the current issue search parameters, view their saved searches, rerun a saved search, and delete it. I’ll keep the existing search behavior unchanged and make sure the saved search restores the original filters accurately.

I’ll first inspect the existing search/state structure, keep the implementation scoped to this issue, and run the project checks before opening a PR.

[ShashankShekhar31]

Hi! I’ve inspected the current search implementation and project structure before starting.

I noticed that #13 requires saved searches to be stored per user, but the current app does not appear to have an authentication or persistence layer yet. The README also lists GitHub authentication as a separate future enhancement.
Before I implement this, could you confirm the intended approach for #13?

Would you prefer:

• saved searches to be implemented with browser-local persistence for now, or
• Saved searches #13 to depend on the GitHub authentication/persistence work first?

I’d like to keep the PR focused and avoid introducing a new auth/database architecture unless that is intended for this issue.

[arnabnandy7]

@ShashankShekhar31 thanks for checking the existing architecture first. Let’s use localStorage for the initial version, since GitHub authentication and server-side persistence are outside the scope of this issue.

Please save the current technology, issue label, sort order, linked PR filter, and Hacktoberfest filter. Users should be able to view their saved searches, rerun one with all filters restored, and delete it.

Keep the storage logic separate and typed so we can replace it with account-based persistence later. It should also handle missing or invalid stored data safely.

For now, “per user” can mean local to the current browser and device. No authentication or database work is needed for this PR.