:docs: Improve contest labels (#1526)

KATO-Hiro commented 4 days ago

Summary by CodeRabbit

New Features
- Added support for new contest types: "TTPC" and "TUPC."
- Enhanced contest classification with improved regex matching for AtCoder and university contests.
- Introduced a new helper function for better label formatting of university contests.
Bug Fixes
- Corrected formatting issues in contest names and expected values for better readability.
- Removed redundant contest test cases to streamline the structure.
Documentation
- Updated translations for contest types to improve output formatting.

coderabbitai[bot] commented 4 days ago

Walkthrough

The changes in this pull request enhance the contest classification and labeling functionality within the codebase. Notable modifications include the addition of new contest types, updates to regex patterns for better contest ID matching, and a refactor of functions to improve readability. The formatting of contest names and expected outputs in test cases has been standardized, ensuring consistency across various contest types. Additionally, translations for contest types have been adjusted for better presentation.

Changes

File Path	Change Summary
`src/lib/utils/contest.ts`	Updated `classifyContest` function to include "TTPC" and "TUPC". Enhanced regex for contest classification. Refactored `getContestNameLabel` to improve matching logic. Added `getAtCoderUniversityContestLabel` function.
`src/test/lib/utils/test_cases/contest_name_and_task_index.ts`	Modified test case string formatting for various contest cases to include spaces. Updated `generateUniversityTestCases` to use the new label function.
`src/test/lib/utils/test_cases/contest_name_labels.ts`	Removed several contest test case definitions and functions. Simplified structure by retaining only relevant contest exports.
`src/test/lib/utils/contest.test.ts`	Removed specific test cases for `getContestNameLabel` related to certain contest IDs due to notational inconsistencies.

Assessment against linked issues

Objective	Addressed	Explanation
Improve readability of contest labels (1526)	✅
Standardize contest name formatting (1526)	✅
Update contest entries for clarity (1526)	❌	Some entries remain unaddressed as per the issue.
Enhance visibility of contest sources (1526)	❓	Changes made, but not all objectives are clear.

🐰 In the fields where contests bloom,
New labels dance, dispelling gloom.
With spaces bright and names so clear,
A joyful cheer for all to hear!
Let's hop along, our path is set,
For contests new, we won't forget! 🐇✨

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

- [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)

🪧 Tips

### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit , please review it.` - `Generate unit testing code for this file.` - `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 generate unit testing code for this file.` - `@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 generate unit testing code.` - `@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.` 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 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](https://docs.coderabbit.ai/guides/configure-coderabbit) 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](https://docs.coderabbit.ai) for detailed information on how to use CodeRabbit. - Join our [Discord Community](http://discord.gg/coderabbit) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.

KATO-Hiro commented 3 days ago

修正範囲は広いですが、それぞれ影響範囲は狭いため少しずつマージしていく方針です。

AtCoder-NoviSteps / AtCoderNoviSteps