Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Add editor information to Complete

未关闭
#449 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 2 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
冷清
技术栈
clojure

调研方向

Start by reading follow-up issue #448 to understand the existing scope. Compare the listed editor context—recent edits, open files, the active buffer, type definitions, and related files—and decide what information and size controls should be included. Done means the agreed editor information is available to Complete; this issue does not specify files or tests.

由索引模型根据 Issue 内容生成。

描述

To upvote this issue, give it a thumbs up. See this list for the most upvoted issues.

Follow up #448.

Add editor information including but not limited to:

  • recent edits/diff histories
    • Found in both Cursor & Zed. Zed serializes to unified diff when injecting in the prompt.
  • open files
    • Zed & Cursor
  • current active file/buffer
    • Zed & Cursor
  • type definitions
  • related files
    • Zed ranks files by how many definitions/imports are pointing to a file
    • Cursor had a key for this but not too much info on it. It looks like they collect a whole lot client side but who knows what happens server side.

One thing to note: Most of these are not raw outputs. Zed dedupes, strips, drops or truncates "related files" if they are too big, etc. There seems to be a balance of information vs token size. If this feature moves forward, we may want to discuss ways to allow users to "tune" the aggressiveness.

主要语言
Clojure
星标
1k
派生
82
平均合并
3 天 39 分钟
30 天内合并 PR
15

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

editor-code-assistant/eca 的其他 Issue

查看 editor-code-assistant/eca 的全部 Issue

相似的 Issue

更多 Clojure Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。