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 setting for csharp_new_line_before_open_brace is not saved correctly in Visual Studio #57937

Closed
vsfeedback opened this issue Nov 23, 2021 · 2 comments
Assignees
Labels
Area-IDE Concept-Continuous Improvement Developer Community The issue was originally reported on https://developercommunity.visualstudio.com help wanted The issue is "up for grabs" - add a comment if you are interested in working on it

Comments

@vsfeedback
Copy link

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


[severity:It's more difficult to complete my work]
When using the default editor layout in Visual Studio 2022 for a .editorconfig file, when making changes to the csharp_new_line_before_open_brace entry, regardless of what is selected, the setting value saved to the .editorconfig is always "all".

If you use the default editor in Visual Studio, after you make changes to the csharp_new_line_before_open_brace option, the file is not marked as dirty to show changes are not saved. If you close the editor and re-launch it, any changes made to those settings are gone.

If you edit the .editorconfig file manually using any text editor in Visual Studio, you can manually change it to none or all and it works. The code formatting for braces is applied correctly. I don't know what other values are permissible for csharp_new_line_before_open_brace, so that's why I use the default editor in Visual Studio and simply select/unselect the options from the list provided.

I was expecting Visual Studio to write & save the correct value for the csharp_new_line_before_open_brace setting based on the selections made from the list provided in the default editor.

Jason


Original Comments

Feedback Bot on 11/18/2021, 07:09 PM:

We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.

Feedback Bot on 11/19/2021, 09:42 AM:

Thank you for sharing your feedback! Our teams prioritize action on product issues with broad customer impact. See details at: https://docs.microsoft.com/en-us/visualstudio/ide/report-a-problem?view=vs-2019#faq. In case you need answers to common questions or need assisted support, be sure to use https://visualstudio.microsoft.com/vs/support/. We’ll keep you posted on any updates to this feedback.


Original Solutions

(no solutions)

@dotnet-issue-labeler dotnet-issue-labeler bot added Area-IDE untriaged Issues and PRs which have not yet been triaged by a lead labels Nov 23, 2021
@Youssef1313
Copy link
Member

Possibly it's the same as the 7th point in #53171.

@jinujoseph jinujoseph added Concept-Continuous Improvement Developer Community The issue was originally reported on https://developercommunity.visualstudio.com help wanted The issue is "up for grabs" - add a comment if you are interested in working on it and removed untriaged Issues and PRs which have not yet been triaged by a lead labels Dec 1, 2021
@jinujoseph jinujoseph added this to the 17.1 milestone Dec 1, 2021
@jmarolf jmarolf modified the milestones: 17.1, 17.2 Jan 11, 2022
@jmarolf
Copy link
Contributor

jmarolf commented Mar 18, 2022

duplicate of #54556

@jmarolf jmarolf closed this as completed Mar 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-IDE Concept-Continuous Improvement Developer Community The issue was originally reported on https://developercommunity.visualstudio.com help wanted The issue is "up for grabs" - add a comment if you are interested in working on it
Projects
None yet
Development

No branches or pull requests

4 participants