Front-end code code review

1. Routine inspection:

  1) Whether the code is running normally

  2) Is there any obvious error reported in the console

  3) Does the code meet the desired effect?

  4) Whether the code writing conforms to the specification

  5) Is it organized as much as possible

  6) Have you reinvented the wheel?

  7) Remove a large section of commented code (if the commented code is available, first submit the uncommented code to Git, and then submit the commented code, and then roll back later)

  8) Whether the button controls a single click

 9) Whether the timer is eliminated with the life cycle

2. Safety check:

1) Introduce other people (inside the company or other external organizations) to rely on the package, whether there is a risk of function unavailability due to unavailability and version upgrade

2) Whether all requests use https, including image links, whether to provide https protocol links for pages embedded in APP applications

3) Whether the code comment or copy contains sensitive words

3. Document check:

1) Whether there are comments that conform to the specification, whether the description of the comments is accurate, and whether the method parameters or nouns are explained

2) Whether there is a complete document for the use of third-party libraries

3) Whether the Readme document is written in a specification, and whether it has an accurate description of the project

4. Performance check

 1) Whether the page loading time exceeds 3s, what is the reason for exceeding 3s, and is there any friendly reminder?

2) Does the code significantly affect performance, logic and calculation?

3) Whether the component level is controllable

4) Whether the component communication is normal

5) Is page nesting simple?

 

Guess you like

Origin blog.csdn.net/weixin_56263402/article/details/121604526