CN114217828A - Configuration method, system, device and storage medium of front-end universal code standard library - Google Patents
Configuration method, system, device and storage medium of front-end universal code standard library Download PDFInfo
- Publication number
- CN114217828A CN114217828A CN202111581590.8A CN202111581590A CN114217828A CN 114217828 A CN114217828 A CN 114217828A CN 202111581590 A CN202111581590 A CN 202111581590A CN 114217828 A CN114217828 A CN 114217828A
- Authority
- CN
- China
- Prior art keywords
- code specification
- file
- configuration
- universal
- module
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 27
- 238000011161 development Methods 0.000 claims abstract description 53
- 238000007689 inspection Methods 0.000 claims abstract description 12
- 230000004048 modification Effects 0.000 description 8
- 238000012986 modification Methods 0.000 description 8
- 230000001419 dependent effect Effects 0.000 description 6
- 238000010586 diagram Methods 0.000 description 6
- 230000008901 benefit Effects 0.000 description 3
- 230000003993 interaction Effects 0.000 description 3
- 238000004590 computer program Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 238000012360 testing method Methods 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Abstract
The invention provides a front-end universal code specification library configuration method based on Web, which comprises the following steps: acquiring a code specification configuration instruction of a user interface; determining a dependency package according to a development framework, marking the dependency package, and generating an initialization code specification file based on the marked dependency package; formulating a universal code specification file based on the initialization code specification file; performing iterative updating based on the universal code specification file; and installing a scaffold based on the selected frame, realizing the initialization configuration of the universal code specification file based on the scaffold, and performing project inspection. The development efficiency and the development quality are improved, and the codes are effectively managed.
Description
Technical Field
The invention relates to the technical field of computer software, in particular to a front-end universal code standard library configuration method and system based on Web.
Background
In the current Web front-end project development, because editors for members are not uniform and the code styles are different, code conflict can be caused due to inconsistent code formats when team collaboratively submits codes. At present, in order to specify codes, the project group mostly adopts the existing mature specifications in the industry, such as the stylelint-config-standard and stylelint-order code specifications of the css language, the eslin-recommended code specification of the JavaScript language, and the like. However, these open source code specifications cannot meet the business requirements of the development team, the expandability is poor, and the code specifications are independent of each other, and if the code specifications need to be initialized or the version of the code specifications needs to be upgraded, the development team must manually operate and modify the code specification document step by step, which not only increases the project development cost, but also has the problem of unreliability. And different development teams or different development members have different code specifications due to different development tool differences and different code styles, so that code conflict is easy to occur during project joint test, a large amount of time and energy are consumed to renew the code specifications, the development efficiency and the development quality are reduced, and the codes cannot be effectively managed.
Disclosure of Invention
The invention aims to provide a front-end universal code specification library configuration method and a front-end universal code specification library configuration system based on Web. So as to solve the technical problems existing in the background technology.
In order to achieve the purpose, the invention adopts the following technical scheme:
a front-end universal code specification library configuration method based on Web comprises the following steps:
acquiring a code specification configuration instruction of a user interface;
determining a dependency package according to a development framework, marking the dependency package, and generating an initialization code specification file based on the marked dependency package;
formulating a universal code specification file based on the initialization code specification file;
performing iterative updating based on the universal code specification file;
and installing a scaffold based on the selected frame, realizing the initialization configuration of the universal code specification file based on the scaffold, and performing project inspection.
In some embodiments, the code specification configuration instructions include at least one of:
a compiler, a development framework, a dependency package required by the development framework.
In some embodiments, said iteratively updating based on said common code specification file comprises:
when the universal code specification needs to be updated, operating and updating a command line of a specified version;
analyzing the called new version code specification based on the scaffold;
confirming whether the current universal code specification file is a version needing to be updated or not;
if yes, giving a relevant prompt;
otherwise, the old rc.js file is checked and removed, and the latest generic code specification file is installed and the corresponding rc.js file is updated.
In some embodiments, the item check comprises:
checking whether the item has a code specification old package and redundancy dependence in the item;
examine and remove the old rc.js file;
introducing a called universal code specification, and adding a corresponding rc file in a project;
json files of the items are added with the configuration of the dependency contained in the code specification;
and displaying the initialization progress of the universal code specification applied to the project based on the scaffold.
Meanwhile, the invention also discloses a front-end universal code specification library configuration system based on Web, which comprises the following steps:
the acquisition module is used for acquiring a code specification configuration instruction of the user interface;
the generation module is used for determining a dependency package according to a development framework, marking the dependency package and generating an initialization code specification file based on the marked dependency package;
the formulating module is used for formulating a universal code specification file based on the initialization code specification file;
the updating module is used for carrying out iterative updating based on the general code specification file;
and the inspection module is used for installing the scaffold based on the selected framework, realizing the initialization configuration of the universal code specification file based on the scaffold and carrying out project inspection.
In some embodiments, the update module is further to:
when the universal code specification needs to be updated, operating and updating a command line of a specified version;
analyzing the called new version code specification based on the scaffold;
confirming whether the current universal code specification file is a version needing to be updated or not;
if yes, giving a relevant prompt;
otherwise, the old rc.js file is checked and removed, and the latest generic code specification file is installed and the corresponding rc.js file is updated.
In some embodiments, the inspection module is further to:
checking whether the item has a code specification old package and redundancy dependence in the item;
examine and remove the old rc.js file;
introducing a called universal code specification, and adding a corresponding rc file in a project;
json files of the items are added with the configuration of the dependency contained in the code specification;
and displaying the initialization progress of the universal code specification applied to the project based on the scaffold.
Meanwhile, the invention also discloses a front-end universal code specification library configuration device based on Web, which comprises a processor and a memory; the memory is configured to store instructions that, when executed by the processor, cause the apparatus to implement any of the above-described Web-based front-end common code specification library configuration methods.
Meanwhile, the invention also discloses a computer-readable storage medium, wherein the storage medium stores computer instructions, and after the computer reads the computer instructions in the storage medium, the computer runs any one of the front-end universal code specification library configuration methods based on Web.
Advantageous effects
Compared with the prior art, the invention has the following remarkable advantages:
through the scheme of the invention, developers can quickly define the universal code specification suitable for the project through the configuration method and the configuration device, the code specification of the whole project is ensured to be consistent, and the problems that the whole project cannot be unified and specified due to different code specifications among different project groups or different developers, and the later code test maintenance needs to spend a great deal of effort on updating and modifying are solved. The configuration method also provides a lightweight command line, so that the project can be conveniently added with specifications or upgraded with specifications, and a code specification library of the device can store code configuration rule files of different iteration versions, thereby improving the development efficiency and the development quality and effectively managing the codes.
Drawings
FIG. 1 is a schematic diagram of a Web-based front-end generic code specification library configuration system according to the present embodiment;
fig. 2 is a schematic flow chart of a method for configuring a front-end universal code specification library based on Web according to this embodiment;
FIG. 3 is a schematic structural diagram of a Web-based front-end generic code specification library apparatus according to the present embodiment;
FIG. 4 is a flowchart illustrating a method for configuring a front-end generic code specification library based on Web according to this embodiment;
FIG. 5 is a diagram illustrating the application of the configuration method according to the present embodiment to a development project;
fig. 6 is a schematic configuration diagram of a front-end generic code specification library apparatus device based on the Web according to the present embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
On the contrary, this application is intended to cover any alternatives, modifications, equivalents, and alternatives that may be included within the spirit and scope of the application as defined by the appended claims. Furthermore, in the following detailed description of the present application, certain specific details are set forth in order to provide a better understanding of the present application. It will be apparent to one skilled in the art that the present application may be practiced without these specific details.
A method for configuring a front-end generic code specification library based on Web according to an embodiment of the present application will be described in detail with reference to fig. 1 to 6. It is to be noted that the following examples are only for explaining the present application and do not constitute a limitation to the present application.
Example 1
As shown in fig. 1, a Web-based front-end generic code specification library configuration system 100 includes:
an obtaining module 101, configured to obtain a code specification configuration instruction of a user interface; in some embodiments, the code specification configuration instructions include at least one of: a compiler, a development framework, a dependency package required by the development framework.
The generation module 102 is configured to determine a dependency package according to a development framework, mark the dependency package, and generate an initialization code specification file based on the marked dependency package;
the formulating module 103 is used for formulating a universal code specification file based on the initialization code specification file;
and the updating module 104 is used for performing iterative updating based on the general code specification file.
In some embodiments, the update module is further to:
when the universal code specification needs to be updated, operating and updating a command line of a specified version;
analyzing the called new version code specification based on the scaffold;
confirming whether the current universal code specification file is a version needing to be updated or not;
if yes, giving a relevant prompt;
otherwise, the old rc.js file is checked and removed, and the latest generic code specification file is installed and the corresponding rc.js file is updated.
And the inspection module 105 is used for installing a scaffold based on the selected frame, realizing the initialization configuration of the universal code specification file based on the scaffold and carrying out project inspection.
In some embodiments, the inspection module is further to:
checking whether the item has a code specification old package and redundancy dependence in the item;
examine and remove the old rc.js file;
introducing a called universal code specification, and adding a corresponding rc file in a project;
json files of the items are added with the configuration of the dependency contained in the code specification;
and displaying the initialization progress of the universal code specification applied to the project based on the scaffold.
It can be seen that the technical solution in this embodiment is mainly that a developer obtains a code specification configuration command at the obtaining module 101, selects a code specification dependency package required by a development framework, and invokes a target code corresponding to the dependency package to generate an initial code specification component configuration file. Developers can perform custom modification and addition on the initialization code specification file in a custom module to obtain a universal code specification suitable for the whole development team. All developers participating in the project can call the general code specification of the project configuration in the device through the interface, use the simple command provided by the script to drive the configuration file to be the code specification of the project, effectively solve the problem that the code specifications among different project groups are inconsistent in development, update and upgrade the code specifications in an open source mode, and improve the development efficiency by using a lightweight command line to facilitate the project addition specification and the upgrade specification
It should be noted that the above description of the system and its modules is for convenience only and should not limit the present disclosure to the illustrated embodiments. It will be appreciated by those skilled in the art that, given the teachings of the present system, any combination of modules or sub-system configurations may be used to connect to other modules without departing from such teachings. In some embodiments, the acquiring module 101, the generating module 102, the formulating module 103, the updating module 104, and the checking module 105 disclosed in fig. 1 may be different modules in a system, or may be a module that implements the functions of two or more of the above modules. For example, each module may share one memory module, and each module may have its own memory module. Such variations are within the scope of the present disclosure.
As shown in fig. 2, a method for configuring a front-end universal code specification library based on Web includes:
For example, a user interface code specification configuration instruction input by a developer is received, and the code specification configuration instruction comprises a compiler and a development framework used by the developer and a dependency package required by the development framework.
And step 220, determining a dependency package according to the development framework, marking the dependency package, and generating an initialization code specification file based on the marked dependency package.
For example, a corresponding related pre-dependency package is selected according to a development framework, the dependency package module contains various existing open-source specification dependency packages, the corresponding configuration module can identify the dependency package selected by a developer, mark each dependency package, and package the marked dependency packages to generate an initialized code specification file.
For example, in the custom specification module, the initialization code specification configuration file is further modified to a common code specification file required by the project.
And 240, performing iterative updating based on the universal code specification file.
In some embodiments, said iteratively updating based on said common code specification file comprises:
when the universal code specification needs to be updated, operating and updating a command line of a specified version; analyzing the called new version code specification based on the scaffold; confirming whether the current universal code specification file is a version needing to be updated or not; if yes, giving a relevant prompt; otherwise, the old rc.js file is checked and removed, and the latest generic code specification file is installed and the corresponding rc.js file is updated.
For example, the generic code specification configuration file is uploaded to the storage module for iterative updating in an open source manner. When the project needs to update the universal code specification, a command line for updating the specified version is operated, the scaffold analyzes the called new version code specification firstly, whether the current code specification is the version needing to be updated is checked, if the current code specification is the version needing to be updated, a relevant prompt is given, if the current code specification is not the version needing to be updated, an old rc.js file is checked and removed, the latest code specification is installed, and the corresponding rc file is updated.
And step 250, installing a scaffold based on the selected frame, realizing the initialization configuration of the universal code specification file based on the scaffold, and performing project inspection.
In some embodiments, the item check comprises:
checking whether the item has a code specification old package and redundancy dependence in the item; examine and remove the old rc.js file; introducing a called universal code specification, and adding a corresponding rc file in a project; json files of the items are added with the configuration of the dependency contained in the code specification; and displaying the initialization progress of the universal code specification applied to the project based on the scaffold.
For example, the interface module is called into the project, a scaffold is installed under a selected development frame, the scaffold is used for identifying a code specification file and starting to perform initialization configuration of the code specification, whether a code specification old package and redundant dependence in the project exist in the project are checked, an old rc.js file is checked and removed, the called general code specification is further introduced, corresponding rc files such as eslinetrc.js and stylelinintrc.js are added into the project, the configuration of dependence included in the code specification is added into a package.json file of the project, and the scaffold can display the initialization progress of the application of the general code specification to the project.
Fig. 3 is a structural diagram of a front-end generic code specification library device based on Web according to this embodiment, which includes a dependency package module, a code specification configuration module, a custom specification module, a call module, a storage (iterative update) module, and a command receiving module.
In some embodiments, the dependency package module is an open source dependency package for storing existing development frameworks, and the open source dependency package may include, for example, stylelint-config-standard and stylelint-order code specifications of css language, esint-recommended code specification of JavaScript language, and so on.
In some embodiments, the code specification configuration module is used for configuring the dependency package selected by the developer into an initialization code specification configuration file; the self-defined specification module is used for further modifying the initialization code specification in the module according to requirements by developers after the initialization code specification is configured, so as to obtain a general code specification configuration file suitable for the whole project.
In some embodiments, the calling module refers to calling a common code specification configuration file into the catalog file src of the project for specifying the project code.
In some embodiments, the storage (iterative update) module stores each version of the common code specification configuration file, and the iterative update can be performed in an open source manner; the instruction receiving module is used for receiving various instruction parameters of a developer, such as a configuration instruction, a modification instruction, an uploading instruction, an updating instruction and the like.
It should be noted that the above description of the system and its modules is for convenience only and should not limit the present disclosure to the illustrated embodiments. It will be appreciated by those skilled in the art that, given the teachings of the present system, any combination of modules or sub-system configurations may be used to connect to other modules without departing from such teachings. In some embodiments, the package-dependent module, the code specification configuration module, the custom specification module, the calling module, the storage (iterative update) module, and the instruction receiving module disclosed in fig. 3 may be different modules in a system, or may be a module that implements the functions of two or more of the above modules. For example, each module may share one memory module, and each module may have its own memory module. Such variations are within the scope of the present disclosure.
Fig. 4 is a schematic flow chart of the front-end generic code specification configuration method related in this embodiment, and the present invention can be implemented in cooperation with the front-end generic code specification library device based on Web as shown in fig. 3, where the steps are as follows:
step 401: and receiving a user interface code specification configuration instruction input by a developer.
In some embodiments, the code specification configuration instruction includes a compiler used by a developer, a development frame, and a dependency package required by the development frame, where the dependency package includes stylelint-config-standard and stylelint-order code specifications of css language, and esint-retrieved code specifications of JavaScript language. In the step, the device provides a human-computer interaction interface, and a user can input a code specification configuration order through the human-computer interaction interface and select corresponding configuration rules under different modules in the human-computer interaction interface.
Step 402: and selecting corresponding dependent package files in the dependent package module according to requirements, and packaging the dependent package files into a uniform initialization code specification file through a configuration module.
In some embodiments, a corresponding relevant pre-dependency package is selected according to a frame used by a developer, a dependency package module includes existing dependency packages of various open source specifications, such as eslin, stylelint-order, and the like, and a configuration module identifies the dependency package selected by the developer, marks each dependency package, and packages the marked dependency package into an initialized code specification file.
Step 403: in the self-defining specification module, the initialization code specification configuration file is further modified and formulated into a general code specification file required by the project.
In some embodiments, as described above, the custom specification module provides various types of code specification parameter settings, such as naming specification settings, including naming specifications such as a project relative path, a project file name, a common code specification file absolute path, a code parameter key value, and a code parameter value; code specification setting, wherein the code specification setting comprises html, css, JavaScript and other relevant syntax specifications and code format specification setting; code comment specification settings. Developers can modify and set the initial code specification in the custom module according to requirements to form a general code specification configuration file of a project team.
Step 404: and uploading the universal code specification configuration file to a storage module so as to be updated in an iterative manner in an open source mode.
In some embodiments, a developer may store the general code specification configuration file in a storage module, and the module may enable the code specification to be maintained and upgraded in an open source manner, and in a project development process, if there is a related specification that needs to be changed, a modification item may be submitted, and after a development team discusses the specification that needs to be changed or not, it is determined whether the specification needs to be changed or not. When the project needs to update the universal code specification, a command line for updating the specified version is operated, the scaffold analyzes the called new version code specification firstly, whether the current code specification is the version needing to be updated is checked, if the current code specification is the version needing to be updated, a relevant prompt is given, if the current code specification is not the version needing to be updated, an old rc.js file is checked and removed, the latest code specification is installed, and the corresponding rc file is updated.
Step 405: calling a universal code specification configuration file into a directory file of the project through an interface, enabling the code specification to serve as the universal code specification of the project, and using the configured universal code specification through a scaffold in the project.
In some embodiments, a scaffold is installed in a development framework selected by a project, a simple command line tool is set by the scaffold for conveniently using a configured universal code specification, then the scaffold recognizes a code specification file and performs initialization configuration, firstly, whether a code specification old package exists in the project and redundant dependence in the project are checked, an old rc.js file is checked and removed, then, a called universal code specification is further introduced, corresponding rc files such as eslinetrc.js and stylelintrc.js are added to the project, and dependent configuration included in the code specification is added to a package.json file of the project. The scaffold will display the initialization progress of the universal code specification application into the project.
Fig. 5 is a flowchart illustrating the application of the front-end common code specification to the development project according to this embodiment, and is based on the flow completed in fig. 4, that is, based on the common code specification configured by the developer and applicable to this project, the code specification is applied to the development project by using the calling module.
Specifically, the method comprises the following steps:
and step 501, installing a scaffold under a development frame selected by a developer.
In step 505, the old rc.js file and redundant dependencies are removed, and then step 506 is entered.
Fig. 6 is a schematic diagram of the front-end generic code specification library apparatus device based on Web according to the present embodiment.
On the hardware level, the device includes a processor, an internal bus, a network interface, a memory, and a non-volatile memory, and may also include hardware required for other services. The processor reads a corresponding computer program from the non-volatile memory through the internal bus, and then transmits the computer program to the memory for execution, so as to implement the method according to fig. 2, 4 and 5, wherein the main execution body related to the processing flow is not limited to each logic unit, and may also be a hardware or a logic device.
It should be noted that the above description of the flow is for illustration and description only and does not limit the scope of the application of the present specification. Various modifications and alterations to the flow may occur to those skilled in the art, given the benefit of this description. However, such modifications and variations are intended to be within the scope of the present description.
Meanwhile, the invention also discloses a front-end universal code specification library configuration device based on Web, which comprises a processor and a memory; the memory is configured to store instructions that, when executed by the processor, cause the apparatus to implement any of the above-described Web-based front-end common code specification library configuration methods.
Meanwhile, the invention also discloses a computer-readable storage medium, wherein the storage medium stores computer instructions, and after the computer reads the computer instructions in the storage medium, the computer runs any one of the front-end universal code specification library configuration methods based on Web.
In summary, according to the technical scheme of the application, under the condition that a code specification configuration instruction input by a developer is received, according to a code specification dependency package required by a development framework, a target code corresponding to the dependency package is called, and an initial code specification configuration file is generated. Developers can perform self-defined modification on the initialization code specification configuration file to obtain a general code specification configuration file suitable for the whole development team. All developers participating in the project can call the general code specification configuration file in the device through the interface and run the command provided by the script to make the configuration file become the code specification of the project, so that the problem of inconsistent code specifications among different project groups or different developers in development is effectively solved, and the code specification configuration file can be updated and upgraded in an open source mode, thereby effectively improving the development efficiency and the development quality.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents and improvements made within the spirit and principle of the present invention are intended to be included within the scope of the present invention.
Claims (10)
1. A front-end universal code specification library configuration method based on Web is characterized by comprising the following steps:
acquiring a code specification configuration instruction of a user interface;
determining a dependency package according to a development framework, marking the dependency package, and generating an initialization code specification file based on the marked dependency package;
formulating a universal code specification file based on the initialization code specification file;
performing iterative updating based on the universal code specification file;
and installing a scaffold based on the selected frame, realizing the initialization configuration of the universal code specification file based on the scaffold, and performing project inspection.
2. The method as claimed in claim 1, wherein the code specification configuration instruction includes at least one of the following:
a compiler, a development framework, a dependency package required by the development framework.
3. The method of claim 1, wherein the iteratively updating based on the generic code specification file comprises:
when the universal code specification needs to be updated, operating and updating a command line of a specified version;
analyzing the called new version code specification based on the scaffold;
confirming whether the current universal code specification file is a version needing to be updated or not;
if yes, giving a relevant prompt;
otherwise, the old rc.js file is checked and removed, and the latest generic code specification file is installed and the corresponding rc.js file is updated.
4. The method of claim 3, wherein the item check comprises:
checking whether the item has a code specification old package and redundancy dependence in the item;
examine and remove the old rc.js file;
introducing a called universal code specification, and adding a corresponding rc file in a project;
json files of the items are added with the configuration of the dependency contained in the code specification;
and displaying the initialization progress of the universal code specification applied to the project based on the scaffold.
5. A Web-based front-end generic code specification library configuration system, comprising:
the acquisition module is used for acquiring a code specification configuration instruction of the user interface;
the generation module is used for determining a dependency package according to a development framework, marking the dependency package and generating an initialization code specification file based on the marked dependency package;
the formulating module is used for formulating a universal code specification file based on the initialization code specification file;
the updating module is used for carrying out iterative updating based on the general code specification file;
and the inspection module is used for installing the scaffold based on the selected framework, realizing the initialization configuration of the universal code specification file based on the scaffold and carrying out project inspection.
6. The Web-based front-end generic code specification library configuration system of claim 5, wherein the code specification configuration instructions comprise at least one of:
a compiler, a development framework, a dependency package required by the development framework.
7. The Web-based front-end common code specification library configuration system of claim 5, wherein the update module is further configured to:
when the universal code specification needs to be updated, operating and updating a command line of a specified version;
analyzing the called new version code specification based on the scaffold;
confirming whether the current universal code specification file is a version needing to be updated or not;
if yes, giving a relevant prompt;
otherwise, the old rc.js file is checked and removed, and the latest generic code specification file is installed and the corresponding rc.js file is updated.
8. The Web-based front-end common code specification library configuration system of claim 7, wherein said checking module is further configured to:
checking whether the item has a code specification old package and redundancy dependence in the item;
examine and remove the old rc.js file;
introducing a called universal code specification, and adding a corresponding rc file in a project;
json files of the items are added with the configuration of the dependency contained in the code specification;
and displaying the initialization progress of the universal code specification applied to the project based on the scaffold.
9. A Web-based front-end universal code specification library configuration device, comprising a processor, wherein the processor is used for executing the Web-based front-end universal code specification library configuration method in any claim 1-4.
10. A computer-readable storage medium storing computer instructions, wherein when the computer instructions in the storage medium are read by a computer, the computer executes the method for configuring the Web-based front-end common code specification library according to any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111581590.8A CN114217828A (en) | 2021-12-22 | 2021-12-22 | Configuration method, system, device and storage medium of front-end universal code standard library |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111581590.8A CN114217828A (en) | 2021-12-22 | 2021-12-22 | Configuration method, system, device and storage medium of front-end universal code standard library |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114217828A true CN114217828A (en) | 2022-03-22 |
Family
ID=80705077
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111581590.8A Pending CN114217828A (en) | 2021-12-22 | 2021-12-22 | Configuration method, system, device and storage medium of front-end universal code standard library |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114217828A (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109032949A (en) * | 2018-08-02 | 2018-12-18 | 郑州悉知信息科技股份有限公司 | A kind of front-end code quality determining method and device |
| CN110704025A (en) * | 2019-08-29 | 2020-01-17 | 贝壳技术有限公司 | Method and device for generating coding specification tool, storage medium and electronic equipment |
| US20200301672A1 (en) * | 2019-03-20 | 2020-09-24 | International Business Machines Corporation | Generating program analysis rules based on coding standard documents |
| CN112256583A (en) * | 2020-10-28 | 2021-01-22 | 冠群信息技术(南京)有限公司 | Front-end code quality detection method |
| CN112559354A (en) * | 2020-12-18 | 2021-03-26 | 中国平安财产保险股份有限公司 | Front-end code specification detection method and device, computer equipment and storage medium |
| CN113342687A (en) * | 2021-07-01 | 2021-09-03 | 厦门极致互动网络技术股份有限公司 | Method for detecting code specification in batches |
-
2021
- 2021-12-22 CN CN202111581590.8A patent/CN114217828A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109032949A (en) * | 2018-08-02 | 2018-12-18 | 郑州悉知信息科技股份有限公司 | A kind of front-end code quality determining method and device |
| US20200301672A1 (en) * | 2019-03-20 | 2020-09-24 | International Business Machines Corporation | Generating program analysis rules based on coding standard documents |
| CN110704025A (en) * | 2019-08-29 | 2020-01-17 | 贝壳技术有限公司 | Method and device for generating coding specification tool, storage medium and electronic equipment |
| CN112256583A (en) * | 2020-10-28 | 2021-01-22 | 冠群信息技术(南京)有限公司 | Front-end code quality detection method |
| CN112559354A (en) * | 2020-12-18 | 2021-03-26 | 中国平安财产保险股份有限公司 | Front-end code specification detection method and device, computer equipment and storage medium |
| CN113342687A (en) * | 2021-07-01 | 2021-09-03 | 厦门极致互动网络技术股份有限公司 | Method for detecting code specification in batches |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10095489B1 (en) | GUI-based application template for containerized application software development | |
| CN110928529B (en) | Method and system for assisting operator development | |
| US8601433B2 (en) | Method and apparatus for generating virtual software platform based on component model and validating software platform architecture using the platform | |
| US9608893B2 (en) | Methods and systems for parsing data objects | |
| US9489184B2 (en) | Adaptive selection of programming language versions for compilation of software programs | |
| CN105446712B (en) | Application program defect repairing method and device | |
| CN105718251A (en) | Multilanguage SDK (software development kit) automatic implementation method and system | |
| WO2015176492A1 (en) | A system and method thereof for creating dynamically attachable and detachable binary files | |
| US20110126179A1 (en) | Method and System for Dynamic Patching Software Using Source Code | |
| CN111488136A (en) | Continuous integration and continuous delivery method, system, device and storage medium | |
| CN107577609B (en) | Embedded system dynamic module debugging system based on host end dynamic link | |
| Hassam et al. | Assistance system for ocl constraints adaptation during metamodel evolution | |
| US11288062B2 (en) | Automatic source code refactoring | |
| US11429372B2 (en) | Application program updating method, apparatus, system, medium and device | |
| KR101409528B1 (en) | Method and apparatus of mda-based authoring application for smart cross-platform | |
| JP2009157533A (en) | Programmable controller system | |
| CN110209565B (en) | Metadata model debugging method and device | |
| CN110647349B (en) | Method for realizing continuous delivery of iOS APP | |
| CN111552480B (en) | Cross-platform compiling method, device, equipment and readable storage medium | |
| CN112000334A (en) | Page development method, device, server and storage medium | |
| CN113220279A (en) | Code index management method, device, equipment and medium | |
| CN114217828A (en) | Configuration method, system, device and storage medium of front-end universal code standard library | |
| JP5906609B2 (en) | Debug support program, debug support method, and debug support system | |
| WO2023277802A2 (en) | Device and method for identifying errors in a software application | |
| US9405514B1 (en) | Process fragment management |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |