dotnet/roslyn

Code lens is placed on wrong line

Open

#46,352 opened on Jul 27, 2020

View on GitHub
 (8 comments) (0 reactions) (0 assignees)C# (20,414 stars) (4,257 forks)batch import
Area-IDEBugCodeLenshelp wanted

Description

This issue has been moved from a ticket on Developer Community.

[severity:I'm somewhat annoyed. A fix would be nice] Now code lenses are placed above the name. But names are placed not always on first line of member declaration. It would be better to place code lenses on first line of declaration.

image

Original Comments

Feedback Bot on 7/26/2020, 08:01 PM:

Feedback Bot on 7/27/2020, 09:52 AM:

Original Solutions

(no solutions)

Contributor guide

Tech stack
csharp
Domain
developer experiencetooling
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Familiarity with Roslyn code baseUnderstanding of code lens rendering
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
Investigate the code lens placement logic in the Roslyn editor layer. The issue reports that code lenses appear above the member name but should appear on the first line of the declaration. Look for where the code lens position is calculated and adjust to use the start line of the member declaration. Check related source files in the EditorFeatures or LanguageServerProtocol areas.