You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's currently seemingly impossible to use editorconfig style/naming configuration without listing every single option, and then keeping it up to date with future .NET updates. It seems like any undefined rule defaults to the Visual Studio settings.
It would be great if it was possible to make all stylistic/naming options to some default (defined by roslyn). For example in eslint, you can install a package that defines rules for you, and then you can extend it, and only override options that you want.
Currently if I simply open editorconfig file in Visual Studio, it automatically wants to add hundreds of lines to my file.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
It's currently seemingly impossible to use editorconfig style/naming configuration without listing every single option, and then keeping it up to date with future .NET updates. It seems like any undefined rule defaults to the Visual Studio settings.
It would be great if it was possible to make all stylistic/naming options to some default (defined by roslyn). For example in eslint, you can install a package that defines rules for you, and then you can extend it, and only override options that you want.
Currently if I simply open editorconfig file in Visual Studio, it automatically wants to add hundreds of lines to my file.
Ref: https://learn.microsoft.com/en-us/dotnet/fundamentals/code-analysis/style-rules/
Beta Was this translation helpful? Give feedback.
All reactions