Fixed: Added type to all buttons that are not meant for form submissions.

[KushalSharmaGit]

Proposed change

Resolves #2656

This PR adds the missing type="button" attribute to several <button> elements across the project.

Checklist

• I've read and followed the contributing guidelines.
• I've run make check-test locally; all checks and tests passed.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Summary by CodeRabbit

• Bug Fixes
  • Enhanced button behavior throughout the application to ensure buttons function correctly and do not inadvertently trigger form submissions across various interface components.

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

Walkthrough

This PR adds explicit type="button" attributes to button elements across 16 frontend components to prevent unintended form submission behavior when these buttons are placed inside forms.

Changes

Cohort / File(s)	Summary
Button Type Attributes frontend/src/components/LoginPageContent.tsx, frontend/src/components/MenteeIssues.tsx, frontend/src/components/Milestones.tsx, frontend/src/components/MultiSearch.tsx, frontend/src/components/NavDropDown.tsx, frontend/src/components/RecentIssues.tsx, frontend/src/components/RecentPullRequests.tsx, frontend/src/components/Release.tsx, frontend/src/components/RepositoryCard.tsx, frontend/src/components/ScrollToTop.tsx, frontend/src/components/Search.tsx, frontend/src/components/SortBy.tsx, frontend/src/components/ToggleableList.tsx, frontend/src/components/UserMenu.tsx	Added type="button" attribute to button elements to prevent default form submission behavior
Multi-button Component Updates frontend/src/components/ModuleList.tsx, frontend/src/components/SingleModuleCard.tsx	Added type="button" attributes to multiple button elements within each component

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Specific areas requiring attention:
  • frontend/src/components/ModuleList.tsx — Reported duplicate type="button" attribute on a single tag; verify the attribute appears only once
  • All 16 components — Verify each button addition follows the same pattern and no attributes were inadvertently duplicated

Possibly related PRs

• Feature: scroll to top button #1112 — Directly modifies ScrollToTop.tsx with similar type="button" attribute changes
• UI/ux mentorship program update #2244 — Modifies SingleModuleCard.tsx dropdown rendering alongside button type attribute updates in this PR
• adding feature of anchor links #960 — Modifies the same components (ToggleableList.tsx, RecentIssues.tsx) affected in this PR

Suggested labels

frontend, frontend-tests

Suggested reviewers

• arkid15r
• kasya

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f542220 and 3f24154.

📒 Files selected for processing (16)

• frontend/src/components/LoginPageContent.tsx (1 hunks)
• frontend/src/components/MenteeIssues.tsx (2 hunks)
• frontend/src/components/Milestones.tsx (1 hunks)
• frontend/src/components/ModuleList.tsx (1 hunks)
• frontend/src/components/MultiSearch.tsx (1 hunks)
• frontend/src/components/NavDropDown.tsx (1 hunks)
• frontend/src/components/RecentIssues.tsx (1 hunks)
• frontend/src/components/RecentPullRequests.tsx (1 hunks)
• frontend/src/components/Release.tsx (1 hunks)
• frontend/src/components/RepositoryCard.tsx (1 hunks)
• frontend/src/components/ScrollToTop.tsx (1 hunks)
• frontend/src/components/Search.tsx (1 hunks)
• frontend/src/components/SingleModuleCard.tsx (4 hunks)
• frontend/src/components/SortBy.tsx (1 hunks)
• frontend/src/components/ToggleableList.tsx (1 hunks)
• frontend/src/components/UserMenu.tsx (3 hunks)

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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

[github-actions]

The linked issue must be assigned to the PR author.

[sonarqubecloud]

Quality Gate failed

Failed conditions
C Reliability Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE