feat: support get entry info

[bytemain]

Types

• 🎉 New Features

Background or solution

ChangeLog

Summary by CodeRabbit

• 新功能

  • 添加了 getEntryInfo 方法，以便从指定的存储库检索条目信息。
  • 新增命令 GET_ENTRY_INFO，扩展了代码服务的功能。

• 改进

  • 更新了多个服务中的 getEntryInfo 方法，以接受新的参数类型 GetEntryInfoParam，提升了数据处理的准确性和类型安全性。

• 文档

  • 修改了导入路径，简化了模块结构，增强了代码的可维护性。

[coderabbitai]

Walkthrough

Walkthrough

此次更改涉及多个文件中 getEntryInfo 方法的签名修改，主要是将参数类型从 EntryParam 更改为 GetEntryInfoParam。此外，新增了 GetEntryInfoParam 接口，并在 CommandsContribution 类中添加了 getEntryInfo 方法，更新了多个服务的导入路径，以简化模块结构。

Changes

文件路径	更改摘要
packages/code-api/src/atomgit/atomgit.service.ts packages/code-api/src/codeup/codeup.service.ts packages/code-api/src/gitee/gitee.service.ts packages/code-api/src/github/github.service.ts packages/code-api/src/gitlab/gitlab.service.ts packages/code-api/src/gitlink/gitlink.service.ts	修改 getEntryInfo 方法的参数类型，从 EntryParam 更改为 GetEntryInfoParam。
packages/code-api/src/common/types.ts	新增 GetEntryInfoParam 接口，包含 ref_name 和 path 属性，并更新 ICodeAPIService 接口中的 getEntryInfo 方法签名。
packages/code-service/src/commands.contribution.ts	在 CommandsContribution 类中新增 getEntryInfo 方法，接受 repoPath、refName 和 filePath 三个参数，并返回 Promise<EntryInfo>。
packages/code-service/src/commands.ts	在 CODE_SERVICE_COMMANDS 中新增 GET_ENTRY_INFO 命令。
packages/startup/src/code/startup.module.ts packages/startup/src/startup/startup.module.ts packages/startup/src/startup/index.tsx	更新多个导入路径，简化模块结构。
packages/startup/src/startup/web-scm.plugin.ts	修改 Deferred 类的导入路径，从 @codeblitzjs/ide-core/lib/modules/opensumi__ide-core-browser 更改为 @opensumi/ide-utils。

---

Recent review details

Configuration used: .coderabbit.yml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 132fd90 and 6ab1886.

Files selected for processing (1)

• packages/code-api/src/common/types.ts (3 hunks)

Files skipped from review as they are similar to previous changes (1)

• packages/code-api/src/common/types.ts

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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.

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.

Tip

Early access features: enabled

We are currently testing the following features in early access:

• Anthropic claude-3-5-sonnet for code reviews: Anthropic claims that the new Claude model has stronger code understanding and code generation capabilities than their previous models. Note: Our default code review model was also updated late last week. Please compare the quality of the reviews between the two models by toggling the early access feature.

Note:

• You can enable or disable early access features from the CodeRabbit UI or by updating the CodeRabbit configuration file.
• Please join our Discord Community to provide feedback and report issues on the discussion post.

[bytemain]

/next

[coderabbitai]

Actionable comments posted: 3

Outside diff range, codebase verification and nitpick comments (4)

packages/code-service/src/commands.ts (1)

52-55: 新命令 GET_ENTRY_INFO 添加正确。

新添加的 GET_ENTRY_INFO 命令遵循了文件中其他命令的结构和模式，这是一个很好的做法。

不过，为了保持一致性，您可能想考虑将命令 ID 中的 "getEntryInfo" 改为全大写，以匹配其他命令的命名约定。例如：

 export const GET_ENTRY_INFO: Command = {
-  id: 'code-service.getEntryInfo',
+  id: 'code-service.GET_ENTRY_INFO',
   category: CATEGORY,
 };

这只是一个小建议，目前的实现也是可以接受的。

packages/code-api/src/common/types.ts (2)

309-312: 新接口 GetEntryInfoParam 添加得当

新添加的 GetEntryInfoParam 接口为 getEntryInfo 方法提供了更明确的参数结构，这是一个很好的改进。

建议考虑将 ref_name 属性重命名为 refName，以保持与驼峰命名约定的一致性。可以应用以下更改：

 export interface GetEntryInfoParam {
-  ref_name: string;
+  refName: string;
   path: string;
 }

---

412-412: getEntryInfo 方法签名更新合理

getEntryInfo 方法签名的更新与新添加的 GetEntryInfoParam 接口保持一致，这是一个很好的改进。

建议更新方法的文档注释，以反映参数类型的变化。可以添加如下注释：

/**
 * 获取 entry 相关信息
 * @param repo - 仓库模型
 * @param entry - 包含 refName 和 path 的入口参数
 * @returns Promise<EntryInfo>
 */
getEntryInfo(repo: IRepositoryModel, entry: GetEntryInfoParam): Promise<EntryInfo>;

packages/code-api/src/gitlink/gitlink.service.ts (1)

Line range hint 1-489: 总结：getEntryInfo 方法签名变更

此次更改主要涉及 getEntryInfo 方法的参数类型变更，从 EntryParam 更改为 GetEntryInfoParam。这个变更可能是为了提高类型的精确性和代码的可维护性。

建议：

1. 确保所有调用 getEntryInfo 方法的地方都已更新，使用新的 GetEntryInfoParam 类型。
2. 更新相关的单元测试，以确保它们使用新的参数类型。
3. 如果有API文档，请更新以反映这个变更。
4. 考虑添加一个简短的注释，解释为什么进行了这个变更，以及 GetEntryInfoParam 与 EntryParam 的区别。

这些变更看起来是朝着正确的方向迈进，有助于提高代码的类型安全性和可读性。

[opensumi]

🎉 PR Next publish successful!

0.0.20240902092222-featntry.0

[bytemain]

/next

[opensumi]

🎉 PR Next publish successful!

0.0.20240902093716-featntry.0