Show a concise member summary when hovering over a definition

Open
#2,231 1 comment 1 reaction 0 assignees View on GitHub

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
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
go
Domain
devtools

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

enhancement
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

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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Open-MBEE/OpenSysML

All issues in Open-MBEE/OpenSysML

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.