dotnet/roslyn

C# Code Style setting "Qualify field access with 'this'" still not remembered / being reset

Open

#49,473 opened on Nov 18, 2020

View on GitHub
 (8 comments) (1 reaction) (1 assignee)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

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

[severity:It's more difficult to complete my work] This issue plays for a long time now and has been posted by multiple people, but it is still not fixed in 16.8. Continuesly all of these posts get closed as duplicates and no real action seems to have been taken so far.

Please Microsoft solve it, because it leads to also incorrect .editorconfig exports, so that the settings are also not usable as a nice template for new exports.

I have added a recording of actions hopfully that these provide more info.

Main problem is after changing any other settings here, I also have to check this first setting over again.

Thank you very much.

Original Comments

Feedback Bot on 11/13/2020, 09:56 AM:

Original Solutions

(no solutions)

Contributor guide

Research direction
Investigate the settings persistence logic in the Roslyn codebase for the 'Qualify field access with this' option. Look at the EditorConfig generation and the Visual Studio options persistence to identify where the setting is not being saved correctly.
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.
Half day
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.
Mostly clear
Prerequisites
C#
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30