Fix: avoid passing function reference directly to map() in ContributePage

[Shubb07]

Proposed change

Resolves #3618

This PR fixes a SonarCloud reliability issue (typescript:S7727) in
frontend/src/app/contribute/page.tsx, where the function
renderContributeCard was passed directly to Array.map().

The code has been updated to use an explicit arrow function:
This makes the iterator arguments explicit, improves readability,
reduces the risk of subtle bugs during future refactors, and resolves
the Sonar warning without changing any existing behavior.

• I followed the contributing workflow
• I verified that my code works as intended and resolves the issue as described.
• I ran make check-test locally: all warnings addressed, tests passed
• I used AI for code, documentation, tests, or communication related to this PR

[coderabbitai]

Summary by CodeRabbit

• Bug Fixes
  • Improved stability of the contribution page to handle edge cases more gracefully.

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

Walkthrough

Replaced issues.map(renderContributeCard) with issues?.map((issue, index) => renderContributeCard(issue, index)) in frontend/src/app/contribute/page.tsx, adding an existence check and making the map callback parameters explicit without changing behavior.

Changes

Cohort / File(s)	Summary
Contribute page frontend/src/app/contribute/page.tsx	Changed issues.map(renderContributeCard) to issues?.map((issue, index) => renderContributeCard(issue, index)): added optional chaining and an explicit arrow callback to pass (issue, index) clearly.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Refactor: added optional chaining #2916 — Similar refactor using optional chaining when mapping arrays in React page components.
• fix: prefer optional chaining over logical AND guard (S6582) #3629 — Modifies the same issues.map expression in frontend/src/app/contribute/page.tsx, including optional chaining and explicit index usage.
• fix: prefer optional chaining over logical AND guards (S6582) #3485 — Related pattern changes replacing direct map/guards with optional chaining across list renderings.

Suggested reviewers

• arkid15r
• kasya

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and accurately describes the main change: avoiding passing a function reference directly to map() in the ContributePage component.
Description check	✅ Passed	The description is related to the changeset, explaining the SonarCloud issue being fixed and how the explicit arrow function approach addresses it.
Linked Issues check	✅ Passed	The PR successfully addresses issue #3618 by replacing the direct function reference with an explicit arrow function that forwards iterator parameters, resolving the SonarCloud typescript:S7727 warning.
Out of Scope Changes check	✅ Passed	The changes are focused and in-scope: only the map() call in frontend/src/app/contribute/page.tsx was modified to use an explicit arrow function with optional chaining, directly addressing the linked issue.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

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

---

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

[arkid15r]

Please resolve merge conflicts.

[Shubb07]

Hi @arkid15r , please re-review the PR #3644 , so I could proceed with solving the merge conflicts of this one.

[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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 87.67%. Comparing base (3851523) to head (c8fb749).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3641   +/-   ##
=======================================
  Coverage   87.67%   87.67%           
=======================================
  Files         462      462           
  Lines       14308    14309    +1     
  Branches     1910     1910           
=======================================
+ Hits        12544    12545    +1     
  Misses       1346     1346           
  Partials      418      418           

Flag	Coverage Δ
backend	87.45% <ø> (ø)
frontend	88.27% <100.00%> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
frontend/src/app/contribute/page.tsx	95.00% <100.00%> (+0.26%)	⬆️

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3851523...c8fb749. Read the comment docs.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.