CN113254040B - Front-end framework updating method, device, equipment and storage medium - Google Patents
Front-end framework updating method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN113254040B CN113254040B CN202110607800.XA CN202110607800A CN113254040B CN 113254040 B CN113254040 B CN 113254040B CN 202110607800 A CN202110607800 A CN 202110607800A CN 113254040 B CN113254040 B CN 113254040B
- Authority
- CN
- China
- Prior art keywords
- update
- plug
- basic configuration
- updating
- target front
- 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.)
- Active
Links
Classifications
-
- 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/30—Creation or generation of source code
- G06F8/38—Creation or generation of source code for implementing user interfaces
-
- 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
- G06F9/44526—Plug-ins; Add-ons
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/448—Execution paradigms, e.g. implementations of programming paradigms
- G06F9/4488—Object-oriented
- G06F9/449—Object-oriented method invocation or resolution
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Human Computer Interaction (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Stored Programmes (AREA)
Abstract
The invention relates to the field of development of research and development frames, and discloses a front-end frame updating method, device and equipment and a storage medium. The method comprises the following steps: acquiring text information sent by a client; according to the text information, collecting a plurality of basic configuration files corresponding to the target front-end framework, and according to the text information, configuring a user-defined configuration file modified by the target front-end framework; classifying each basic configuration file according to the deployment type of each basic configuration file to obtain an update plug-in of the target front end framework; adding the custom configuration file into an update plug-in for generating a corresponding update script, wherein the update script comprises a plurality of update commands; based on the update script, updating the current engineering catalog corresponding to the target front-end framework to obtain a new engineering catalog, and executing update on the target front-end framework by adopting the new engineering catalog. The invention realizes the automatic update of the front end frame and reduces the complexity of the automatic update of the front end frame.
Description
Technical Field
The present invention relates to the field of development frameworks, and in particular, to a method, an apparatus, a device, and a storage medium for updating a front end framework.
Background
In the current market, each company has own unique ecological environment, and the deployed front-end framework is also basically in a continuously updated state so as to adapt to the technical iterative development requirements of the company. The number of front end frames which are popular at present is 2, one is a compact-based create-compact-app scaffold, and the other is a vue-based vue-cli, generally, the scaffold is required to be configured to realize engineering facilities of the front end frames which are commonly used in a set of companies, then plug-in libraries of departments in the companies are configured in config. Js files of the front end frames, and then custom configuration and general configuration are combined in a weback merg mode, so that the custom configuration of the front end frames in the companies is realized, and different requirements in the companies are met. However, the configuration in the package json needs to be manually managed by the command line, and the hierarchical splitting of each module in the front-end framework is not obvious enough, so that the iterative updating flow of the front-end framework is complex.
Disclosure of Invention
The invention mainly aims to solve the technical problem that the construction of the existing front-end framework is complicated in iterative updating flow.
The first aspect of the present invention provides a front end framework updating method, including:
Acquiring text information sent by a client, wherein the text information comprises modified contents of a target front-end frame to be updated;
according to the text information, collecting a plurality of basic configuration files corresponding to the target front end frame, and according to the text information, configuring a user-defined configuration file modified by the target front end frame;
classifying each basic configuration file according to the deployment type of each basic configuration file to obtain an update plug-in of the target front end framework;
adding the custom configuration file into the update plug-in for generating a corresponding update script, wherein the update script comprises a plurality of update commands;
and updating the current engineering catalog corresponding to the target front-end framework based on the updating script to obtain a new engineering catalog, and updating the target front-end framework by adopting the new engineering catalog.
Optionally, in a first implementation manner of the first aspect of the present invention, the collecting, according to the text information, a plurality of basic configuration files corresponding to the target front end frame includes:
analyzing the text information to obtain a plurality of configuration parameters and assignment information corresponding to each configuration parameter, and selecting a basic configuration parameter corresponding to the target front end frame from each configuration parameter;
Generating a file calling request according to assignment information corresponding to the basic configuration parameters, and sending the file calling request to a preset storage space corresponding to the target front-end framework;
when response information of the storage space to the file call information is received, the response information is analyzed, and a plurality of basic configuration files corresponding to the target front-end framework are obtained.
Optionally, in a second implementation manner of the first aspect of the present invention, configuring the custom configuration file modified by the target front end framework according to the text information includes:
analyzing the text information to obtain a plurality of configuration parameters and assignment information corresponding to each configuration parameter, and selecting a custom configuration parameter corresponding to the target front end frame from each configuration parameter;
selecting a corresponding preset configuration template according to the self-defined configuration parameters, and writing assignment information corresponding to the self-defined configuration parameters into the selected configuration template;
and packaging each configuration template to obtain the self-defined configuration file modified by the target front-end framework.
Optionally, in a third implementation manner of the first aspect of the present invention, the classifying, according to a deployment type of each base configuration file, the base configuration file to obtain an update plug-in of the target front end framework includes:
Extracting plug-in identification information corresponding to each basic configuration file from a preset plug-in package according to the deployment type of each basic configuration file;
configuring signature files corresponding to the basic configuration files according to the plug-in identification information, and inserting the signature files into the basic configuration files to obtain corresponding types of updated sub-plug-ins;
and packaging the updating sub-plug-ins of different types to obtain the updating plug-in of the target front-end framework.
Optionally, in a fourth implementation manner of the first aspect of the present invention, according to a deployment type of each basic configuration file, plug-in identification information corresponding to each basic configuration file is extracted from a preset plug-in package:
calling a preset identification reading tool to read initial identification information in a preset plug-in package according to the deployment type of each basic configuration file;
analyzing the initial identification information, and extracting plug-in identification information corresponding to each basic configuration file from the analyzed initial identification information.
Optionally, in a fifth implementation manner of the first aspect of the present invention, the calling a preset identifier reading tool to read initial identifier information in a preset package according to a deployment type of each of the base configuration files includes:
Calling a preset identification reading tool to read the identification readable file in the preset plug-in package according to the deployment type of each basic configuration file;
analyzing the identification readable file to obtain an identification command line dialog box, and extracting the identification command line in the identification command dialog box to obtain corresponding initial identification information.
Optionally, in a sixth implementation manner of the first aspect of the present invention, updating, based on the update script, a current engineering catalog corresponding to the target front end framework, and obtaining a new engineering catalog includes:
sequentially verifying whether each update command in the update script accords with a preset command reference condition, and assembling the update command which accords with the command reference condition to obtain a new update script;
executing an update command in the new update script to obtain a plurality of update template files, and sequentially comparing each update template file with a preset engineering catalog corresponding to the target front-end framework;
copying the update template files which do not exist in the engineering catalogue to the engineering catalogue through the corresponding update interfaces to obtain a new engineering catalogue.
A second aspect of the present invention provides a front end framework updating apparatus, comprising:
The system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring text information sent by a client, wherein the text information contains modified contents of a target front end frame to be updated;
the configuration module is used for collecting a plurality of basic configuration files corresponding to the target front end frame according to the text information and configuring the custom configuration files modified by the target front end frame according to the text information;
the classification module is used for classifying each basic configuration file according to the deployment type of each basic configuration file to obtain an update plug-in of the target front end frame;
the generation module is used for adding the custom configuration file into the update plug-in for generating a corresponding update script, wherein the update script comprises a plurality of update commands;
and the updating module is used for updating the current engineering catalog corresponding to the target front-end framework based on the updating script to obtain a new engineering catalog, and updating the target front-end framework by adopting the new engineering catalog.
Optionally, in a first implementation manner of the second aspect of the present invention, the configuration module includes:
the collecting unit is used for analyzing the text information to obtain a plurality of configuration parameters and assignment information corresponding to each configuration parameter, and selecting basic configuration parameters corresponding to the target front end frame from each configuration parameter; generating a file calling request according to assignment information corresponding to the basic configuration parameters, and sending the file calling request to a preset storage space corresponding to the target front-end framework; when response information of the storage space to the file call information is received, the response information is analyzed, and a plurality of basic configuration files corresponding to the target front-end framework are obtained.
Optionally, in a second implementation manner of the second aspect of the present invention, the configuration module further includes:
the configuration unit is used for analyzing the text information to obtain a plurality of configuration parameters and assignment information corresponding to each configuration parameter, and selecting a custom configuration parameter corresponding to the target front end frame from each configuration parameter; selecting a corresponding preset configuration template according to the self-defined configuration parameters, and writing assignment information corresponding to the self-defined configuration parameters into the selected configuration template; and packaging each configuration template to obtain the self-defined configuration file modified by the target front-end framework.
Optionally, in a third implementation manner of the second aspect of the present invention, the classification module includes:
the extraction unit is used for extracting plug-in identification information corresponding to each basic configuration file from a preset plug-in package according to the deployment type of each basic configuration file;
the configuration unit is used for configuring signature files corresponding to the basic configuration files according to the plug-in identification information, and inserting the signature files into the basic configuration files to obtain corresponding types of updated sub-plug-ins;
And the packaging unit is used for packaging the updating sub-plug-ins of different types to obtain the updating plug-in of the target front-end framework.
Optionally, in a fourth implementation manner of the second aspect of the present invention, the extracting unit is further configured to:
calling a preset identification reading tool to read initial identification information in a preset plug-in package according to the deployment type of each basic configuration file;
analyzing the initial identification information, and extracting plug-in identification information corresponding to each basic configuration file from the analyzed initial identification information.
Optionally, in a fifth implementation manner of the second aspect of the present invention, the extracting unit is further configured to:
calling a preset identification reading tool to read the identification readable file in the preset plug-in package according to the deployment type of each basic configuration file;
analyzing the identification readable file to obtain an identification command line dialog box, and extracting the identification command line in the identification command dialog box to obtain corresponding initial identification information.
Optionally, in a sixth implementation manner of the second aspect of the present invention, the update module includes a first update unit and a second unit, where the first update unit is configured to:
Sequentially verifying whether each update command in the update script accords with a preset command reference condition, and assembling the update command which accords with the command reference condition to obtain a new update script;
executing an update command in the new update script to obtain a plurality of update template files, and sequentially comparing each update template file with a preset engineering catalog corresponding to the target front-end framework;
copying the update template files which do not exist in the engineering catalogue to the engineering catalogue through the corresponding update interfaces to obtain a new engineering catalogue.
A third aspect of the present invention provides a front end framework update apparatus comprising: a memory and at least one processor, the memory having instructions stored therein; the at least one processor invokes the instructions in the memory to cause the front end framework update device to perform the front end framework update method described above.
A fourth aspect of the present invention provides a computer readable storage medium having instructions stored therein which, when run on a computer, cause the computer to perform the front end framework updating method described above.
In the technical scheme provided by the invention, a developer firstly writes the modified content of the target front-end frame in a text information manner in an interactive interface, then reads a plurality of basic configuration files of the target front-end frame through the text information, and classifies the basic configuration files to obtain a plurality of updating plugins for updating the basic configuration of the target front-end frame; meanwhile, the custom configuration file of the developer is configured, and the custom configuration file is added into the update plug-in to generate an update script of the target front-end frame, through the update script, on one hand, the basic configuration of the target front-end frame can be updated, and on the other hand, the custom configuration of the target front-end frame can be updated, so that the automatic update of the front-end frame is realized, the complexity of the automatic update of the front-end frame is reduced, and meanwhile, the individuation degree of the front-end frame update is improved.
Drawings
FIG. 1 is a schematic diagram of a first embodiment of a front end frame updating method according to an embodiment of the present invention;
FIG. 2 is a diagram illustrating a second embodiment of a front end framework update method according to an embodiment of the present invention;
FIG. 3 is a schematic diagram of a front end frame updating apparatus according to a first embodiment of the present invention;
FIG. 4 is a schematic diagram of a second embodiment of a front end frame updating apparatus according to an embodiment of the present invention;
fig. 5 is a schematic diagram of an embodiment of a front end frame updating apparatus according to an embodiment of the present invention.
Detailed Description
The embodiment of the invention provides a front end framework updating method, a device, equipment and a storage medium, which are used for acquiring text information sent by a client; according to the text information, collecting a plurality of basic configuration files corresponding to the target front-end framework, and according to the text information, configuring a user-defined configuration file modified by the target front-end framework; classifying each basic configuration file according to the deployment type of each basic configuration file to obtain an update plug-in of the target front end framework; adding the custom configuration file into an update plug-in for generating a corresponding update script, wherein the update script comprises a plurality of update commands; based on the update script, updating the current engineering catalog corresponding to the target front-end framework to obtain a new engineering catalog, and executing update on the target front-end framework by adopting the new engineering catalog. The invention realizes the automatic update of the front end frame and reduces the complexity of the automatic update of the front end frame.
The terms "first," "second," "third," "fourth" and the like in the description and in the claims and in the above drawings, if any, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments described herein may be implemented in other sequences than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed or inherent to such process, method, article, or apparatus.
For easy understanding, the following describes a specific flow of an embodiment of the present invention, referring to fig. 1, and a first embodiment of a front end frame updating method in an embodiment of the present invention includes:
101. acquiring text information sent by a client, wherein the text information comprises modified contents of a target front-end frame to be updated;
It will be appreciated that the execution body of the present invention may be a front end framework updating device, and may also be a terminal or a server, which is not limited herein. The embodiment of the invention is described by taking a server as an execution main body as an example.
In this embodiment, when the add-delete modification front end frame is performed, the add-delete modification may be performed by adding an add-delete modification file to the add-delete modification file. In order to realize automatic updating of the front-end framework, firstly, a developer writes modified content of the target front-end framework on an interactive interface of a client, wherein the modified content is written in a text format file, namely text information; then uploading the file to a background server through a client; the text information comprises basic configuration and custom configuration of the front-end framework.
Specifically, for example, a front-end framework written in JSON (JavaScript Object Notation, JS object numbered musical notation) may write the modification content into a preset template, and generate an HTML (Hyper Text Markup Language ) file for modifying a plug-in of a file in a package.
102. According to the text information, collecting a plurality of basic configuration files corresponding to the target front end frame, and according to the text information, configuring a user-defined configuration file modified by the target front end frame;
in this embodiment, a basic configuration and a custom configuration of a front end framework modification content are written in text information, where the basic configuration is pre-written by a developer and stored in a local folder or a storage server, and at this time, a corresponding basic configuration file can be directly collected according to the modification content corresponding to the basic configuration in the text information, and used for updating a corresponding plug-in of the basic configuration in a subsequent target front end framework, where an identification field corresponding to the basic configuration is written in the text information, and the identification field is bound with a file name of the basic configuration file, that is, according to the identification field, the basic configuration file bound in the local folder or the storage server can be searched; the custom configuration in the text information is written into a corresponding command line by a developer, and then the corresponding command line is written into a position corresponding to a preset custom blank table according to the configuration name of the command line, so that the custom configuration file in a uniform format can be converted.
103. Classifying each basic configuration file according to the deployment type of each basic configuration file to obtain an update plug-in of the target front end framework;
in this embodiment, the deployment type of the basic configuration file includes a development environment and a release environment, and normalized classification processing is performed according to the deployment type of the basic configuration file, where the basic configuration file corresponding to the development environment may be classified into a plugin module corresponding to the dependencies, and the basic configuration environment corresponding to the release environment may be classified into a plugin module corresponding to the dependencies, and the development environment or the release environment may be specified through node_env=development or node_env=production. Wherein, the basic configuration file on which the 'devDependencies' depend can only be used in a development environment, and the production environment cannot be driven into a package; the "dependencies" dependent basic configuration file can be used not only in the development environment, but also in the production environment, which means that the dependent development environment installed in dependencies can be used without installing the dependencies in "dependencies" again, for example, the babel compiling tool is only used during development, and the dependencies can be configured, and the dependencies can be used in the development environment if the dependencies are installed in the basic configuration file.
104. Adding the custom configuration file into the update plug-in for generating a corresponding update script, wherein the update script comprises a plurality of update commands;
in this embodiment, the custom configuration file includes descriptions command configuration of a developer, and after the custom configuration file is added to the update plug-in, an update script is generated, which may be a sh file, and may be executed by a corresponding sh file running tool. In addition, each update command in the update script corresponds to the configuration file of each modification content of the target front-end framework, and comprises an update command corresponding to the basic configuration file and an update command corresponding to the custom configuration file. And subsequently, when the target front-end framework is updated, the package json is read again according to the update command so as to refresh the current HTML configuration file.
Further, the modification of the target front-end framework also introduces command-, for injecting custom commands, an required script for interacting with the user, and ORA-, for prompting feedback, loading, success, error information of the target front-end framework update. In addition, the target front-end framework also adds a script for checking update, so that the next time the developer uses the latest target front-end framework can be ensured.
105. And updating the current engineering catalog corresponding to the target front-end framework based on the updating script to obtain a new engineering catalog, and updating the target front-end framework by adopting the new engineering catalog.
In this embodiment, the current engineering catalog records current configuration information of the target front end framework, and includes the content such as the configuration of the baseband. Config, the eslin specification code, the object test unit, the task code submitting hook, the nodejs service, the configuration file, the proxy setting, the starting service, the framework configuration, the package. Json configuration, and the like, which correspond to each function item. And according to the update script, acquiring corresponding content of the corresponding functional item from a preset database, copying the functional item which does not exist in the current engineering catalog into the current engineering item, and reloading the target front end frame by adopting the new engineering item, thereby realizing the update of the target front end frame.
In the embodiment of the invention, a developer firstly writes the modified content of the target front-end frame in a text information mode in an interactive interface, then reads a plurality of basic configuration files of the target front-end frame through the text information, and classifies the basic configuration files to obtain a plurality of updating plugins for updating the basic configuration of the target front-end frame; meanwhile, the custom configuration file of the developer is configured, and the custom configuration file is added into the update plug-in to generate an update script of the target front-end frame, through the update script, on one hand, the basic configuration of the target front-end frame can be updated, and on the other hand, the custom configuration of the target front-end frame can be updated, so that the automatic update of the front-end frame is realized, the complexity of the automatic update of the front-end frame is reduced, and meanwhile, the individuation degree of the front-end frame update is improved.
Referring to fig. 2, a second embodiment of a front end frame updating method according to an embodiment of the present invention includes:
201. acquiring text information sent by a client, wherein the text information comprises modified contents of a target front-end frame to be updated;
202. analyzing the text information to obtain a plurality of configuration parameters and assignment information corresponding to each configuration parameter, and selecting a basic configuration parameter corresponding to the target front end frame from each configuration parameter;
203. generating a file calling request according to assignment information corresponding to the basic configuration parameters, and sending the file calling request to a preset storage space corresponding to the target front-end framework;
204. when receiving response information of the storage space to the file call information, analyzing the response information to obtain a plurality of basic configuration files corresponding to the target front-end framework;
in this embodiment, configuration parameters, such as initialization data, module export, monitor, lifecycle, etc., are written in the modification content of the basic configuration in the text information, and then each configuration parameter is written with assignment information, for example, for the lifecycle of the page, the assignment information may include: the assignment information may include, for example, a monitor name, the number of monitor objects, a trigger condition of the monitor object, and so on, for the monitor. For basic configuration which does not need to be modified, assignment information of corresponding configuration parameters in the text information is null, the basic configuration which needs to be modified is obtained, the corresponding assignment information is compiled for the corresponding configuration parameters in the text information, and the configuration parameters which are compiled with the assignment information can be selected as basic configuration parameters.
In this embodiment, after obtaining the basic assignment information corresponding to the basic configuration, the basic configuration that needs to be modified by the front end framework may be determined, and the basic assignment information is written as the configuration request content into the template of the preset file call request, so that a file call request, for example, an Ajax request, may be generated, and the JSON data may be requested to be loaded by using the HTTP GET method. And finally, according to the basic assignment information in the file calling request, searching a corresponding basic configuration file in a storage space of the target front-end framework, and returning to the server in a response information mode, wherein the storage space can be a local physical storage space or a cloud storage space of the server.
205. Analyzing the text information to obtain a plurality of configuration parameters and assignment information corresponding to each configuration parameter, and selecting a custom configuration parameter corresponding to the target front end frame from each configuration parameter;
206. selecting a corresponding preset configuration template according to the self-defined configuration parameters, and writing assignment information corresponding to the self-defined configuration parameters into the selected configuration template;
207. packaging each configuration template to obtain a custom configuration file modified by the target front end framework;
In this embodiment, the modification content of the custom configuration in the text information is written with custom configuration parameters, and for different custom configuration parameters, corresponding configuration templates are associated to perform standardization processing on the custom configuration parameters, where the configuration templates include configuration names of each custom configuration and configuration parameters included in the custom configuration, match corresponding configuration names in the configuration templates, and fill assignment information in the custom configuration parameters into the configuration templates in sequence, and for configuration parameters that are not assigned, the configuration parameters can be automatically set to be null or assigned according to default settings. After the assignment information corresponding to the custom configuration parameters is written into each configuration template, each configuration template can be packaged into a custom configuration file.
208. Extracting plug-in identification information corresponding to each basic configuration file from a preset plug-in package according to the deployment type of each basic configuration file;
209. configuring signature files corresponding to the basic configuration files according to the plug-in identification information, and inserting the signature files into the basic configuration files to obtain corresponding types of updated sub-plug-ins;
210. Packaging the updating sub-plug-ins of different types to obtain the updating plug-in of the target front-end framework;
in this embodiment, the plug-in identification information includes, but is not limited to, various information for identifying the base profile. The plug-in identification information may include at least any one of an application name, a basic profile name, a version number, and the like, and for example, the plug-in identification information of the basic profile may include only the application name, or may include three items of an application name, a package name, and a version number.
The plug-in identification information is included in a manifest file (such as manifest. Xml) of the base configuration file, and plug-in initial identification information specified by the base configuration file may be extracted from the manifest file. Preferably, an identification information reading tool may be invoked to obtain the plug-in initial identification information, where the identification information reading tool refers to a tool provided by the intelligent operating system for reading the plug-in initial identification information. The identification information reading tool can acquire the initial identification information of the plug-in by reading a manifest file (manifest. Xml) in the basic configuration file; the identification information reading tool may be an adb tool (AndroidDebug Bridge, abbreviated as adb) under the android operating system.
In this embodiment, according to the plug-in identification information, a corresponding signature file is configured for the base configuration file, and the configured signature file is inserted into the plug-in package. Wherein the signature file includes, but is not limited to, various files containing signature information.
When the plug-in integrated in the basic configuration file needs to run, the host computer can obtain signature information according to the signature file of each updated sub-plug-in, and compare the signature information with the preset signature information. If so, the host may allow the update child plug-in to run. If not, the host does not allow the update child plug-in to run. Wherein different update sub-plug-ins may be assigned the same signature file. Alternatively, different update sub-plug-ins may be assigned different signature files. Each update sub-package may be assigned a signature file, such as a random code; as another example, the signature file of the update sub-plug-in may also be generated based on various signature file generation algorithms.
Specifically, the manner of inserting the configured signature file into the update sub-plug-in includes, but is not limited to, the following 3 types:
1) Distributing or generating signature files for the update sub-plug-ins by self, and inserting the distributed or generated signature files into the update sub-plug-ins;
2) Acquiring a signature file for an updated sub-plug-in from a first signature device, and inserting the acquired signature file into a plug-in package;
3) The update sub-plug-in is provided to the second signing device, the second signing device configures a signature file for the update sub-plug-in, the signature file is inserted into the plug-in package, and then the update sub-plug-in with the inserted signature file can be received from the second signing device.
Wherein the first signing device and the second signing device may be incorporated in any apparatus. For example, the first signing device may be provided in the host or in the network apparatus. The first signature device can allocate or generate a signature file for the update sub-plug-in and provide the signature file for the host; the second signing device may assign or generate a signature file for the update sub-plug-in and insert the assigned or generated signature file into the update sub-plug-in.
Accordingly, the host may acquire a signature file from the first signing device for the update sub-plug-in, and insert the acquired signature file into the update sub-plug-in. Specifically, a unified signature file may be directly obtained from the first signature device, or the update sub-plug-in or the plug-in identification information thereof may be sent to the first signature device. Accordingly, the first signing device may allocate or generate a signature file according to the received update sub-plug-in or its plug-in identification information. The first signing device may then return the generated signature file to the host.
And finally, storing the updated sub-plug-in inserted with the signature file to a specified path, so that the updated sub-plug-in can be associated with the host computer to obtain the updated plug-in of the target front-end framework.
Preferably, if the current package name of the update sub-plug-in is consistent with the package name in the manifest file of the base configuration file, the update sub-plug-in that has inserted the signature file may be saved to under the path specified by the host. The current package name of the update sub-plug-in inserted into the signature file can be compared with the package name in the manifest file (xml) of the base configuration file, and if the package names are consistent, the update sub-plug-in inserted into the signature file can be directly stored under the path appointed by the host.
Preferably, if the current package name of the updated sub-plug-in is inconsistent with the package name in the manifest file of the base configuration file, the current package name of the updated sub-plug-in is renamed to the package name in the manifest file, and the updated sub-plug-in inserted into the signature file is saved under the path appointed by the host according to the renamed package name.
Specifically, the extraction process of the plug-in identification information comprises the following steps:
(1) Calling a preset identification reading tool to read initial identification information in a preset plug-in package according to the deployment type of each basic configuration file;
(2) Analyzing the initial identification information, and extracting plug-in identification information corresponding to each basic configuration file from the analyzed initial identification information.
The plug-in initial identification information refers to plug-in identification information directly obtained by an identification information reading tool. The plug-in initial identification information typically includes plug-in identification information specified by the base profile, as well as other redundant information. In the subsequent step, the plug-in initial identification information needs to be parsed to obtain plug-in identification information specified by the basic configuration file. Preferably, the plug-in initial identifying information is presented in a command line dialog box. The plug-in initial identification information presented in the command line dialog box may then be saved in a readable file such that the plug-in initial identification information is resolvable. Wherein the plug-in initial identification information presented in the command line dialog box cannot be parsed, and the plug-in initial identification information stored in the readable file can be parsed.
Further, the initial identification information may be read in the following manner:
(1) Calling a preset identification reading tool to read the identification readable file in the preset plug-in package according to the deployment type of each basic configuration file;
(2) Analyzing the identification readable file to obtain an identification command line dialog box, and extracting the identification command line in the identification command dialog box to obtain corresponding initial identification information
Further, the plug-in identification information specified by the base profile is typically saved in the initial identification information in the form of a "name/value" pair. For example, the initial identification information may be searched according to a preset "name" string, so as to obtain a "value" string corresponding to the "name" string. The character string representing the value is the plug-in identification information. For example, the initial identification information may be searched according to a "name" string, namely "package name", where the "value" string corresponding to the "name" string is package identification information designated by the host; for another example, the "value" string corresponding to the "name" string may be found in the initial identification information according to the "version" string, which is the plug-in identification information, i.e. the version number.
211. Adding the custom configuration file into the update plug-in for generating a corresponding update script, wherein the update script comprises a plurality of update commands;
212. And updating the current engineering catalog corresponding to the target front-end framework based on the updating script to obtain a new engineering catalog, and updating the target front-end framework by adopting the new engineering catalog.
(1) Sequentially verifying whether each update command in the update script accords with a preset command reference condition, and assembling the update command which accords with the command reference condition to obtain a new update script;
(2) Executing an update command in the new update script to obtain a plurality of update template files, and sequentially comparing each update template file with a preset engineering catalog corresponding to the target front-end framework;
(3) Copying the update template files which do not exist in the engineering catalogue to the engineering catalogue through the corresponding update interfaces to obtain a new engineering catalogue.
In this embodiment, the update script includes a plurality of update commands, and according to the main method in package. Json, the entry for executing the script may be determined, and then a command writing tool, for example, a command writing tool, is passed to verify whether each update command meets a preset command basic condition, and specifically, the command basic condition may be determined by GNU tool, UNIX tool, fs-extra, and the like.
Specifically, for example, UNIX command line options typically include a dash followed by one or more lowercase letters; the GNU tool adds a double dash followed by a complete word or compound word, examples of which are as follows:
help, namely giving out the use information, and then exiting, wherein the UNIX command acts as "-h", and the GNU tool is "- -hellp";
version, namely the real program version number, then quit, UNIX command behavior "-v", GNU tool is "- -version";
all the information or operation of all the parameters are displayed, the UNIX command acts as "- -a", and the GNU tool is "- -all";
listing files or parameters, taking no other action, the UNIX command acts "-l", and the GNU tool is "- -list";
quiet, i.e., inhibit stdout, UNIX command behavior "-q", GNU tool "- -quick";
recursion, i.e., recursion operations (including subdirectory trees), UNIX command behavior "-R" or "-R", GNU tool "- -recovery";
in this embodiment, the update template file is written with a background configuration, an eslin specification code, a test unit, a task code submitting hook, a nodejs service, a configuration file, a proxy setting, a startup service, a framework configuration, a package json configuration, and the like corresponding to each function item, and if the update template file does not exist in the preset engineering catalog, the corresponding update template file can be determined to be modified content, and the update template file is copied to the engineering catalog, so that the modified content can be presented on the target front-end framework.
In the embodiment of the invention, the configuration of the basic configuration file and the custom configuration file is performed according to the text information, the configuration is performed through the basic configuration file and the custom configuration file to generate the update script for updating the current front-end framework, and the update of the target front-end framework can be realized by executing the update script directly in the later stage.
The front end frame updating method in the embodiment of the present invention is described above, and the front end frame updating device in the embodiment of the present invention is described below, referring to fig. 3, where a first embodiment of the front end frame updating device in the embodiment of the present invention includes:
an obtaining module 301, configured to obtain text information sent by a client, where the text information includes modified content of a target front end frame to be updated;
the configuration module 302 is configured to collect a plurality of basic configuration files corresponding to the target front end frame according to the text information, and configure a custom configuration file modified by the target front end frame according to the text information;
the classification module 303 is configured to classify each basic configuration file according to a deployment type of each basic configuration file, so as to obtain an update plug-in of the target front end framework;
A generating module 304, configured to add the custom configuration file to the update plug-in, so as to generate a corresponding update script, where the update script includes a plurality of update commands;
and the updating module 305 is configured to update the current engineering catalog corresponding to the target front-end framework based on the updating script, obtain a new engineering catalog, and execute updating on the target front-end framework by using the new engineering catalog.
In the embodiment of the invention, a developer firstly writes the modified content of the target front-end frame in a text information mode in an interactive interface, then reads a plurality of basic configuration files of the target front-end frame through the text information, and classifies the basic configuration files to obtain a plurality of updating plugins for updating the basic configuration of the target front-end frame; meanwhile, the custom configuration file of the developer is configured, and the custom configuration file is added into the update plug-in to generate an update script of the target front-end frame, through the update script, on one hand, the basic configuration of the target front-end frame can be updated, and on the other hand, the custom configuration of the target front-end frame can be updated, so that the automatic update of the front-end frame is realized, the complexity of the automatic update of the front-end frame is reduced, and meanwhile, the individuation degree of the front-end frame update is improved.
Referring to fig. 4, a second embodiment of the front end frame updating apparatus according to the present invention includes:
an obtaining module 301, configured to obtain text information sent by a client, where the text information includes modified content of a target front end frame to be updated;
the configuration module 302 is configured to collect a plurality of basic configuration files corresponding to the target front end frame according to the text information, and configure a custom configuration file modified by the target front end frame according to the text information;
the classification module 303 is configured to classify each basic configuration file according to a deployment type of each basic configuration file, so as to obtain an update plug-in of the target front end framework;
a generating module 304, configured to add the custom configuration file to the update plug-in, so as to generate a corresponding update script, where the update script includes a plurality of update commands;
and the updating module 305 is configured to update the current engineering catalog corresponding to the target front-end framework based on the updating script, obtain a new engineering catalog, and execute updating on the target front-end framework by using the new engineering catalog.
Specifically, the configuration module 302 includes a gathering unit 3021 and a configuration unit 3022, where the gathering unit 3021 is configured to:
Analyzing the text information to obtain a plurality of configuration parameters and assignment information corresponding to each configuration parameter, and selecting a basic configuration parameter corresponding to the target front end frame from each configuration parameter;
generating a file calling request according to assignment information corresponding to the basic configuration parameters, and sending the file calling request to a preset storage space corresponding to the target front-end framework;
when response information of the storage space to the file call information is received, the response information is analyzed, and a plurality of basic configuration files corresponding to the target front-end framework are obtained.
Specifically, the configuration unit 3022 is configured to:
analyzing the text information to obtain a plurality of configuration parameters and assignment information corresponding to each configuration parameter, and selecting a custom configuration parameter corresponding to the target front end frame from each configuration parameter;
selecting a corresponding preset configuration template according to the self-defined configuration parameters, and writing assignment information corresponding to the self-defined configuration parameters into the selected configuration template;
and packaging each configuration template to obtain the self-defined configuration file modified by the target front-end framework.
Specifically, the classification module 303 includes:
an extracting unit 3031, configured to extract plug-in identification information corresponding to each basic configuration file from a preset plug-in package according to a deployment type of each basic configuration file;
a configuration unit 3032, configured to configure signature files corresponding to the basic configuration files according to the plug-in identification information, and insert each signature file into the basic configuration file to obtain a corresponding type of updated sub-plug-in;
and the packaging unit 3033 is configured to package each of the different types of update sub-plug-ins to obtain an update plug-in of the target front-end framework.
Specifically, the extracting unit 3031 is further configured to:
calling a preset identification reading tool to read initial identification information in a preset plug-in package according to the deployment type of each basic configuration file;
analyzing the initial identification information, and extracting plug-in identification information corresponding to each basic configuration file from the analyzed initial identification information.
Specifically, the extracting unit 3031 is further configured to:
calling a preset identification reading tool to read the identification readable file in the preset plug-in package according to the deployment type of each basic configuration file;
Analyzing the identification readable file to obtain an identification command line dialog box, and extracting the identification command line in the identification command dialog box to obtain corresponding initial identification information.
Specifically, the update module 305 includes a first update unit 3051 and a second unit 3052, where the first update unit 3051 is configured to:
sequentially verifying whether each update command in the update script accords with a preset command reference condition, and assembling the update command which accords with the command reference condition to obtain a new update script;
executing an update command in the new update script to obtain a plurality of update template files, and sequentially comparing each update template file with a preset engineering catalog corresponding to the target front-end framework;
copying the update template files which do not exist in the engineering catalogue to the engineering catalogue through the corresponding update interfaces to obtain a new engineering catalogue.
In the embodiment of the invention, the configuration of the basic configuration file and the custom configuration file is performed according to the text information, the configuration is performed through the basic configuration file and the custom configuration file to generate the update script for updating the current front-end framework, and the update of the target front-end framework can be realized by executing the update script directly in the later stage.
The front end frame updating apparatus in the embodiment of the present invention is described in detail above in fig. 3 and 4 from the point of view of modularized functional entities, and the front end frame updating device in the embodiment of the present invention is described in detail below from the point of view of hardware processing.
Fig. 5 is a schematic structural diagram of a front-end framework updating apparatus provided in an embodiment of the present invention, where the front-end framework updating apparatus 500 may have a relatively large difference due to configuration or performance, and may include one or more processors (central processing units, CPU) 510 (e.g., one or more processors) and a memory 520, and one or more storage media 530 (e.g., one or more mass storage devices) storing application programs 533 or data 532. Wherein memory 520 and storage medium 530 may be transitory or persistent storage. The program stored on the storage medium 530 may include one or more modules (not shown), each of which may include a series of instruction operations in the front end framework updating apparatus 500. Still further, the processor 510 may be arranged to communicate with the storage medium 530 and to perform a series of instruction operations in the storage medium 530 on the front end framework updating device 500.
The front end framework updating apparatus 500 may also include one or more power supplies 540, one or more wired or wireless network interfaces 550, one or more input/output interfaces 560, and/or one or more operating systems 531, such as Windows Serve, mac OS X, unix, linux, freeBSD, and the like. It will be appreciated by those skilled in the art that the front end frame updating apparatus structure shown in fig. 5 is not limiting of the front end frame updating apparatus and may include more or fewer components than shown, or may combine certain components, or may be a different arrangement of components.
The present invention also provides a front end frame updating apparatus, which includes a memory and a processor, where the memory stores computer readable instructions that, when executed by the processor, cause the processor to execute the steps of the front end frame updating method in the above embodiments.
The present invention also provides a computer readable storage medium, which may be a non-volatile computer readable storage medium, or a volatile computer readable storage medium, having stored therein instructions that, when executed on a computer, cause the computer to perform the steps of the front end frame updating method.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, which are not repeated herein.
The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied essentially or in part or all of the technical solution or in part in the form of a software product stored in a storage medium, including instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a read-only memory (ROM), a random access memory (random access memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
The above embodiments are only for illustrating the technical solution of the present invention, and not for limiting the same; although the invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present invention.
Claims (10)
1. A front end framework update method, the front end framework update method comprising:
acquiring text information sent by a client, wherein the text information comprises modified contents of a target front-end frame to be updated;
according to the text information, collecting a plurality of basic configuration files corresponding to the target front end frame, and according to the text information, configuring a user-defined configuration file modified by the target front end frame;
classifying each basic configuration file according to the deployment type of each basic configuration file to obtain an update plug-in of the target front end framework;
adding the custom configuration file into the update plug-in for generating a corresponding update script, wherein the update script comprises a plurality of update commands;
And updating the current engineering catalog corresponding to the target front-end framework based on the updating script to obtain a new engineering catalog, and updating the target front-end framework by adopting the new engineering catalog.
2. The method of updating a front-end framework according to claim 1, wherein the gathering the plurality of basic configuration files corresponding to the target front-end framework according to the text information comprises:
analyzing the text information to obtain a plurality of configuration parameters and assignment information corresponding to each configuration parameter, and selecting a basic configuration parameter corresponding to the target front end frame from each configuration parameter;
generating a file calling request according to assignment information corresponding to the basic configuration parameters, and sending the file calling request to a preset storage space corresponding to the target front-end framework;
when response information of the storage space to the file call information is received, the response information is analyzed, and a plurality of basic configuration files corresponding to the target front-end framework are obtained.
3. The method for updating a front end framework according to claim 1, wherein configuring the custom configuration file modified by the target front end framework according to the text information comprises:
Analyzing the text information to obtain a plurality of configuration parameters and assignment information corresponding to each configuration parameter, and selecting a custom configuration parameter corresponding to the target front end frame from each configuration parameter;
selecting a corresponding preset configuration template according to the self-defined configuration parameters, and writing assignment information corresponding to the self-defined configuration parameters into the selected configuration template;
and packaging each configuration template to obtain the self-defined configuration file modified by the target front-end framework.
4. The method for updating a front end framework according to claim 1, wherein the classifying each basic configuration file according to the deployment type of each basic configuration file to obtain the update plug-in of the target front end framework comprises:
extracting plug-in identification information corresponding to each basic configuration file from a preset plug-in package according to the deployment type of each basic configuration file;
configuring signature files corresponding to the basic configuration files according to the plug-in identification information, and inserting the signature files into the basic configuration files to obtain corresponding types of updated sub-plug-ins;
And packaging the updating sub-plug-ins of different types to obtain the updating plug-in of the target front-end framework.
5. The method for updating a front end framework according to claim 4, wherein extracting plug-in identification information corresponding to each basic configuration file from a preset plug-in package according to a deployment type of each basic configuration file comprises:
calling a preset identification reading tool to read initial identification information in a preset plug-in package according to the deployment type of each basic configuration file;
analyzing the initial identification information, and extracting plug-in identification information corresponding to each basic configuration file from the analyzed initial identification information.
6. The method for updating a front end framework according to claim 5, wherein the calling a preset identifier reading tool to read initial identifier information in a preset package according to the deployment type of each basic configuration file comprises:
calling a preset identification reading tool to read the identification readable file in the preset plug-in package according to the deployment type of each basic configuration file;
analyzing the identification readable file to obtain an identification command line dialog box, and extracting the identification command line in the identification command line dialog box to obtain corresponding initial identification information.
7. The method for updating a front end framework according to any one of claims 1 to 6, wherein updating the current engineering catalog corresponding to the target front end framework based on the update script, to obtain a new engineering catalog includes:
sequentially verifying whether each update command in the update script accords with a preset command reference condition, and assembling the update command which accords with the command reference condition to obtain a new update script;
executing an update command in the new update script to obtain a plurality of update template files, and sequentially comparing each update template file with a preset engineering catalog corresponding to the target front-end framework;
copying the update template files which do not exist in the engineering catalogue to the engineering catalogue through the corresponding update interfaces to obtain a new engineering catalogue.
8. A front end frame updating apparatus, characterized in that the front end frame updating apparatus comprises:
the system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring text information sent by a client, wherein the text information contains modified contents of a target front end frame to be updated;
the configuration module is used for collecting a plurality of basic configuration files corresponding to the target front end frame according to the text information and configuring the custom configuration files modified by the target front end frame according to the text information;
The classification module is used for classifying each basic configuration file according to the deployment type of each basic configuration file to obtain an update plug-in of the target front end frame;
the generation module is used for adding the custom configuration file into the update plug-in for generating a corresponding update script, wherein the update script comprises a plurality of update commands;
and the updating module is used for updating the current engineering catalog corresponding to the target front-end framework based on the updating script to obtain a new engineering catalog, and updating the target front-end framework by adopting the new engineering catalog.
9. A front end framework update apparatus, the front end framework update apparatus comprising: a memory and at least one processor, the memory having instructions stored therein;
the at least one processor invoking the instructions in the memory to cause the front end frame update device to perform the front end frame update method of any of claims 1-7.
10. A computer readable storage medium having stored thereon a computer program, which when executed by a processor implements the front end framework updating method of any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110607800.XA CN113254040B (en) | 2021-06-01 | 2021-06-01 | Front-end framework updating method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110607800.XA CN113254040B (en) | 2021-06-01 | 2021-06-01 | Front-end framework updating method, device, equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113254040A CN113254040A (en) | 2021-08-13 |
| CN113254040B true CN113254040B (en) | 2023-10-20 |
Family
ID=77185763
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110607800.XA Active CN113254040B (en) | 2021-06-01 | 2021-06-01 | Front-end framework updating method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113254040B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114756217B (en) * | 2022-03-22 | 2022-10-25 | 北京云枢创新软件技术有限公司 | Plug-in based script generation system |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110647320A (en) * | 2019-08-14 | 2020-01-03 | 平安普惠企业管理有限公司 | Project framework construction method and device, computer equipment and storage medium |
| CN111897520A (en) * | 2020-07-31 | 2020-11-06 | 平安科技（深圳）有限公司 | Front-end project framework construction method and device, computer equipment and storage medium |
| CN112306533A (en) * | 2020-11-27 | 2021-02-02 | 平安普惠企业管理有限公司 | Front-end framework automatic conversion method and device, computer equipment and storage medium |
-
2021
- 2021-06-01 CN CN202110607800.XA patent/CN113254040B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110647320A (en) * | 2019-08-14 | 2020-01-03 | 平安普惠企业管理有限公司 | Project framework construction method and device, computer equipment and storage medium |
| CN111897520A (en) * | 2020-07-31 | 2020-11-06 | 平安科技（深圳）有限公司 | Front-end project framework construction method and device, computer equipment and storage medium |
| CN112306533A (en) * | 2020-11-27 | 2021-02-02 | 平安普惠企业管理有限公司 | Front-end framework automatic conversion method and device, computer equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113254040A (en) | 2021-08-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR101314949B1 (en) | Integration environment generator | |
| US9424003B1 (en) | Schema-less system output object parser and code generator | |
| CN108399083B (en) | System deployment method, device, electronic equipment and storage medium | |
| US20150082298A1 (en) | Packaging and deploying hybrid applications | |
| US8365163B2 (en) | Method for configuring a computer program | |
| US8839107B2 (en) | Context based script generation | |
| US9384005B2 (en) | Systems and methods for dynamic configuration of client-side development environments through use of application servers | |
| EP3502896A1 (en) | Generation of an adapters configuration user interface | |
| US20100070961A1 (en) | Supplying Software Updates Synchronously | |
| WO2004086222A2 (en) | Development of software systems | |
| CN113986226A (en) | Micro front end architecture based on qiankun and Web Component and construction method thereof | |
| CN110795139A (en) | Client batch packaging method and device, computer equipment and storage medium | |
| CN112000320A (en) | Automatic code generation method, device, equipment and storage medium | |
| CN110908670A (en) | Method and device for automatically publishing service | |
| CN113254040B (en) | Front-end framework updating method, device, equipment and storage medium | |
| CN115686606A (en) | Method, device, system and medium for displaying item dependency tree | |
| WO2017001417A1 (en) | Tracing dependencies between development artifacts in a software development project | |
| US7100039B2 (en) | Systems and methods for a bootstrap mechanism for software execution | |
| CN106484488B (en) | Integrated cloud Compilation Method and system | |
| US9244706B2 (en) | Command line shell command generation based on schema | |
| CN116166907B (en) | Method and device for developing Web application by using WebAsssembly and service page compiling technology | |
| Queirós | Kaang: a RESTful API generator for the modern web | |
| CN114003257A (en) | Upgrading method and device | |
| CN114816364A (en) | Method, device and application for dynamically generating template file based on Swagger | |
| CN107577476A (en) | A kind of Android system source code difference analysis method, server and medium based on Module Division |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |