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

Add preference to configure GenericEditorContentAssistant.contextInformationPopupOrientation

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
53/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
冷清
技术栈
java
领域
desktop

调研方向

Start with GenericEditorContentAssistant.java, especially the line linked in the issue where the context-information popup orientation is hard-coded, and inspect how ContentAssistant exposes that option. Then look for the generic editor’s existing preference definitions and tests; the issue does not name them. Done means users can choose the context-information orientation and the selected setting is applied.

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

描述

enhancement

While working with the generic text editor, I noticed that the context information is placed below the cursor, which causes any additional shells, such as the proposal list or the additional information popup to cover the context information.

Example:
Initially only the context information is shown:
Image
If the user triggers the proposals or starts typing, the context info is barely visible:
Image

ContentAssistant already has the option to show the context above the cursor (which is the default) , but GenericEditorContentAssistant hard-codes this to be rendered below:
https://github.com/eclipse-platform/eclipse.platform.ui/blob/61565e63f53ce84d1e983d6f2ab1cc399207d1cb/bundles/org.eclipse.ui.genericeditor/src/org/eclipse/ui/internal/genericeditor/GenericEditorContentAssistant.java#L98

I propose to add a preference so the user can decide where the context info is shown.

Moving it to the top looks like this:
Image

For comparison, VS Code also displays this information at the top, if there is enough space:
Image
If there isn't enough space, it also displays the info below the cursor where it also covered by any additional popups.

Thoughts?

主要语言
Java
星标
124
派生
269
平均合并
2 天 7 小时
30 天内合并 PR
68

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

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

eclipse-platform/eclipse.platform.ui 的其他 Issue

查看 eclipse-platform/eclipse.platform.ui 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

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