dotnet/roslyn

Editorconfig naming convention for tuple element names

Open

#38,705 opened on Sep 16, 2019

View on GitHub
 (5 comments) (6 reactions) (0 assignees)C# (4,257 forks)batch import
Area-IDEConcept-Continuous Improvementhelp wanted

Repository metrics

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

Description

Now that we have settled on the guidance of pascal case for tuple element names (https://github.com/dotnet/corefx/pull/35595, https://github.com/dotnet/corefx/issues/33553), it would be nice to have a tuple_element symbol kind to which a naming convention can be applied.

https://docs.microsoft.com/en-us/visualstudio/ide/editorconfig-naming-conventions?view=vs-2019#kinds-of-symbols

Contributor guide

Research direction
Study existing naming convention symbol kinds in the Roslyn codebase, then add a new tuple element symbol kind following the pattern of existing kinds like method, property, etc.
Tech stack
csharp
Domain
compilers
Issue type
Feature
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-2 days
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.
Clear
Prerequisites
C#Editorconfig understanding
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40