Evaluating code review findings

You need to evaluate findings in the Code Review view and decide that a finding is a problem you want to fix. It is recommended that you deal with the highest severity problems first, especially those that contain Quick Fix and Quick Fix All icons.

Code refactoring should be an interactive process. Using automatic refactoring can eliminate obvious problems, which helps to clean up the code overall before further actions are planned.

Evaluate each finding and decide what action, if any, you want to take to modify the code.

Working with code review findings
For each code review finding, you can review details, open the source code editor, and get more information.

Working with the Code Review view
You can sort, filter, and search for specific rule findings in the Code Review view.

Ignoring a rule finding
In the list of code review findings, you can ignore a finding. If you ignore the finding it gets marked with an X. Visually, this helps you distinguish between findings that you want to evaluate and those that you want to ignore.

 

Parent topic

Fixing a problem found in code review