We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Product and Version Used: VS Code 1.63.2 dotnet v6.0.101
Steps to Reproduce: Place file "editorconfig" next to the csproj file containing:
roslynator_accessibility_modifiers = implicit roslynator_enum_has_flag_style = method dotnet_analyzer_diagnostic.category-roslynator.severity = error roslynator_analyzers.enabled_by_default = true roslynator_refactorings.enabled = true
1st run of "dotnet build" throws out warnings:
CSC : warning ROS0003: Analyzer RCS1018 requires config option to be specified: roslynator_accessibility_modifiers [/home/richard/git/workitem-automation/WorkItemAutomation/WorkItemAutomation.csproj] CSC : warning ROS0003: Analyzer RCS1096 requires config option to be specified: roslynator_enum_has_flag_style [/home/richard/git/workitem-automation/WorkItemAutomation/WorkItemAutomation.csproj]
2nd run of "dotnet build" completes with no warnings.
I can produce the above warnings every time using "dotnet build --no-incremental".
Actual Behavior: Clean build on first build
Expected Behavior: Dirty build on first build
The text was updated successfully, but these errors were encountered:
9c56292
New version should be released within a few days.
Sorry, something went wrong.
@Richard-Payne Newer version of Roslynator for VS Code was just released.
No branches or pull requests
Product and Version Used:
VS Code 1.63.2
dotnet v6.0.101
Steps to Reproduce:
Place file "editorconfig" next to the csproj file containing:
1st run of "dotnet build" throws out warnings:
2nd run of "dotnet build" completes with no warnings.
I can produce the above warnings every time using "dotnet build --no-incremental".
Actual Behavior:
Clean build on first build
Expected Behavior:
Dirty build on first build
The text was updated successfully, but these errors were encountered: