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

Use Roslyn's native .editorconfig support #1657

Closed
JoeRobich opened this issue Nov 22, 2019 · 6 comments · Fixed by #1771
Closed

Use Roslyn's native .editorconfig support #1657

JoeRobich opened this issue Nov 22, 2019 · 6 comments · Fixed by #1771

Comments

@JoeRobich
Copy link
Member

EditorConfigDocumentOptionsProvider pulls options from Workspace.AnalyzerDocuments. Need to register this OptionsProvider with the OptionService during Workspace initialization.

@coder2000
Copy link

coder2000 commented Mar 30, 2020

Is this supported yet?

@filipw
Copy link
Member

filipw commented Mar 30, 2020

not yet

@coder2000
Copy link

Any timeline for implementation? It gets kind of annoying having 800 warnings that are not supposed to be there.

@filipw
Copy link
Member

filipw commented Mar 30, 2020

Any timeline for implementation?

no timeline, hopefully soon

@333fred
Copy link
Contributor

333fred commented Apr 10, 2020

Also looking for this, I'm assuming my issues with analyzer settings not being respected are due to this.

@filipw
Copy link
Member

filipw commented Apr 10, 2020

yes correct, when we implemented editorconfig there was no native Roslyn support yet so we had to use the VS conventions package like dotnet format did at the time

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.

4 participants