Code Inspections in Resource files
In Resource files, JetBrains Rider 2024.2 provides 17 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 by their categories.
Grammar Issues (4 inspections)
Inspections in this category report grammar issues in string literals and documentation comments.
Inspection | |
|---|---|
Grammar error in comment | |
Grammar error in markup attribute value | |
Grammar error in markup text | |
Grammar error in string literal |
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.
Inspection | |
|---|---|
| |
| |
| |
Format string placeholders mismatch | |
Resource is not declared in base culture | |
Resource is not overridden in specific culture | |
Resource overrides base resource with empty value | |
Resource value type is invalid |
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.
Inspection | |
|---|---|
| |
Resource is overridden with identical value |
Spelling Issues (3 inspections)
These inspections detect typos in various contexts.
Inspection | |
|---|---|
| |
Typo in markup attribute value | |
|