Show a concise member summary when hovering over a definition
Maintainers usually reply within 1 day
@devin-ai-integration is already working on this.
Since Nov 16, 2026.
- #2334 by @devin-ai-integration — open
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
The payload names no files, tests or entry points, so begin by finding where the existing hover response is built in the language-server code and how model element definitions expose their owned features. The request is open-ended: it leaves open whether to add a configurable limit, an expandable summary, and inherited members, so confirm those choices with maintainers first. Done means a hover on a definition or reference lists each member's kind, name, type and multiplicity, truncated past the chosen limit, and the same behaviour works in notebook cells.
Written by the indexing model from the issue text.
Description
Feature request
When hovering over a model element definition or a reference to it, show a concise summary of its owned features alongside its signature and documentation. This would help model authors discover what is available when developing a usage without navigating away from their current location.
For example, the summary could show each member’s kind, name, type, and multiplicity where applicable. Keep large hovers manageable with a configurable limit or an expandable summary, and consider an option to include inherited features with their origin clearly distinguished. The summary should work both in model files and notebook cells.
Related precedents
- rust-analyzer displays struct fields in hovers and provides a field display limit.
- TypeScript supports expandable hover information.
This request concerns additional hover information, not the incorrect documentation issue #2196.
- Dominant language
- Go
- Stars
- 59
- Forks
- 20
- Avg merge
- 10h 23m
- Merged PRs (30d)
- 897
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Open-MBEE/OpenSysML
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
A model's parse is still paid cold in every process; the library record cache does not cover itOpen
Difficulty 5/5 Over a week Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 28/100
Maintainers usually reply within 1 day
All issues in Open-MBEE/OpenSysML
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
krakenhavoc/cmd_and_ctrl#5853 ·
Maintainers usually reply within 1 day
-
flaky test: TestTRTAsyncPrefillFailures/transport reads the token load before prefillDone has released itPossibly taken @Jackmeson1 claimed this today. Openarea/cicd area/gateway kind/misc
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
vllm-project/aibrix#3488 · 2 comments ·
Maintainers usually reply within 1 day
-
Type: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
projectdiscovery/httpx#2735 ·
Maintainers usually reply within 1 day
-
NuGet registry builds every URL from ROOT_URL, ignoring the host the client usedPossibly taken @gritse claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day