feat: Add linux_loong64 platform setup support

[hustcer]

feat: Add linux_loong64 platform setup support

Summary by CodeRabbit

• New Features

  • Added support for the LoongArch architecture on Linux, expanding compatibility and providing updated download options.

• Chores

  • Updated the spell checker’s custom vocabulary to include “loong,” ensuring it’s recognized as a valid term.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The changes introduce a new custom word "loong" in the spell checker configuration (cspell.yml) and extend the platform support in the setup code (src/setup.ts). The platform type is updated to include a new entry, linux_loong64, with corresponding entries in both the default and full platform mappings. These modifications ensure that the tool recognizes the new word and supports the LoongArch architecture.

Changes

File(s)	Change Summary
cspell.yml	Added custom word "loong" to the list of accepted words.
src/setup.ts	Extended the Platform type with 'linux_loong64' and updated PLATFORM_DEFAULT_MAP and PLATFORM_FULL_MAP with new entries for this platform.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Setup
    participant DEFAULT_MAP
    User->>Setup: Request configuration for platform detection
    Setup->>DEFAULT_MAP: Look up mapping for 'linux_loong64'
    DEFAULT_MAP-->>Setup: Return ['loongarch64-unknown-linux-gnu']
    Setup->>User: Provide platform configuration

Loading

sequenceDiagram
    participant SpellChecker
    participant Config
    SpellChecker->>Config: Load spell-check configuration
    Config-->>SpellChecker: Return word list including "loong"

Loading

Poem

I'm a bunny in the codeyard,
Hopping through changes, light and hard.
"loong" now joins the spelling crew,
And linux_loong64 steps in, too.
Cheers and hops for updates new! 🐇

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d670692 and 8bbccee.

⛔ Files ignored due to path filters (1)

• dist/index.js is excluded by !**/dist/**

📒 Files selected for processing (2)

• cspell.yml (1 hunks)
• src/setup.ts (3 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings

---

🪧 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 generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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.

[github-actions]

Code Analysis

• Key observations:
  • Added support for LoongArch64 architecture (linux_loong64)
  • Updated platform mappings with appropriate file patterns for the new architecture
  • Added reference link to Node.js process.arch documentation
  • Maintained consistent naming convention with other platform entries
  • Properly extended the existing type and mapping structures

Security Review

• No security vulnerabilities detected in the changes. The modifications are purely architectural support additions with no security implications.

Optimization Suggestions

• Consider adding input validation for the new platform type to ensure robustness
• Could add unit tests for the new platform mapping to verify correct behavior
• Might want to document the new architecture support in relevant project documentation

Overall Quality: 4

The changes are well-structured and follow the existing patterns in the codebase. The only minor improvements would be additional validation and documentation, but the core implementation is solid. The changes maintain good compatibility with the existing architecture support system.