Front-end code automatic checking method based on centralized management mode
A centralized management and verification method technology, applied in the field of computer automatic verification, can solve problems such as low familiarity with historical codes, uncontrollable project operation, and unavailability, etc., to achieve flexible settings, improve inspection efficiency and correct repair rate Effect
- Summary
- Abstract
- Description
- Claims
- Application Information
AI Technical Summary
Problems solved by technology
Method used
Image
Examples
Embodiment 1
[0054] A kind of front-end code automatic verification method based on the centralized management mode of this embodiment, such as figure 1 as shown,
[0055] In this embodiment, through the above steps, firstly, the problem of how to trigger the automatic verification of the code when the hook script cannot be configured on the SVN server is solved. Secondly, it is not limited by the project, and the automatic code inspection rules can be flexibly configured with the project. It is not restricted by the administrator, and finally it can automatically check the front-end code, providing a solution for the scenario where the verification hook cannot be configured through normal channels (for example: no permission configuration, unified configuration).
[0056] This embodiment proposes a method and device for automatic verification of front-end codes by using +Prettier+ESLint or TSLint inspection rules based on code centralized management mode, and realizes automatic inspection...
Embodiment 2
[0061] This embodiment is further optimized on the basis of Embodiment 1. In this embodiment, the current source code management tools, whether GIT or SVN, provide corresponding client-side hooks and server-side hooks, and users can define hook scripts by themselves. , this method gives users more flexibility, but it (customized script) can only be configured on the client or server side, generally only the administrator has the configuration authority of the relevant server, the user configures the hook through the client , the hook verification can only be triggered when the client submits the code, otherwise the hook will not take effect; if there are many project team members, all members participating in the project need to configure the script uniformly and submit the code by the client to ensure code standardization and unity. This method has relatively high limitations. In this embodiment, the problem of user-defined various hook script schemes can be solved by setting ...
Embodiment 3
[0064] This embodiment is further optimized on the basis of Embodiment 1. In this embodiment, if you do not choose the code hosting method, you will go to the default configuration and enter the management of the default configuration of the front-end code. This default configuration can be GIT configuration, do not choose automation Code inspection rules, which makes our use still not to pass the automatic code inspection rules, but to find hook scripts or custom hook scripts provided by others on the Internet to use with the code automation inspection plug-ins provided by the IDE; first, search for others on the Internet Hook scripts may have security issues. If online open source hook scripts are used by criminals, new security issues may be introduced. The content implemented by the scripts may not be applicable to our own projects, which has certain limitations, and there are still user-defined Various hook script schemes have the same defect problem. Secondly, the custom ...
PUM
Login to View More Abstract
Description
Claims
Application Information
Login to View More 
