CC-42: Cannot Select Player when Submitting Tournament Match Result

[ianpaschal]

Fixes CC-42

Summary by CodeRabbit

• Improvements
  • Player selection field now auto-populates when only one competitor option is available, streamlining the match result entry process.
  • Optimized form initialization and state management for improved user experience and performance.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
combat-command	Ready	Preview, Comment	Apr 29, 2026 7:40pm

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 90c0cb8c-cba8-4ddc-ae2e-cc089f539bba

📥 Commits

Reviewing files that changed from the base of the PR and between 99f1901 and 1de193a.

📒 Files selected for processing (2)

• src/components/MatchResultForm/MatchResultForm.tsx
• src/components/MatchResultForm/components/PlayerField/PlayerField.tsx

💤 Files with no reviewable changes (1)

• src/components/MatchResultForm/MatchResultForm.tsx

---

Walkthrough

The pull request modifies match result form components to change player selection behavior. In the main form component, the explicit default value assignment for player0UserId based on the authenticated user is removed. In the player field component, a new effect is added that automatically populates the player{index}UserId field with the sole available competitor when only one option exists, without marking the form as dirty. Additionally, the readOnly field logic is refactored to use optional chaining for the current user ID comparison and incorporate this check into the final readOnly condition.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is incomplete. It only states 'Fixes CC-42' without following the repository template or providing implementation details.	Expand the description to follow the template format and include details about the changes made, such as auto-population logic and readOnly refactoring.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly references the issue (CC-42) and describes the specific problem being fixed: inability to select a player when submitting tournament match results.
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.

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

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch ian/cc-42-cannot-select-player-when-submitting-tournament-match-result

---

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

_{Review rate limit: 0/1 reviews remaining, refill in 60 minutes.}

_{Comment @coderabbitai help to get the list of available commands and usage tips.}