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# (20,414 stars) (4,257 forks)batch import
Area-IDEBughelp wanted

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

Tech stack
csharp
Domain
developer experience
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
C# knowledgeRoslyn codebase familiarity
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
The issue is assigned and has 10 comments. Investigate the naming suggestion implementation in the Roslyn codebase, likely in the IDE or completion features. Review the comments for any additional context or attempted approaches.
Variable naming suggestions should prefer long form · dotnet/roslyn#20927 | Good First Issue