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
I think we should revert #1581 since it still results in various problems like #1684 and #1720. We originally did this and ran into problems where users did not realize manual steps were needed after applying the code fix in order for stylecop.json settings to take effect. This can be resolved by adding a comment at the top of the generated stylecop.json file:
// ACTION REQUIRED: This file was automatically added to your project, but it// will not take effect until additional steps are taken to enable it. See the// following page for additional information://// https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/EnableConfiguration.md
📝 The page mentioned above should only contain information about enabling stylecop.json. A good starting point would be the content which was removed from Configuration.md in #1636.
📝 This is not technically valid JSON syntax, but it is supported by both the Visual Studio JSON editor and Newtonsoft.Json library we use for reading the file.
The text was updated successfully, but these errors were encountered:
I think we should revert #1581 since it still results in various problems like #1684 and #1720. We originally did this and ran into problems where users did not realize manual steps were needed after applying the code fix in order for stylecop.json settings to take effect. This can be resolved by adding a comment at the top of the generated stylecop.json file:
📝 The page mentioned above should only contain information about enabling stylecop.json. A good starting point would be the content which was removed from Configuration.md in #1636.
📝 This is not technically valid JSON syntax, but it is supported by both the Visual Studio JSON editor and Newtonsoft.Json library we use for reading the file.
The text was updated successfully, but these errors were encountered: