📚 Update external links (#1512)

[KATO-Hiro]

close #1512

Summary by CodeRabbit

• New Features
  • Updated external links to include a new URL for ICPC Japan Problems.
  • Removed the old AOJ ICPC URL and replaced it with the new ICPC Japan Problems URL.
• Bug Fixes
  • Corrected the title and path for the ICPC link in the external links array.

[coderabbitai]

Walkthrough

The changes involve updating constants related to external links in the codebase. The constant AOJ_ICPC_URL has been removed and replaced with ICPC_JAPAN_PROBLEMS_URL. This update is reflected in both the src/lib/constants/external-links.ts and src/lib/constants/urls.ts files, where the corresponding entries and URLs have been modified. The overall structure of the external links remains unchanged aside from these updates.

Changes

File	Change Summary
src/lib/constants/external-links.ts	Removed AOJ_ICPC_URL, added ICPC_JAPAN_PROBLEMS_URL, and updated the externalLinks array.
src/lib/constants/urls.ts	Removed AOJ_ICPC_URL with its URL, added ICPC_JAPAN_PROBLEMS_URL with the new URL.

Assessment against linked issues

Objective	Addressed	Explanation
Update external links as recommended (#1512)	✅

🐰 In the world of links, we hop and play,
With AOJ gone, we found a new way.
ICPC Japan Problems, bright and clear,
A change for the better, let’s all cheer!
🌟 So here’s to the updates, fresh and bright,
Guiding us forward, a wonderful sight!

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between fec2e79 and 068fc05.

📒 Files selected for processing (2)

• src/lib/constants/external-links.ts (2 hunks)
• src/lib/constants/urls.ts (1 hunks)

🔇 Additional comments (4)

src/lib/constants/external-links.ts (2)

6-6: LGTM! Import statement correctly updated

The addition of ICPC_JAPAN_PROBLEMS_URL import aligns with the PR objective of transitioning from AOJ-ICPC to ICPC Japan Problems.

---

15-15: Verify the new external link functionality

The replacement of AOJ-ICPC with ICPC Japan Problems is implemented correctly. Please ensure:

1. The link is accessible and working in the production environment
2. Users are properly redirected to the new platform
3. Any documentation referencing the old AOJ-ICPC platform is updated accordingly

src/lib/constants/urls.ts (2)

22-22: LGTM on constant declaration!

The new constant follows the established naming conventions and type annotations consistently with the rest of the codebase.

---

22-22: Please verify the URL authenticity

The URL domain irrrrr.cc seems unusual. Could you please confirm this is the official/recommended URL for ICPC Japan Problems? This verification is important to ensure we're directing users to the correct and secure platform.

---

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
• Mastodon
• Reddit
• LinkedIn

🪧 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.
  • 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 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.