UPDATE November 7, 2019: The new Code Review system is enabled by default!
In this blogpost, we are going to show you more about what is new in the Code Review system and how you can take advantage of it.
We first shared with you an overview of the upcoming new Code Review system.
And then, we showed you the first improvements in the Code Review.
Let's see the latest in the Code Review.
plastic --codereview
Outline support
(Release 8.0.16.3476)
When a comment was placed in a line that was collapsed due to outlining, it was rendered in a wrong line. Now the comment is hidden when the line is collapsed and visible when the line is not collapsed.
We also improved the comments navigation. When navigating to a comment, we always ensure that the line that contains the comment is always expanded. Otherwise, in some scenarios a comment could be not visible.
In the following example, you can see how the code are collapsed. And when you double-click the comment, the code expands to show you the line that contains this comment:
Display questions
(Release 8.0.16.3476)
The new Code Review system now displays questions in the comments list. The reviewer asks a question when they need an answer, but no change is required initially:
Review branches changeset by changeset
(Release 8.0.16.3533)
The new Code Review system now allows you to review a branch, changeset by changeset. Just go to the Branch Explorer, right-click a branch and select New code review for this branch:
When the developers checkin often, keeping reviewers in mind, it's helpful to review the branch walking through each changeset.
So, we added a new tab that allows you to review a branch, stepping through changeset by changeset:
While reviewing a branch, you can switch between the modes Review changeset by changeset and Review entire branch at any time, adding comments in either of them. Each comment will be displayed in the mode it was added.
Why is so important reviewing changeset by changeset? When a developer follows the rule of running checkins with the reviewer in mind, then every single checkin helps the reviewer following the developer's thoughts and steps to really understand what happened.
Now, the reviewer can review the branch by diffing changeset by changeset. This way, the reviewer will follow the pre-recorded explanation the author made to clarify each step of the task.
No comments:
Post a Comment