Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EditorConfig UI: Change how the .editorconfig file is saved #53833

Closed
BhaaLseN opened this issue Jun 2, 2021 · 0 comments · Fixed by #54601
Closed

EditorConfig UI: Change how the .editorconfig file is saved #53833

BhaaLseN opened this issue Jun 2, 2021 · 0 comments · Fixed by #54601

Comments

@BhaaLseN
Copy link

BhaaLseN commented Jun 2, 2021

I used the Roslyn .editorconfig as a base, and generally liked how there are spaces around the equals sign:

setting1 = value
setting2 = value

However, updating it with the EditorConfig UI only puts the space in front:

 setting1 = value
 setting2 = value
+setting3 =value

...and that looks really ugly, especially when it now causes the file to use mixed conventions.

It would be nice if it would either be detected from the existing file, or a styling option somewhere (perhaps inside that Editor, perhaps inside Tools > Options, Text Editor, perhaps somewhere else) to pick the preferred formatting. Or even more Meta, EditorConfig specific keys inside .editorconfig :D

Originally posted by @BhaaLseN in #53791

@dotnet-issue-labeler dotnet-issue-labeler bot added Area-IDE untriaged Issues and PRs which have not yet been triaged by a lead labels Jun 2, 2021
@jmarolf jmarolf self-assigned this Jun 2, 2021
@jmarolf jmarolf added this to the 16.11 milestone Jun 2, 2021
@jinujoseph jinujoseph added Concept-Continuous Improvement and removed untriaged Issues and PRs which have not yet been triaged by a lead labels Jun 2, 2021
@jinujoseph jinujoseph modified the milestones: 16.11, 17.0 Jul 16, 2021
@jmarolf jmarolf modified the milestones: 17.0, 17.1 Oct 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants