fix: remove unused searchParams prop

[Shikigami1606]

Description

This PR removes the unused searchParams prop from page.tsx, as it was declared but never referenced within the component.

Changes Made

• Removed the unused searchParams prop from the page component.
• Updated the related type/interface by removing the unused fields.
• No functional changes were introduced; this is a code cleanup to improve maintainability and eliminate unnecessary TypeScript/ESLint warnings.

Fixes #

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update (non-code modifications)

How Has This Been Tested?

• Manual testing

Test Steps

1. Run the application locally.
2. Navigate to the affected page.
3. Verify that the page renders as expected.
4. Confirm there are no TypeScript/ESLint warnings related to the removed searchParams prop.

Checklist

• My code follows the style guidelines of this project.
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas (not applicable for this change).
• I have updated the documentation accordingly (not required for this change).
• My changes generate no new warnings or console errors.
• Any dependent changes have been merged and published in downstream modules (not applicable).

Summary by CodeRabbit

• Refactor
  • Simplified the homepage so it no longer depends on incoming page parameters.
  • Kept the existing event loading and recommendation display behavior unchanged.

[vercel]

@Shikigami1606 is attempting to deploy a commit to the niharika-mente's projects Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Warning

Review limit reached

@Shikigami1606, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 55 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 9855ee75-4ced-4b2e-b372-af547cc6f311

📥 Commits

Reviewing files that changed from the base of the PR and between c064137 and af346e8.

📒 Files selected for processing (1)

• app/page.tsx

📝 Walkthrough

Walkthrough

The Page component in app/page.tsx is changed to accept no props, removing the searchParams parameter and the associated PageProps interface. The existing data-fetching flow using getAllEvents() and getRecommendedEvents() remains unchanged.

Changes

Page Component Signature Cleanup

Layer / File(s)	Summary
Remove unused searchParams prop app/page.tsx	The Page function signature is simplified to take no parameters, and the PageProps interface with the searchParams promise type is removed.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related issues

• [BUG] The searchParams prop is defined in page.tsx but is never used within the page component. #134: This issue targets removing the unused searchParams prop from the same Page component in app/page.tsx.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely matches the main change: removing an unused searchParams prop.
Description check	✅ Passed	The description follows the template and includes summary, type of change, testing, and checklist; only the issue number remains a placeholder.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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.}

[SatyamPandey-07]

next time write issue no too @Shikigami1606

[Shikigami1606]

okay i will remember that