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 regressions in Visual Studio v16.10 #54526

Closed
vsfeedback opened this issue Jul 1, 2021 · 2 comments
Closed

.editorconfig regressions in Visual Studio v16.10 #54526

vsfeedback opened this issue Jul 1, 2021 · 2 comments
Assignees
Labels
Area-Analyzers Bug Developer Community The issue was originally reported on https://developercommunity.visualstudio.com

Comments

@vsfeedback
Copy link

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


[severity:It bothers me. A fix would be nice] [regression] [worked-in:16.9.x]

  1. Configure severity for analyzers from editor context menu doesn't work.

  2. No convenient facility to view .editorconfig in plain text (.csproj files are opened in text mode by default, GUI editor is opened only when Properties is selected in Solution Explorer context menu).

  3. New GUI editor edits .editorconfig with formatting which differs from "Configure severity for analyzers" item (when it work).

  4. No ability to select "none" severity for analyzers rules in GUI editor.


Original Comments

Feedback Bot on 6/16/2021, 01:16 AM:

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.

Maxim Marinchenko on 6/16/2021, 01:44 AM:

I can see that some of these issues are already covered on GitHub.

1 may be related to 7 at #53171

2 is covered at #53120

3 covered at #52720 and #53833

I didn’t find any github issue for point 4.

Feedback Bot on 6/16/2021, 09:58 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-Analyzers untriaged Issues and PRs which have not yet been triaged by a lead labels Jul 1, 2021
@jmarolf jmarolf self-assigned this Jul 1, 2021
@jinujoseph jinujoseph added Bug and removed untriaged Issues and PRs which have not yet been triaged by a lead labels Jul 9, 2021
@jinujoseph jinujoseph added this to the 17.0 milestone Jul 9, 2021
@jinujoseph jinujoseph added the Developer Community The issue was originally reported on https://developercommunity.visualstudio.com label Jul 9, 2021
@jmarolf jmarolf modified the milestones: 17.0, 17.1 Oct 6, 2021
@jmarolf jmarolf modified the milestones: 17.1, 17.2 Jan 10, 2022
@jmarolf
Copy link
Contributor

jmarolf commented Mar 18, 2022

these are all being tracked in separate issues

@jmarolf jmarolf closed this as completed Mar 18, 2022
@majorregal
Copy link

Is this a joke? The github issue says it's continued in the Developer Community ticket and the ticket refers back to this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Analyzers Bug Developer Community The issue was originally reported on https://developercommunity.visualstudio.com
Projects
None yet
Development

No branches or pull requests

4 participants