fix: add missing type="button" attributes to button elements

[Eshaan-byte]

Proposed change

Resolves #2656

This PR adds the missing type="button" attribute to button elements that are not intended to submit forms. Without this attribute, buttons default to type="submit" which can cause unintended form submissions and unexpected page behavior.

Changes Made

Added explicit type="button" to the following components:

• ToggleableList.tsx (line 42): Search filter buttons
• Search.tsx (line 89): Clear search button
• SortBy.tsx (line 64): Sort order toggle button
• Release.tsx (line 77): Repository navigation button

Note: ModuleList.tsx already had the correct type="button" attribute and didn't require changes.

Testing

• Ran make check-frontend - all linting and formatting checks passed ✅
• Pre-commit hooks executed successfully ✅
• Verified buttons behave as expected (no form submissions)

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
  • Fixed unintended form submission behavior caused by interactive buttons throughout the application. Navigation, search, sorting, and list management controls were inadvertently triggering form submissions when clicked. These controls now function correctly as standalone buttons, eliminating accidental form submissions and providing users with more predictable and reliable interactions.

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

Walkthrough

Added explicit type="button" attributes to button elements across four frontend components (Release, Search, SortBy, ToggleableList) to prevent unintended form submission behavior.

Changes

Cohort / File(s)	Summary
Button Type Attribute Addition frontend/src/components/Release.tsx, frontend/src/components/Search.tsx, frontend/src/components/SortBy.tsx, frontend/src/components/ToggleableList.tsx	Added explicit type="button" attribute to button elements to prevent default form submission behavior; no logic or control flow modifications

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~5–10 minutes

• Verify each button's type="button" attribute is correctly added
• Confirm no functional or behavioral logic was altered
• Ensure consistency across all four component files

Possibly related PRs

• fix: align 'Show more' button in Projects page-#1329 #1894: Modifies ToggleableList.tsx button rendering with a ShowMoreButton component replacement while this PR adds explicit type attributes to the same component.
• fix: improve Sort By dropdown styling consistency #2363: Updates SortBy.tsx sort order button styling alongside this PR's type attribute addition.

Suggested labels

frontend

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 18779b6 and ff570be.

📒 Files selected for processing (4)

• frontend/src/components/Release.tsx (1 hunks)
• frontend/src/components/Search.tsx (1 hunks)
• frontend/src/components/SortBy.tsx (1 hunks)
• frontend/src/components/ToggleableList.tsx (1 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.

---

Tip

✨ Issue Enrichment is now available for GitHub issues!

CodeRabbit can now help you manage issues more effectively:

• Duplicate Detection — Identify similar or duplicate issues
• Related Issues & PRs — Find relevant issues and PR's from your repository
• Suggested Assignees — Find the best person to work on the issue
• Implementation Planning — Generate detailed coding plans for engineers and agents

Disable automatic issue enrichment

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

---

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 passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud