Description of what has been done in this request. On the platform, before sharing a link – that usually helps with some comments, console.logs, bad formatting and other leftovers. Developer (that requests the code) has actually checked the code himself.
There are a few things I really like in this process, and I consider as highly useful. They will help you stay less angry, as the person that provides React development services and prepares the code review will have specific steps to follow before sending the code to you. If you are a reviewer, and you do the React code review often – you should set up some rules first. We should do a code review to share knowledge and make the other developer more confident about the code – if you will accept the PR – he will feel like he did a good job. Show other developers what changes have been made to the project.Ĭatching bugs seems to be the most desired goal BUT let’s be honest – it happens occasionally and should be threatened as a bonus.What is the goal of the React code review? I will try to point out what you should be looking for during this process and how to write good comments instead of just “change A to B”.īut let’s start with the simple question. It also helps other teammates to be up to date as they see all code updates. If not – it’s a process that helps keep good code in a project, eliminate potential bugs or just check from higher-skilled React developers. If you have some experience as a React developer, you are probably familiar with the React code review process.
0 kommentar(er)
