Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

C# local hover omits inferred types and nullable flow context

Open
  • Is something wrong?
#434 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp
Domain
developer-experience

Research direction

Start by locating the C# local hover rendering path and the four sidecar IPC regressions described in the issue. Read [HOVER-CSHARP-RENDERING] and trace how Roslyn type and flow information becomes typed display parts. Done means local hovers show fully qualified types and names with nullability matching flow state, including the listed generic, LINQ, foreach, tuple, and nullable-flow cases.

Written by the indexing model from the issue text.

Description

Hovering a C# local identifier currently renders only its name, omitting its inferred type. Four real sidecar IPC regressions reproduce this for generic objects, LINQ results, a foreach collection reference, and a named tuple.

Expected under [HOVER-CSHARP-RENDERING]: a fully qualified type and local name, with nullability matching the flow state at the hovered declaration or use. Nullable generic arguments must remain intact when the collection itself is known non-null.

The fix enables local type rendering and uses Roslyn type/flow information plus typed display parts. The original regressions are unchanged; additional IPC cases cover nullable-to-non-null flow transitions and nested nullable arguments.

Dominant language
TypeScript
Stars
168
Forks
9
Avg merge
2h 51m
Merged PRs (30d)
59

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

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 Nimblesite/SharpLsp

All issues in Nimblesite/SharpLsp

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.