[BUG] The searchParams prop is defined in page.tsx but is never used within the page component.

[Shikigami1606]

Describe the Bug

The searchParams prop is defined in page.tsx but is never used within the page component. Keeping unused props increases code clutter and may trigger TypeScript or ESLint warnings, making the codebase harder to maintain.

To Reproduce

Open page.tsx.
Inspect the PageProps interface and the page component.
Notice that searchParams is declared with query, mode, and tag fields.
Observe that searchParams is never referenced anywhere in the component.

Expected Behavior

Unused props should be removed if they are no longer needed. If searchParams is intended for future functionality, it should either be implemented or documented to avoid confusion.

Screenshots/Gifs

N/A

Environment (please complete the following information):

OS: Windows
Browser: Chrome
Node Version: 20.x

Additional Context

Removing the unused searchParams prop will improve code readability, eliminate unnecessary TypeScript/ESLint warnings, and make the component easier to maintain. If future search or filtering functionality is planned, the prop can be reintroduced when it is actively used.

I'd like to work on this issue and submit a fix.
Can you please assign me this issue for SSOC?

[MamidiDhana]

Hi @niharika-mente,
I would like to work on this bug under SSoC'26.
I have reviewed the issue and understand that the unused searchParams prop is creating unnecessary code clutter and may trigger TypeScript/ESLint warnings. My implementation plan includes:

• 🔍 Reviewing the component to confirm whether searchParams is currently required.
• 🧹 Removing the unused prop and related type definitions if it is no longer needed.
• 📝 Ensuring the component remains clean, maintainable, and aligned with the project's coding standards.
• ✅ Verifying that the change introduces no regressions and that the project builds without TypeScript or ESLint warnings.
  If searchParams is intended for upcoming functionality, I will preserve the code in a well-documented manner to avoid confusion while maintaining code quality.
  Kindly assign this issue to me. I would be happy to contribute.
  Thank you!