LSP type inlay hint prefers initializer type over inherited redefinition typing
Maintainers usually reply within 1 day
@devin-ai-integration is already working on this.
Since Nov 16, 2026.
- #2333 by @devin-ai-integration — open
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
Research direction
Start with inferredType in internal/workspace/model/editor_facts.go, which calls sem.ExprResultType before sem.DeclaredFeatureTypes, so the string literal's String type wins over the inherited Label typing. Reproduce with the Example package in the issue via an inlay-hint request for the whole document. Done when the hint after redefines name reflects the inherited Label typing or clearly separates the initializer type from the feature's effective type, with a test covering that case.
Written by the indexing model from the issue text.
Description
What happened, and what I expected instead
For an attribute that redefines a feature typed by a custom String subtype, the language server displays : String with tooltip inferred type ScalarValues::String. This looks like the type of the feature, but it is the type of the initializer expression and omits the more specific typing inherited through the redefinition.
Expected: the hint should account for the inherited Label typing, or clearly distinguish the initializer's expression type from the feature's effective typing. This report concerns the misleading inlay hint; it does not claim that the underlying semantic model loses the inherited typing or that assignment compatibility is necessarily validated incorrectly.
Reproduction
Open this standalone model and enable inferred-type inlay hints:
package Example {
attribute def Label :> ScalarValues::String;
attribute def Record {
attribute name : Label;
}
attribute example : Record {
attribute redefines name = "example";
}
}
The hint after redefines name is : String, rather than reflecting the inherited Label typing.
Independently reproduced against sysml-lsp v0.12.1 using a fresh stdio LSP process with -no-record-cache: send initialize, initialized, textDocument/didOpen with the model above, and textDocument/inlayHint for the whole document. No model file needs to be written.
The server published an empty diagnostic list and returned:
[
{
"position": { "line": 6, "character": 32 },
"label": ": String",
"kind": 1,
"tooltip": "inferred type ScalarValues::String",
"paddingLeft": true
}
]
Suspected cause
In internal/workspace/model/editor_facts.go, inferredType first calls sem.ExprResultType(scope, usage.Value) and only consults sem.DeclaredFeatureTypes(sym) if that returns nil. A string literal therefore supplies String before inherited/redefined feature typing can inform the hint.
Source checked at the installed extension's commit:
https://github.com/Open-MBEE/OpenSysML/blob/ddc5b7a632/internal/workspace/model/editor_facts.go
Version
Original editor observation: VS Code extension open-mbee.opensysml-sysml, version 0.12.2-nightly-20261109-ddc5b7a632.
Independent LSP reproduction:
sysml-lsp v0.12.1
Commit: b2f0e9b802a334369da94312c35cefbd8726d3bf
Build time: 2026-11-06_03:25:57
Go version: go1.27.3
Surface
Language server (sysml-lsp) / VS Code extension
Platform
Linux, VS Code Remote environment.
- 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