File specific configuration should be respected over global configuration. #1066
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With config from .globalconfig, roslynator analyzers should respect file-specific diagnostic severities over those set globally.
For example, if we have a .globalconfig file that looks like the following:
The current behaviour is that RCS1007 will not be applied to any files.
I would expect the diagnostic to be applied to File.cs but not the rest of the files in the repository (which is consistent with how analyzers from Roslyn (and the majority of roslynator analyzers) work.