Inspections, Quick-Fixes and Context Actions
One of the strengths of Rider is code analysis. Rider comes with over 2400 code inspections that analyze your code at design time, so you can instantly see any errors, problems or potential improvements – whether in the current file or in our entire solution.
Code Analysis continuously looks at what we are doing and tries to determine what we want to achieve. Rider looks at individual statements and at your overall solution architecture. If it detects a potential issue, it will show a warning. It may show suggestions too, helping you improve code.
Inspections can hep you with many things:
- Spot errors before our application runs
- Consistent code bases using Rider code analysis
- Solution-wide analysis in Rider
- Learn best practices and language features using Rider code inspections
Learn Language Features - C#8 and Nullability
How do you stay up-to-date and learn about new language features (such as those in C#8)?
Rider comes with several Language Usage Opportunities inspections that teach new syntax and language updates. For C#8, Rider helps you migrate a code base to C#8 and adopt nullable reference types.
Plugins to Extend Rider Inspections
The Heap Allocations Viewer plugin helps highlight local object allocations, boxing, delegates and closure creations points. This will make our code perform better in terms of memory usage and throughput.
After installing the Cognitive Complexity plugin, Rider will calculate how complex a method is, using the Cognitive Complexity metric, which was proposed by G. Ann Campbell in Cognitive Complexity - A new way of measuring understandability (c) SonarSource S.A. 2016-2018, Switzerland.
Share Inspection Settings with the Team
Code inspections have their own default severity level, which is set according to potential impact of code issues that it detects. Most of the inspections have a configurable severity level, which you can change.
Severities and several other settings can be shared with your team using settings layers.