Skip to content

Conversation

@ianpaschal
Copy link
Owner

@ianpaschal ianpaschal commented Aug 3, 2025

Summary by CodeRabbit

  • New Features

    • Added support for specifying an edition year when creating or editing a tournament.
    • Tournament display names now include the edition year when available.
    • Tournament forms now include a required edition year field with selectable options.
  • Enhancements

    • Tournament title length requirements have been relaxed to allow shorter names.
    • Improved preview of tournament display names in the form interface.
  • Style

    • Updated styles for tournament form fields and muted text for a more refined appearance.

@vercel
Copy link

vercel bot commented Aug 3, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
combat-command ✅ Ready (Inspect) Visit Preview 💬 Add feedback Aug 3, 2025 2:29pm

@coderabbitai
Copy link

coderabbitai bot commented Aug 3, 2025

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

An optional editionYear field was added to tournament models, forms, and schemas. The tournament display name now uses a new utility function that combines the title and edition year. UI components and styles were updated to support this, including form fields, card and banner displays, and muted text styling.

Changes

Cohort / File(s) Change Summary
Tournament Model Schema
convex/_model/tournaments/fields.ts
Added optional numeric editionYear to editableFields.
Tournament Display Name Utility
src/utils/common/getTournamentDisplayName.ts
Introduced getTournamentDisplayName, formatting tournament name with optional year.
Tournament Card and Banner Display
src/components/TournamentCard/TournamentCard.tsx, src/pages/TournamentDetailPage/components/TournamentDetailBanner/TournamentDetailBanner.tsx
Updated to use getTournamentDisplayName for displaying tournament names. Banner now accesses tournament fields via object, not destructured props.
Tournament Form Schema and Defaults
src/components/TournamentForm/TournamentForm.schema.ts
Added required editionYear (coerced to number) to schema and default values. Adjusted title length validation.
Tournament Form Fields and Preview
src/components/TournamentForm/components/GeneralFields.tsx
Added edition year select input, year options helper, and preview section using getTournamentDisplayName. Grouped title and year inputs.
Form Field Styling
src/components/TournamentForm/components/GeneralFields.module.scss, src/style/_text.scss
Added new layout and muted text styles for form fields and preview. Muted text now has font-weight: 300.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~15 minutes


Note

🎁 Summarized by CodeRabbit Free

Your organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/login.

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Join our Discord community for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@ianpaschal
Copy link
Owner Author

@coderabbitai review

@coderabbitai
Copy link

coderabbitai bot commented Aug 3, 2025

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@ianpaschal ianpaschal merged commit d822fa2 into develop Aug 3, 2025
3 checks passed
@ianpaschal ianpaschal deleted the 134-add-edition-year-to-tournaments branch August 3, 2025 14:30
ianpaschal added a commit that referenced this pull request Aug 4, 2025
* #137 Add tooling for automated releases (#139)

* task: Add tooling for automating releases

* task: Move generate component script to /scripts

* #138 Remove storage ID empty strings from tournament form (#140)

* #136 fix: Correctly show ConfigureRound, StartRound and End actions for tournaments (#141)

* #132 Add user profile page (#143)

* feat: Add <CardHeader/>

* feat: Add getMatchResultsByUser()

* feat: Add <UserProfilePage/>

* feat: Link to user profile on identity badge click

* feat: Add user profile to account menu

* #133 feat: Add lists to back-end (#144)

* #134 feat: Add edition year to tournaments (#147)

* feat: Add edition year to tournaments

* fix: Replace accidentally removed mission matrix options

* fix: Improve tournament form label

* Prepare release v1.9.0

* fix: Address v1.9.0 feedback
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants