dotnet/roslyn

Suggestion: improve error message when missing a semicolon in immediate window variable creation

Open

#46,736 opened on Aug 12, 2020

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

Repository metrics

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

Description

I am creating this issue on behalf of @WebFreak001 from https://github.com/OmniSharp/omnisharp-vscode/issues/3940

Version Used: Visual Studio 16.8 preview 2 [30410.220.master]

Steps to Reproduce:

  1. Create a new hello world application
  2. Open the immediate window (or the debug console in VS Code)
  3. Evaluate var x = 10 (note the missing semicolon)

Expected Behavior: An error message that might lead one to understand that variable creation statements require a semicolon

Actual Behavior: error CS0726: 'x' is not a valid format specifier

Contributor guide

Research direction
Search for error code CS0726 in the Roslyn source code, identify the context where it is emitted when missing a semicolon in the immediate window, and propose a new error message suggesting to add a semicolon.
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.
2
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.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75