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
There are some analyzers that conflict with csharpier, it appears that it is possible to distribute a config via a nuget package that would disable them.
Can you elaborate on why that portion of the page should disappear? It was a common question early on. I feel like it just needs to be expanded upon to call out any analyzers that may not play nice with csharpiers formatting.
I meant that the tool does this by itself, that the user is not even faced by the problem at all, and hence does not need to worry about fixing it in user code.
If the library solves the compatibility issues like the suggestion in #781, or silently disables the conflicting issues by itself without asking the user to, which I understand is what #896 does, then no need to get the user to do anything.
There are some analyzers that conflict with csharpier, it appears that it is possible to distribute a config via a nuget package that would disable them.
This talks about the approach, and calls out that .net needs more support for global analyzer configs
https://devzone.channeladam.com/notebooks/languages/dotnet/editorconfig-distribution/
This indicates that the needed support is available
dotnet/roslyn#49834
The text was updated successfully, but these errors were encountered: