dotnet/roslyn

Variable naming suggestions should prefer long form

Open

#20,927 opened on Jul 17, 2017

View on GitHub
 (10 comments) (0 reactions) (2 assignees)C# (4,257 forks)batch import
Area-IDEBughelp wanted

Repository metrics

Stars
 (20,414 stars)
PR merge metrics
 (Avg merge 6d 17h) (256 merged PRs in 30d)

Description

Version Used: 15.3 Preview 4

Steps to Reproduce:

  1. Open a file with an existing method, which also has an import to System.Threading
  2. In the method, start to declare a local variable by typing CancellationToken c

Expected Behavior:

cancellationToken is the suggested name (soft selection).

Actual Behavior:

cancellation is the suggested name (soft selection).

Contributor guide

Research direction
Examine the naming suggestion logic in Roslyn's CompletionProvider or name suggestion service to find where short form is preferred over long form. Look for rules that truncate names based on variable type.
Tech stack
csharp
Domain
developer experience
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C#
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60