JetBrains Rider 2018.1 Help

Inspection Settings

File | Settings | Editor | Inspection Settings for Windows and Linux
JetBrains Rider | Preferences | Editor | Inspection Settings for macOS
Ctrl+Alt+S settings

In this page of JetBrains Rider settings, you can specify your preferences for code inspection.

Enable code analysis Select this check box to enable design-time code inspection.
Read settings from editorconfig and project settings

If you use EditorConfig to maintain code styles for your project, you can also configure code inspections from .editorconfig files.

If this checkbox is enabled, you can configure code inspection severity levels right from .editorconfig files.
Color identifiers This option lets you enable or disable ReSharper syntax highlighting scheme.
If it is selected, language identifiers are highlighted with colors as defined in Visual Studio options: Tools | Options | Environment | Fonts and Colors.
The list of syntax identifiers provided by ReSharper is available in the Display items list, each name starting with ReSharper prefix.
Highlight color usages Enables highlighting of color definitions in code. For more information, see Color Assistance.
Highlight special characters in string literals Enables highlighting of correct and incorrect escape sequences in non-verbatim strings. For example:
Highlighting of escape sequence in strings
For more information, see Regular Expressions Assistance.
Highlight context exits This option, enabled by default, tells JetBrains Rider to highlight all places where the control flow can exit the current context. For example, for a method, it will highlight the return type of the method, all return, throw keywords, etc. when you set the caret to one of these identifiers
JetBrains Rider highlights context exits
For a loop, it will additionally highlight the loop keyword as well as all the break statements inside this loop.
Note that if a method is not entirely visible in the editor, you can invoke the Navigate To Function Exits command on the method name to trigger another kind of highlighting, which will not disappear when you your caret leaves the method name.
Enable solution-wide analysis

Enables solution-wide analysis (including solution-wide code inspections ), which is disabled by default.

Note that in large solutions, solution-wide analysis may result in some performance degradation. However, there are several ways to improve the performance of the solution-wide analysis .

Show unused non-private type members when solution-wide analysis is off When this option is enabled, JetBrains Rider will detect all unused non-private members even if the solution-wide analysis is disabled. This option does not have any significant performance impact on small- and medium-sized solutions.
However, you may want to disable it if you experience performance problems in a large solution or when working with very large source files.
Show the 'Import namespace' action using popup If this option is selected, a pop-up that suggests importing namespaces shows up if there is one or more non-imported types are detected in the file:
Namespace import quick-fix
If it is not selected, the corresponding action appears in the action list. See Importing Missing Namespaces for details.
Value analysis mode Using the value analysis, JetBrains Rider finds out which entities can hold null value and highlights possible errors with null dereference. You can choose one of the following modes.
  • Optimistic: when explicitly marked with [CanBeNull] attribute, or checked for null - JetBrains Rider assumes that only entities explicitly marked with CanBeNull or ItemCanBeNull attribute or explicitly checked for being null, can be null.
  • Pessimistic: when entity doesn't have explicit [NotNull] attribute - JetBrains Rider assumes that all nullable entities without an explicit NotNull or ItemNotNull attributes can be null.
Elements to skip

JetBrains Rider allows you to configure the list of files, file masks, and folders that should be excluded from code inspection. The excluded items are ignored by both design-time code inspection and code inspection in specific scope, but they are still indexed by JetBrains Rider, so that you can navigate to or refactor symbols excluded from code inspection.

Last modified: 20 August 2018