CN113254040A - 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
- CN113254040A CN113254040A CN202110607800.XA CN202110607800A CN113254040A CN 113254040 A CN113254040 A CN 113254040A CN 202110607800 A CN202110607800 A CN 202110607800A CN 113254040 A CN113254040 A CN 113254040A
- Authority
- CN
- China
- Prior art keywords
- end framework
- updating
- update
- basic configuration
- file
- 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.)
- Granted
Links
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/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 frameworks, and discloses a front-end framework updating method, device, equipment and storage medium. The method comprises the following steps: acquiring text information sent by a client; according to the text information, a plurality of basic configuration files corresponding to the target front-end framework are collected, and according to the text information, a user-defined configuration file modified by the target front-end framework is configured; classifying each basic configuration file according to the deployment type of each basic configuration file to obtain an update plug-in of a target front-end framework; adding the custom configuration file into an update plug-in to generate 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. The invention realizes the automatic update of the front-end framework and reduces the complexity of the automatic update of the front-end framework.
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 a specific ecological environment, and the deployed front-end framework is basically in a continuously updated state so as to adapt to the technical iteration development requirements of the company. Currently, there are 2 popular front-end frameworks, one is a real-create-real-app scaffold, and the other is vue-cli based on vue, and generally, the scaffold needs to be configured first to realize a set of engineering facilities of the front-end framework shared in a company, then plug-in libraries of all doors in the company are configured in a config.js file of the front-end framework, and then the custom configuration and the general configuration are combined in a webpack merg manner to realize the custom configuration of the front-end framework in each company, so as to meet different requirements in the company. Json, however, needs to manually manage command lines, and the hierarchy of each module in the front-end framework is not obviously split, so that the iterative update process of the front-end framework is complex.
Disclosure of Invention
The invention mainly aims to solve the technical problem that the existing front-end framework is complex in iterative updating process.
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 contains modified content 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 framework, and configuring a user-defined configuration file modified by the target front-end framework according to the text information;
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 to generate 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 framework includes:
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 framework from each configuration parameter;
generating a file calling request according to the 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 calling information is received, analyzing the response information to obtain a plurality of basic configuration files corresponding to the target front-end framework.
Optionally, in a second implementation manner of the first aspect of the present invention, the configuring, according to the text information, the custom configuration file modified by the target front-end framework 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 framework from each configuration parameter;
selecting a corresponding preset configuration template according to the user-defined configuration parameters, and writing assignment information corresponding to the user-defined configuration parameters into the selected configuration template;
and packaging each configuration template to obtain a user-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 the deployment type of each basic configuration file, to obtain an update plug-in of the target front-end framework includes:
extracting plugin identification information corresponding to each basic configuration file from a preset plugin 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 update sub-plug-ins of corresponding types;
and packaging the different types of update sub-plug-ins to obtain the update plug-ins of the target front-end framework.
Optionally, in a fourth implementation manner of the first aspect of the present invention, the extracting, according to the deployment type of each basic configuration file, plugin identification information corresponding to each basic configuration file from a preset plugin 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;
and analyzing the initial identification information, and extracting the 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 invoking a preset identifier reading tool to read initial identifier information in a preset plugin package according to the deployment type of each basic configuration file includes:
calling a preset identification reading tool to read an identification readable file in a preset plug-in package according to the deployment type of each basic configuration file;
and 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, the updating, based on the update script, the current engineering catalog corresponding to the target front-end framework to obtain a new engineering catalog includes:
sequentially verifying whether each updating command in the updating script accords with preset command reference conditions or not, and assembling the updating commands which accord with the command reference conditions to obtain a new updating script;
executing the updating command in the new updating script to obtain a plurality of updating template files, and sequentially comparing each updating template file with the preset engineering catalog corresponding to the target front-end framework;
and copying the updated template file which does not exist in the engineering catalog into the engineering catalog through a corresponding updating interface to obtain a new engineering catalog.
A second aspect of the present invention provides a front-end framework update apparatus, including:
the system comprises an acquisition module, a display module and a display module, wherein the acquisition module is used for acquiring text information sent by a client, and the text information contains modified content 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 framework according to the text information and configuring a user-defined configuration file modified by the target front-end framework 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 framework;
the generating module is used for adding the custom configuration file into the updating plug-in so as to generate a corresponding updating script, wherein the updating script comprises a plurality of updating 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 framework from each configuration parameter; generating a file calling request according to the 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 calling information is received, analyzing the response information to obtain a plurality of basic configuration files corresponding to the target front-end framework.
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 framework from each configuration parameter; selecting a corresponding preset configuration template according to the user-defined configuration parameters, and writing assignment information corresponding to the user-defined configuration parameters into the selected configuration template; and packaging each configuration template to obtain a user-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 the plugin identification information corresponding to each basic configuration file from a preset plugin 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 the update sub-plug-ins of corresponding types;
and the packaging unit is used for packaging each updating sub-plug-in 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;
and analyzing the initial identification information, and extracting the 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 an identification readable file in a preset plug-in package according to the deployment type of each basic configuration file;
and 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 updating command in the updating script accords with preset command reference conditions or not, and assembling the updating commands which accord with the command reference conditions to obtain a new updating script;
executing the updating command in the new updating script to obtain a plurality of updating template files, and sequentially comparing each updating template file with the preset engineering catalog corresponding to the target front-end framework;
and copying the updated template file which does not exist in the engineering catalog into the engineering catalog through a corresponding updating interface to obtain a new engineering catalog.
A third aspect of the present invention provides a front-end framework updating apparatus, including: 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 updating apparatus to execute the front-end framework updating method described above.
A fourth aspect of the present invention provides a computer-readable storage medium having stored therein instructions, which, when run on a computer, cause the computer to execute the above-described front-end framework updating method.
In the technical scheme provided by the invention, a developer writes the modified content of the target front-end framework in a text information mode on an interactive interface, then reads a plurality of basic configuration files of the target front-end framework through the text information, and classifies the basic configuration files to obtain a plurality of updating plug-ins for updating the basic configuration of the target front-end framework; and meanwhile, configuring a custom configuration file of a developer, and adding the custom configuration file into an update plug-in to generate an update script of the target front-end framework, wherein the update script can update the basic configuration of the target front-end framework on one hand and update the custom configuration of the target front-end framework on the other hand, so that the automatic update of the front-end framework is realized, the complexity of the automatic update of the front-end framework is reduced, and the personalization degree of the update of the front-end framework is improved.
Drawings
FIG. 1 is a diagram of a front-end framework updating method according to a first embodiment of the present invention;
FIG. 2 is a diagram of a second embodiment of a front-end framework updating method according to an embodiment of the present invention;
FIG. 3 is a diagram of a front end frame updating apparatus according to a first embodiment of the present invention;
FIG. 4 is a 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 framework updating device in the embodiment of the present invention.
Detailed Description
The embodiment of the invention provides a method, a device, equipment and a storage medium for updating a front-end framework, which are used for acquiring text information sent by a client; according to the text information, a plurality of basic configuration files corresponding to the target front-end framework are collected, and according to the text information, a user-defined configuration file modified by the target front-end framework is configured; classifying each basic configuration file according to the deployment type of each basic configuration file to obtain an update plug-in of a target front-end framework; adding the custom configuration file into an update plug-in to generate 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. The invention realizes the automatic update of the front-end framework and reduces the complexity of the automatic update of the front-end framework.
The terms "first," "second," "third," "fourth," and the like in the description and in the claims, as well as in the drawings, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It will be appreciated that the data so used may be interchanged under appropriate circumstances such that the embodiments described herein may be practiced otherwise than as specifically illustrated or described herein. Furthermore, the terms "comprises," "comprising," or "having," and any variations thereof, are intended to cover non-exclusive inclusions, 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, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
For convenience of understanding, a detailed flow of the embodiment of the present invention is described below, and referring to fig. 1, a first embodiment of a front-end framework updating method in the embodiment of the present invention includes:
101. acquiring text information sent by a client, wherein the text information contains modified content of a target front-end frame to be updated;
it is to be understood that the execution subject of the present invention may be a front-end framework updating apparatus, and may also be a terminal or a server, which is not limited herein. The embodiment of the present invention is described by taking a server as an execution subject.
In this embodiment, when the front-end framework is modified by adding or deleting, the addition or deletion modification can be performed by adding or deleting the plug-in the file. In order to realize the automatic updating of the front-end framework, a developer writes the 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 to a background server through a client; the text information comprises basic configuration and self-defined configuration of the front-end framework.
Specifically, for example, the front-end framework written in JSON (JSON Object Notation) may write the modification content into a preset template, and generate an HTML (Hyper Text Markup Language) file for modifying the plug-in of the file in package.
102. According to the text information, collecting a plurality of basic configuration files corresponding to the target front-end framework, and configuring a user-defined configuration file modified by the target front-end framework according to the text information;
in this embodiment, the text information writes basic configuration and custom configuration of the front-end framework modification content, where the basic configuration is written in advance by a developer and stored in a local folder or a storage server, and at this time, a corresponding basic configuration file may be directly collected according to the modification content corresponding to the basic configuration in the text information, so as to update a plug-in corresponding to 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 to 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 may be searched; the self-defined configuration in the text information is written by a developer into a corresponding command line, and then is written into a position corresponding to a preset self-defined blank table according to the configuration name of the command line, so that the self-defined configuration can be converted into a self-defined configuration file with a unified format.
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 an issuing 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 plug-in module corresponding to devdependences, the basic configuration environment corresponding to the issuing environment may be classified into a plug-in module corresponding to dependences, and the development environment or the issuing environment may be specified by NODE _ ENV ═ depth or NODE _ ENV ═ production. Wherein, the basic configuration file depended on by the devdependences can be only used in a development environment, and a production environment cannot be packed; the basic configuration file dependent on the 'dependencies' can be used not only in the development environment but also in the production environment, and means that the dependent development environment installed in the dependencies can also be used without being installed again in the 'devDependencies', for example, a babel compiling tool is only used in development, only the devDependencies can be matched, and if the basic configuration file is installed in the dependencies, the basic configuration file can also be used in the development environment.
104. Adding the custom configuration file into the update plug-in to generate a corresponding update script, wherein the update script comprises a plurality of update commands;
in this embodiment, the custom configuration file includes script 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 an sh file, and the sh file may be run by a corresponding sh file running tool. In addition, each update command in the update script corresponds to a configuration file of each modified 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. Json is read again according to the update command when the target front-end frame is updated subsequently, so as to refresh the current HTML configuration file.
Furthermore, a commander-is introduced for modifying the target front-end framework so as to inject a custom command, an inquirer script is introduced for interacting with a user, and an ORA-is introduced for prompting feedback, loading, success and error information of updating of the target front-end framework. In addition, the target front-end framework also adds a script for checking update, so that the latest target front-end framework can be ensured to be used by the developer next time.
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 directory records current configuration information of the target front-end framework, and includes content such as babel.config configuration, eslin standard codes, jest test units, hue code submission hooks, nodejs services, configuration files, proxy settings, start services, framework configuration, package.json configuration, and the like corresponding to each functional item. And according to the updating script, acquiring corresponding contents of corresponding functional items from a preset database, copying functional items which do not exist in the current engineering catalog into the current engineering items, and reloading the target front-end framework by adopting new engineering items, so that the target front-end framework can be updated.
In the embodiment of the invention, a developer writes the modified content of the target front-end framework in a text information mode on an interactive interface, then reads a plurality of basic configuration files of the target front-end framework through the text information, and classifies the basic configuration files to obtain a plurality of updating plug-ins for updating the basic configuration of the target front-end framework; and meanwhile, configuring a custom configuration file of a developer, and adding the custom configuration file into an update plug-in to generate an update script of the target front-end framework, wherein the update script can update the basic configuration of the target front-end framework on one hand and update the custom configuration of the target front-end framework on the other hand, so that the automatic update of the front-end framework is realized, the complexity of the automatic update of the front-end framework is reduced, and the personalization degree of the update of the front-end framework is improved.
Referring to fig. 2, a second embodiment of the front-end framework updating method according to the embodiment of the present invention includes:
201. acquiring text information sent by a client, wherein the text information contains modified content 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 basic configuration parameters corresponding to the target front-end framework from each configuration parameter;
203. generating a file calling request according to the 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 response information of the storage space to the file calling information is received, analyzing the response information to obtain a plurality of basic configuration files corresponding to the target front-end framework;
in this embodiment, in the modification content of the basic configuration in the text information, configuration parameters, such as initialization data, module export, a monitor, a life cycle, and the like, are written, and then, assignment information is written for each configuration parameter, for example, for the life cycle of the page, the assignment information may include: the assignment information may include, for example, for the listener, the name of the monitored object, the number of the monitored objects, the triggering condition of the monitored object, and the like. For the basic configuration which does not need to be modified, the assignment information of the corresponding configuration parameters in the text message is empty, the basic configuration which needs to be modified, and the corresponding configuration parameters in the text message are compiled with the corresponding assignment information, so that the configuration parameters which are compiled with the assignment information can be selected as the basic configuration parameters.
In this embodiment, after obtaining the basic assignment information corresponding to the basic configuration, the basic configuration that the front-end framework needs to modify may be determined, and the basic assignment information is written as the configuration request content into the template of the preset file invocation request, so that a file invocation request, for example, an Ajax request, may be generated, and JSON data may be requested to be loaded through an HTTP GET method. And finally, retrieving a corresponding basic configuration file in a storage space of the target front-end framework according to the basic assignment information in the file calling request, and returning the basic configuration file 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 framework from each configuration parameter;
206. selecting a corresponding preset configuration template according to the user-defined configuration parameters, and writing assignment information corresponding to the user-defined configuration parameters into the selected configuration template;
207. packaging each configuration template to obtain a user-defined configuration file modified by the target front-end framework;
in this embodiment, the customized configuration parameters are written in the modified content of the customized configuration in the text information, and for different customized configuration parameters, corresponding configuration templates are associated with the customized configuration parameters to perform normalized processing on the customized configuration parameters, where the configuration templates include configuration names of each customized configuration and configuration parameters included therein, match the corresponding configuration names in the configuration templates, and sequentially fill assignment information in the customized configuration parameters into the configuration templates, and for configuration parameters that are not assigned, the configuration templates may be automatically set to be empty or assigned according to default settings. And after the assignment information corresponding to the user-defined configuration parameters is written into each configuration template, packaging each configuration template into a user-defined configuration file.
208. Extracting plugin identification information corresponding to each basic configuration file from a preset plugin 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 update sub-plug-ins of corresponding types;
210. packaging each updating sub-plug-in of different types to obtain an 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 basic configuration file. The plug-in identification information may include at least any one of an application name, a base configuration file name, a version number, and the like, for example, the plug-in identification information of the base configuration file may include only the application name, or may include three items of the application name, a package name, and a version number.
The manifest file (e.g., manifest. xml) of the basic configuration file contains the plug-in identification information, and the plug-in initial identification information specified by the basic configuration file can be extracted from the manifest file. Preferably, an identification information reading tool may be invoked to obtain the plug-in initial identification information, wherein the identification information reading tool refers to a tool provided by the smart operating system for reading the plug-in initial identification information. The identification information reading tool can obtain 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 (android debug 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 basic configuration file, and the configured signature file is inserted into the plug-in package. 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 can obtain the signature information according to the signature file of each updating sub-plug-in and compare the signature information with the preset signature information. If so, the host may allow the update sub-plug-in to run. If not, the host does not allow the update plugin 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 for the updated sub-plug-in may also be generated based on various signature file generation algorithms.
Specifically, the ways of inserting the configured signature file into the update sub-plug-in include, but are not limited to, the following 3:
1) automatically distributing or generating a signature file for the updating sub-plug-in, and inserting the distributed or generated signature file into the updating sub-plug-in;
2) acquiring a signature file for updating the sub-plug-in from the first signature device, and inserting the acquired signature file into the plug-in package;
3) the updated sub-plug-in is provided to a second signing device, a signature file is configured for the updated sub-plug-in by the second signing device, the signature file is inserted into the plug-in package, and then the updated sub-plug-in into which the signature file is inserted can be received from the second signing device.
The first signature device and the second signature device can be arranged in any equipment. For example, the first signature device may be installed in the host or the network device. The first signature device can distribute or generate a signature file for the updating sub-plug-in and provide the signature file for the host; the second signing means 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 obtain the signature file for the update sub-plug-in from the first signing device and insert the obtained signature file into the update sub-plug-in. Specifically, the unified signature file may be directly obtained from the first signature apparatus, or the updated sub-plug-in or the plug-in identification information thereof may be sent to the first signature apparatus. Accordingly, the first signature apparatus may assign or generate a signature file according to the received update child plug-in or the plug-in identification information thereof. Subsequently, the first signing device may return the generated signature file to the host.
And finally, storing the update sub-plug-in into which the signature file is inserted to a specified path, so that the update sub-plug-in is associated with the host to obtain the update 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 into which the signature file has been inserted may be saved to the path specified by the host. Here, the current package name of the update sub-plug-in inserted into the signature file may be compared with the package name in the manifest file (manifest. xml) of the basic configuration file, and if the current package name of the update sub-plug-in inserted into the signature file is consistent with the package name in the manifest file (manifest. xml), the update sub-plug-in inserted into the signature file may be directly saved to the path specified by the host.
Preferably, if the current package name of the updated sub-plug-in is not consistent with the package name in the manifest file of the basic configuration file, the current package name of the updated sub-plug-in may be renamed to the package name in the manifest file, and the updated sub-plug-in into which the signature file is inserted is saved to the path specified 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) and analyzing the initial identification information, and extracting the 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 configuration file, as well as other redundant information. In the subsequent step, the initial identification information of the plug-in needs to be analyzed to obtain the identification information of the plug-in specified by the basic configuration file. Preferably, the plug-in initial identification 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 so that it is resolvable. Wherein, the initial identification information of the plug-in presented in the dialog box of the command line can not be analyzed, and the initial identification information of the plug-in saved in the readable file can be analyzed.
Further, the reading mode of the initial identification information may also adopt the following mode:
(1) calling a preset identification reading tool to read an identification readable file in a 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 configuration file is typically saved in the initial identification information in the form of a "name/value" pair. For example, a preset "name" character string may be searched in the initial identification information to obtain a "value" character string corresponding to the "name" character string. The character string representing the "value" is the plug-in identification information. For example, the initial identification information may be searched for according to a "name" character string — a "package name", where a "value" character string corresponding to the "name" character string is the package name, which is the package identification information specified by the host; for another example, the initial identification information may be searched for according to a "name" string — a "version", where a "value" string corresponding to the "name" string is the plug-in identification information — a version number.
211. Adding the custom configuration file into the update plug-in to generate 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 updating command in the updating script accords with preset command reference conditions or not, and assembling the updating commands which accord with the command reference conditions to obtain a new updating script;
(2) executing the updating command in the new updating script to obtain a plurality of updating template files, and sequentially comparing each updating template file with the preset engineering catalog corresponding to the target front-end framework;
(3) and copying the updated template file which does not exist in the engineering catalog into the engineering catalog through a corresponding updating interface to obtain a new engineering catalog.
In this embodiment, the update script includes a plurality of update commands, an entry for executing the script may be determined according to a main method in package.
Specifically, for example, UNIX command line options typically include a dash followed by one or more lower case letters; the GNU tool adds a double dash followed by a complete word or compound word, as exemplified below:
help, i.e. give usage information, then exit, UNIX command line "-h", GNU tool "- -hellp";
version, i.e. the real program version number, and then quit, the UNIX command line is "-v", the GNU tool is "- -version";
all, i.e., all information or operations showing all parameters, UNIX command line "-a", GNU tool "- -all";
list, i.e. list files or parameters, do not take other actions, UNIX command line is "-l", GNU tool is "- -list";
quiet, i.e., suppress stdout, UNIX command line is "-q", GNU tool is "- - -jet";
recursion, i.e., recursive operation (containing subdirectory trees), UNIX command line is "-R" or "-R", GNU tool is "- - -recursive";
in this embodiment, the update template file is written with a babel.config configuration, an esint specification code, a jest test unit, a hue code submission hook, a nodejs service, a configuration file, an agent setting, a start service, a frame configuration, a package.json configuration, and the like corresponding to each functional item, and if the update template file does not exist in the preset engineering directory, the corresponding update template file may be determined as the modified content, and the update template file is copied to the engineering directory, that is, the modified content may be presented on the target front-end frame.
In the embodiment of the invention, the configuration of the basic configuration file and the user-defined configuration file is carried out according to the text information, the updating script updated by the current front-end framework is generated by the configuration of the basic configuration file and the user-defined configuration file, and the updating of the target front-end framework can be realized by directly executing the updating script at the later stage.
With reference to fig. 3, the method for updating a front end frame according to the embodiment of the present invention is described above, and a front end frame updating apparatus according to the embodiment of the present invention is described below, where a first embodiment of the front end frame updating apparatus according to 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 framework to be updated;
a configuration module 302, configured to collect a plurality of basic configuration files corresponding to the target front-end framework according to the text information, and configure a custom configuration file modified by the target front-end framework according to the text information;
the classification module 303 is configured to classify each basic configuration file according to the 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 to generate a corresponding update script, where the update script includes multiple update commands;
an updating module 305, configured to update the current engineering catalog corresponding to the target front-end framework based on the update script, obtain a new engineering catalog, and perform updating on the target front-end framework by using the new engineering catalog.
In the embodiment of the invention, a developer writes the modified content of the target front-end framework in a text information mode on an interactive interface, then reads a plurality of basic configuration files of the target front-end framework through the text information, and classifies the basic configuration files to obtain a plurality of updating plug-ins for updating the basic configuration of the target front-end framework; and meanwhile, configuring a custom configuration file of a developer, and adding the custom configuration file into an update plug-in to generate an update script of the target front-end framework, wherein the update script can update the basic configuration of the target front-end framework on one hand and update the custom configuration of the target front-end framework on the other hand, so that the automatic update of the front-end framework is realized, the complexity of the automatic update of the front-end framework is reduced, and the personalization degree of the update of the front-end framework is improved.
Referring to fig. 4, a second embodiment of the front end frame updating apparatus according to 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 framework to be updated;
a configuration module 302, configured to collect a plurality of basic configuration files corresponding to the target front-end framework according to the text information, and configure a custom configuration file modified by the target front-end framework according to the text information;
the classification module 303 is configured to classify each basic configuration file according to the 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 to generate a corresponding update script, where the update script includes multiple update commands;
an updating module 305, configured to update the current engineering catalog corresponding to the target front-end framework based on the update script, obtain a new engineering catalog, and perform 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 basic configuration parameters corresponding to the target front-end framework from each configuration parameter;
generating a file calling request according to the 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 calling information is received, analyzing the response information to obtain a plurality of basic configuration files corresponding to the target front-end framework.
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 framework from each configuration parameter;
selecting a corresponding preset configuration template according to the user-defined configuration parameters, and writing assignment information corresponding to the user-defined configuration parameters into the selected configuration template;
and packaging each configuration template to obtain a user-defined configuration file modified by the target front-end framework.
Specifically, the classification module 303 includes:
an extracting unit 3031, configured to extract, according to the deployment type of each basic configuration file, plugin identification information corresponding to each basic configuration file from a preset plugin package;
a configuration unit 3032, configured to configure, according to the plug-in identification information, signature files corresponding to the basic configuration files, and insert the signature files into the basic configuration files to obtain update sub-plugs of corresponding types;
an encapsulating unit 3033, configured to encapsulate each update sub-plug-in of the different types, so as 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;
and analyzing the initial identification information, and extracting the 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 an identification readable file in a preset plug-in package according to the deployment type of each basic configuration file;
and 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 update unit 3052, where the first update unit 3051 is configured to:
sequentially verifying whether each updating command in the updating script accords with preset command reference conditions or not, and assembling the updating commands which accord with the command reference conditions to obtain a new updating script;
executing the updating command in the new updating script to obtain a plurality of updating template files, and sequentially comparing each updating template file with the preset engineering catalog corresponding to the target front-end framework;
and copying the updated template file which does not exist in the engineering catalog into the engineering catalog through a corresponding updating interface to obtain a new engineering catalog.
In the embodiment of the invention, the configuration of the basic configuration file and the user-defined configuration file is carried out according to the text information, the updating script updated by the current front-end framework is generated by the configuration of the basic configuration file and the user-defined configuration file, and the updating of the target front-end framework can be realized by directly executing the updating script at the later stage.
Fig. 3 and fig. 4 describe the front end framework updating apparatus in the embodiment of the present invention in detail from the perspective of the modular functional entity, and the front end framework updating device in the embodiment of the present invention is described in detail from the perspective of hardware processing.
Fig. 5 is a schematic structural diagram of a front-end framework updating apparatus according to an embodiment of the present invention, where the front-end framework updating apparatus 500 may generate relatively large differences due to different configurations or performances, and may include one or more processors (CPUs) 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) for storing applications 533 or data 532. Memory 520 and storage media 530 may be, among other things, transient 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 for the front-end framework update apparatus 500. Still further, the processor 510 may be configured to communicate with the storage medium 530, and execute a series of instruction operations in the storage medium 530 on the front end framework updating apparatus 500.
The front-end framework update 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 Server, Mac OS X, Unix, Linux, FreeBSD, and the like. It will be understood by those skilled in the art that the front end frame refreshing apparatus configuration shown in fig. 5 does not constitute a limitation of the front end frame refreshing apparatus, and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.
The present invention further provides a front-end framework updating apparatus, where the front-end framework updating apparatus includes a memory and a processor, where the memory stores computer-readable instructions, and when the computer-readable instructions are executed by the processor, the processor is caused to execute the steps of the front-end framework updating method in the foregoing embodiments.
The present invention also provides a computer-readable storage medium, which may be a non-volatile computer-readable storage medium, and which may also be a volatile computer-readable storage medium, having stored therein instructions, which, when run on a computer, cause the computer to perform the steps of the front-end framework updating method.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
The above-mentioned embodiments are only used for illustrating the technical solutions of the present invention, and not for limiting the same; although the present 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 solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.
Claims (10)
1. A front-end framework updating method, characterized in that the front-end framework updating method comprises:
acquiring text information sent by a client, wherein the text information contains modified content 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 framework, and configuring a user-defined configuration file modified by the target front-end framework according to the text information;
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 front-end framework updating method of claim 1, wherein the gathering a plurality of basic profiles 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 basic configuration parameters corresponding to the target front-end framework from each configuration parameter;
generating a file calling request according to the 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 calling information is received, analyzing the response information to obtain a plurality of basic configuration files corresponding to the target front-end framework.
3. The front-end framework updating method of claim 1, wherein configuring the custom configuration file modified by the target front-end framework according to the text message 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 framework from each configuration parameter;
selecting a corresponding preset configuration template according to the user-defined configuration parameters, and writing assignment information corresponding to the user-defined configuration parameters into the selected configuration template;
and packaging each configuration template to obtain a user-defined configuration file modified by the target front-end framework.
4. The front-end framework updating method 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 plugin identification information corresponding to each basic configuration file from a preset plugin 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 update sub-plug-ins of corresponding types;
and packaging the different types of update sub-plug-ins to obtain the update plug-ins of the target front-end framework.
5. The front-end framework updating method according to claim 4, wherein the extracting, according to the deployment type of each basic configuration file, the plugin identification information corresponding to each basic configuration file from a preset plugin package includes:
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;
and analyzing the initial identification information, and extracting the plug-in identification information corresponding to each basic configuration file from the analyzed initial identification information.
6. The front-end framework updating method according to claim 5, wherein the calling a preset identification reading tool to read initial identification information in a preset plugin package according to the deployment type of each basic configuration file comprises:
calling a preset identification reading tool to read an identification readable file in a preset plug-in package according to the deployment type of each basic configuration file;
and 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.
7. The front-end framework updating method according to any one of claims 1 to 6, wherein the updating the current engineering catalog corresponding to the target front-end framework based on the update script to obtain a new engineering catalog comprises:
sequentially verifying whether each updating command in the updating script accords with preset command reference conditions or not, and assembling the updating commands which accord with the command reference conditions to obtain a new updating script;
executing the updating command in the new updating script to obtain a plurality of updating template files, and sequentially comparing each updating template file with the preset engineering catalog corresponding to the target front-end framework;
and copying the updated template file which does not exist in the engineering catalog into the engineering catalog through a corresponding updating interface to obtain a new engineering catalog.
8. A front-end framework update apparatus, the front-end framework update apparatus comprising:
the system comprises an acquisition module, a display module and a display module, wherein the acquisition module is used for acquiring text information sent by a client, and the text information contains modified content 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 framework according to the text information and configuring a user-defined configuration file modified by the target front-end framework 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 framework;
the generating module is used for adding the custom configuration file into the updating plug-in so as to generate a corresponding updating script, wherein the updating script comprises a plurality of updating 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, characterized in that the front-end framework update apparatus comprises: 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 framework update apparatus to perform the front end framework update method of any of claims 1-7.
10. A computer-readable storage medium, having stored thereon a computer program, wherein the computer program, when executed by a processor, implements the front-end framework updating method as claimed in any one 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 true CN113254040A (en) | 2021-08-13 |
| CN113254040B 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) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114756217A (en) * | 2022-03-22 | 2022-07-15 | 北京云枢创新软件技术有限公司 | 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 |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114756217A (en) * | 2022-03-22 | 2022-07-15 | 北京云枢创新软件技术有限公司 | Plug-in-based script generation system |
| CN114756217B (en) * | 2022-03-22 | 2022-10-25 | 北京云枢创新软件技术有限公司 | Plug-in based script generation system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113254040B (en) | 2023-10-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104793946B (en) | Dispositions method and system are applied based on cloud computing platform | |
| JP6755954B2 (en) | Interface data presentation method and equipment | |
| KR101314949B1 (en) | Integration environment generator | |
| US20150082298A1 (en) | Packaging and deploying hybrid applications | |
| US9424003B1 (en) | Schema-less system output object parser and code generator | |
| CN111679965A (en) | Automatic testing method and device, computer equipment and storage medium | |
| CN101002174B (en) | Method for loading software with an intermediate object oriented language in a portable device | |
| CN111680253B (en) | Page application data packet generation method and device, computer equipment and storage medium | |
| WO2004086222A2 (en) | Development of software systems | |
| CN109032631B (en) | Application program patch package obtaining method and device, computer equipment and storage medium | |
| CN107015903B (en) | Interface test program generation method and device and electronic equipment | |
| CN110795139A (en) | Client batch packaging method and device, computer equipment and storage medium | |
| CN112000320A (en) | Automatic code generation method, device, equipment and storage medium | |
| CN115686606A (en) | Method, device, system and medium for displaying item dependency tree | |
| EP3314409A1 (en) | Tracing dependencies between development artifacts in a software development project | |
| CN113254040B (en) | Front-end framework updating method, device, equipment and storage medium | |
| US7100039B2 (en) | Systems and methods for a bootstrap mechanism for software execution | |
| CN111309332A (en) | File content on-demand loading method and device, electronic equipment and storage medium | |
| CN112947896B (en) | Directed graph-based component dependency analysis method | |
| CN110806891B (en) | Method and device for generating software version of embedded device | |
| CN115794214B (en) | Application module metadata management method, device, storage medium and apparatus | |
| CN113448793A (en) | System monitoring method and device compatible with multiple operating systems | |
| CN114816364A (en) | Method, device and application for dynamically generating template file based on Swagger | |
| CN111930387B (en) | Integration method and device of integration package, electronic equipment and storage medium | |
| CN114398102A (en) | Application package generation method and device, compiling server and computer readable storage medium |
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 |