Code Inspections in Resource files
In Resource files, Rider 2017.1 provides 10 proprietary code inspections, any of which you can disable or change its severity level.
These code inspections help you detect code issues in design time in all open files, and additionally they allow you to find code issues in specific scope.
Configurable Resource files inspections are listed below, grouped in the following categories:
Potential Code Quality Issues (8 inspections)This category includes inspections that detect critical issues (code smells), mostly with Error or Warning level. This category also includes inspections that ensure localization assistance.
|Cannot resolve symbol||Warning|
|Duplicate resource name||Warning|
|Element is localizable||Warning|
|Format string placeholders mismatch||Warning|
|Resource is not declared in base culture||Warning|
|Resource is not overridden in specific culture||Warning|
|Resource overrides base resource with empty value||Warning|
|Resource value type is invalid||Warning|
Redundancies in Code (2 inspections)Code inspections in this category look for redundancies and dead code, which affect code readability and style, and could be safely removed. Some code redundancies cannot be fixed automatically, and quick-fixes for them are performed in the interactive mode, requiring the user input. But the majority of the redundancies can be fixed without user interaction, using either fix in scope or code cleanup.
|Redundant string type||Suggestion|
|Resource is overridden with identical value||Suggestion|