CN112965733A - Component library updating method and device, electronic equipment and readable storage medium - Google Patents
Component library updating method and device, electronic equipment and readable storage medium Download PDFInfo
- Publication number
- CN112965733A CN112965733A CN202110303244.7A CN202110303244A CN112965733A CN 112965733 A CN112965733 A CN 112965733A CN 202110303244 A CN202110303244 A CN 202110303244A CN 112965733 A CN112965733 A CN 112965733A
- Authority
- CN
- China
- Prior art keywords
- sub
- application
- component
- component library
- version
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
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/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Abstract
The invention provides a component library updating method and device, electronic equipment and a readable storage medium, and relates to the technical field of computers. The method is applied to a micro-front-end system consisting of a plurality of sub-applications, and comprises the following steps: newly building a second sub-application, wherein the second sub-application is provided with a first component library of a second version; the first component library comprises a plurality of components; deriving a first target path from the second version of the first component library to the second sub-application; and acquiring at least one target component from the first component library of the second version according to the first target path, and exporting the target component to a target sub-application in the plurality of sub-applications. The problem of system compatibility when the component library is subjected to large-version incompatible updating in the prior art is solved.
Description
Technical Field
The embodiment of the invention relates to the technical field of computers, in particular to a component library updating method and device, electronic equipment and a readable storage medium.
Background
In the prior art, a software system has a general functional module, and a front-end system has a general component library, however, when a large-version incompatible update is performed on a dependent component library, the front-end system cannot directly update the component library, and the system is unavailable due to incompatibility.
In the prior art, a new version of a component library is used for software reconstruction and business codes are modified, so that when the use rule of the new version is met for component upgrading, the cost is extremely high and the system cannot be reused when the system is large and complex, and then the reconstruction is required to be tested again when a large version is updated again, and a leak is easily introduced; if the code analysis tool provided by the official is adopted to automatically modify the codes and then manually adjust the part which cannot be modified, the problem that the cost is low but the change is still needed manually exists, and if the code analysis tool provided by the official is not strong enough, the business codes can be modified into a whole grain of grains, and the problem that a leak is introduced also exists.
Disclosure of Invention
The embodiment of the invention provides a component library updating method and device, electronic equipment and a readable storage medium, and aims to solve the problem of system compatibility when a large-version incompatible update is carried out on a component library in the prior art.
In order to solve the technical problem, the invention is realized as follows:
in a first aspect, an embodiment of the present invention provides a component library updating method, which is applied to a micro-front-end system configured by multiple sub-applications, where the method includes:
newly building a second sub-application, wherein the second sub-application is provided with a first component library of a second version; the first component library comprises a plurality of components;
deriving a first target path from the second version of the first component library to the second sub-application;
and acquiring at least one target component from the first component library of the second version according to the first target path, and exporting the target component to a target sub-application in the plurality of sub-applications.
Optionally, the target sub-application is a first sub-application, and the first sub-application is installed with a first component library of a first version.
Optionally, the target sub-application is a third sub-application, and the first component library is not installed in the third sub-application.
Optionally, the method further includes:
exporting a first version of a first component library from the first sub-application to a second target path of the first sub-application;
if the second sub-application needs to use the component of the first version, the method further includes:
and acquiring at least one target component from the first component library of the first version according to the second target path, and importing the target component to the second sub-application for use.
In a second aspect, an embodiment of the present invention further provides a component library updating apparatus, including:
the component library module is used for newly building a second sub application, and the second sub application is provided with a first component library of a second version; the first component library comprises a plurality of components;
an execution module to export the second version of the first component library to a first target path of the second sub-application;
and the export module is used for acquiring at least one target component from the first component library of the second version according to the first target path and exporting the target component to a target sub-application in the plurality of sub-applications.
Optionally, the target sub-application is a first sub-application, and the first sub-application is installed with a first component library of a first version.
Optionally, the target sub-application is a third sub-application, and the first component library is not installed in the third sub-application.
Optionally, the system further comprises an importing module;
the execution module is further configured to export a first component library of a first version from the first sub-application to a second target path of the first sub-application;
if the component of the first version needs to be used in the second sub-application, the importing module is configured to obtain at least one target component from the first component library of the first version according to the second target path, and import the target component into the second sub-application.
In a third aspect, an embodiment of the present invention further provides an electronic device, including: a processor, a memory and a program stored on the memory and executable on the processor, which program, when executed by the processor, carries out the steps of the component library update method according to any one of the first aspect.
In a fourth aspect, the embodiment of the present invention further provides a readable storage medium, where a program is stored, and the program, when executed by a processor, implements the steps of the component library updating method according to any one of the first aspect.
In the embodiment of the invention, the micro front-end system comprises a plurality of sub-applications, a second sub-application is newly built, a first component library of a second version is installed in the second sub-application, a first component library of the second version is led out to a first target path, at least one target component is obtained from the first component library of the second version according to the first target path, the target component is led out to the target sub-application, and the component library of the sub-application of the component comprising the first component library in the micro front-end system is updated to the second version; according to the component library updating method realized by the scheme, the micro-front-end system can be completely compatible with the old version codes, the coexistence of multiple versions of the first component library of the same micro-front-end system is realized, the upgrading of the component library can be realized on the premise of not modifying the old codes, no leak is introduced before and after the upgrading of the versions, the development period is short, the real-time cost is low, and the upgrading of the component library is quick.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:
fig. 1 is a schematic flow chart of a component library updating method according to an embodiment of the present invention;
fig. 2 is a second schematic flow chart of a component library updating method according to an embodiment of the present invention;
fig. 3 is a schematic structural diagram of a component library updating apparatus according to an embodiment of the present invention;
fig. 4 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Referring to fig. 1, fig. 1 is a schematic flow chart illustrating a component library updating method according to an embodiment of the present invention;
the embodiment of the invention provides a component library updating method which is applied to a micro front-end system consisting of a plurality of sub-applications, and the method comprises the following steps:
step 11: newly building a second sub-application, wherein the second sub-application is provided with a first component library of a second version; the first component library comprises a plurality of components;
step 12: deriving a first target path from the second version of the first component library to the second sub-application;
step 13: and acquiring at least one target component from the first component library of the second version according to the first target path, and exporting the target component to a target sub-application in the plurality of sub-applications.
In the embodiment of the invention, the micro front-end system comprises a plurality of sub-applications, a second sub-application is newly built, a first component library of a second version is installed in the second sub-application, a first component library of the second version is led out to a first target path, at least one target component is obtained from the first component library of the second version according to the first target path, the target component is led out to the target sub-application, and the component library of the sub-application of the component comprising the first component library in the micro front-end system is updated to the second version; according to the component library updating method realized by the scheme, the micro-front-end system can be completely compatible with the old version codes, the coexistence of multiple versions of the first component library of the same micro-front-end system is realized, the upgrading of the component library can be realized on the premise of not modifying the old codes, no leak is introduced before and after the upgrading of the versions, the development period is short, the real-time cost is low, and the upgrading of the component library is quick.
In some embodiments of the invention, optionally, each sub-application is installed with multiple component libraries.
In some embodiments of the present invention, optionally, the software of the non-micro front-end system architecture may be converted into a micro front-end system architecture, and then the component library is updated according to the method.
In the embodiment of the invention, the component library needing to be upgraded in the micro-front-end system comprises a plurality of component libraries, the target component is obtained by obtaining the target path of the component library, and the target component is led to the target sub-application to realize the version upgrade of the second component library of the target sub-application.
In some embodiments of the present invention, optionally, a plurality of versions of the first component library exist in the micro-front-end system, and each target sub-application may obtain and import a component of a corresponding version according to a target path exported by the second sub-application installed with a component library of a different version, so as to implement component upgrade of a specific version of a specific sub-application.
In some embodiments of the present invention, optionally, the target sub-application is a first sub-application, and the first sub-application is installed with a first component library of a first version.
In the embodiment of the invention, when the target sub-application is provided with the first sub-application of the first component library of the first version, the first sub-application can obtain the target component from the first component library of the second version and import the target component to realize the functional use of the component of the second version; when the first sub application needs to use the component in the first component library of the first version, calling the component library of the first sub application to realize the operation, and when the component in the first component library of the second version needs to be used, importing a target component or a target component package from the second sub application provided with the first component library of the second version; the complete compatibility of the multi-version components on the same sub-application is realized, the component libraries of different versions are also placed in different sub-applications for isolation, and the seamless switching from the first version to the second version is realized on the premise of not modifying any first version service codes; the method has the advantages of no vulnerability introduced before and after version upgrading, short development period, low real-time cost and quick component library upgrading.
In some embodiments of the present invention, optionally, the target sub-application is a third sub-application, and the third sub-application does not install the first component library of the first version.
In the embodiment of the invention, when the target sub-application is the third sub-application without the first component library, the target component can be directly obtained from the first component library of the second version through the first target path and is imported, so that the application of the component of the second version on the third sub-application is realized.
In some embodiments of the present invention, optionally, further comprising:
exporting a first component library of a first version from the first sub-application to a second target path of the first sub-application;
if the second sub-application needs to use the component of the first version, the method further includes:
and acquiring at least one target component from the first component library of the first version according to the second target path, and importing the target component to the second sub-application for use.
Specifically, when the old version of the component library is installed in the newly created second sub-application, the second target path of the first sub-application is acquired, and the second sub-application is imported into the second sub-application, so that the use of the new version of the component in the second sub-application is realized, wherein the new version of the component library is installed in the first sub-application. In this case, if the second sub-application needs to use the component of the old version, the component in the component library of the old version installed by the second sub-application may be called.
In the embodiment of the invention, when the target sub-application is provided with the first sub-application of the first component library of the first version, the second sub-application can realize the functional use of the first version component by acquiring the target component from the first component library of the first version and importing the target component; when the second sub application needs to use the component in the first component library of the second version, the component library of the second sub application can be called, and when the component in the first component library of the first version needs to be used, the target component or the target component package is led in from the first sub application provided with the first component library of the first version; the complete compatibility of the multi-version components on the same sub-application is realized, the component libraries of different versions are also placed in different sub-applications for isolation, and the seamless switching from the first version to the second version is realized on the premise of not modifying any first version service codes; the method has the advantages of no vulnerability introduced before and after version upgrading, short development period, low real-time cost and quick component library upgrading.
In some embodiments of the present invention, optionally, the obtaining at least one target component from the first component library of the second version according to the first target path, and importing the target component to a target sub-application of the plurality of sub-applications includes:
and acquiring a plurality of target components from the first component library of the second version according to the first target path to form a target component package, and importing the target component package to a target sub-application in the plurality of sub-applications.
In the embodiment of the invention, the exported component packages can be mutually introduced among the multiple sub-applications of the micro-front-end system, the target sub-application acquires the multiple components from the first component library of the second version through the first target path shared by the second sub-application to form the target component package, and the target component package is introduced to realize the updating of the component version of the target sub-application, so that the old code does not need to be modified, no leak is introduced before and after the version is updated, the development period is short, the real-time cost is low, and the component library is updated quickly.
Specifically, referring to fig. 2, fig. 2 is a second schematic flow chart of the component library updating method according to the embodiment of the present invention; the first component library is an Ant component library (a set of enterprise-level interactive Design language and exact component libraries, which is called Ant Design entirely), the second sub-application is an antdv4-app sub-application, a sub-application of the Ant Design component library is installed on the second sub-application, the versions of the Ant Design component library comprise a v1-v4 version, a first component library 211 with an antd v4 version as a second version, and a first component library 221 with an antd v3 version as a first version.
Wherein the micro-front-end system 20 is composed of a plurality of sub-applications, including a second sub-application 21 and a target sub-application 22;
the second sub-application 21 is provided with a second version of the first component library 211; the target sub-application 22 has a second version of the first component library 221 installed thereon.
The exported component packages may be imported into each other among the sub-applications.
When the second sub-application 21 needs to call the first component of the first version, step 202 is executed: exporting a first component library of a first version from the first sub-application to a second target path of the first sub-application; and acquiring at least one target component from the first component library of the first version according to the second target path, and importing the target component to the second sub-application for use.
When the first sub-application 22 needs to call the first component of the second version, step 201 is executed: deriving a first target path from the second sub-application to the second sub-application from the first component library of the second version; and acquiring at least one target component from the first component library of the second version according to the first target path, and exporting the target component to the first sub-application for use.
In the embodiment of the invention, the Ant Design of the v4 version exported by the antdv4-app is directly imported and directly used when a new version is used, the original code using the Ant Design of the v3 version of a business sub application does not need to be modified, the original antdv3 version of the business sub application is still used, the coexistence of multiple versions of the component library v3 v4 is finally realized, and the coexistence of multiple versions of the v3 v4 v5 can be realized in the same way when the next incompatible upgrade of the v5 version exists.
In some embodiments of the present invention, the old version component library installed on the second sub application may be uninstalled, and then the new version component library is installed into the second sub application, at this time, the use of the old version component in the second sub application is implemented by importing a target component that obtains the old version from other sub applications in which the old version component library is installed (i.e., modifying the reference path for all references that use the old version component).
Referring to fig. 3, fig. 3 is a schematic structural diagram of a component library updating apparatus according to an embodiment of the present invention; the embodiment of the present invention further provides a device for updating a component library, including:
the component library module 31 is configured to create a second sub-application, where the second sub-application is installed with a first component library of a second version; the first component library comprises a plurality of components;
an execution module 32, configured to derive a first target path from the second version of the first component library to the second sub-application;
and an export module 33, configured to obtain at least one target component from the first component library of the second version according to the first target path, and export the target component to a target sub-application of the multiple sub-applications.
In the embodiment of the invention, the component library updating device updates the component library of the sub-application containing the components of the first component library in the micro front-end system to the second version by newly building the second sub-application, installing the first component library of the second version into the second sub-application, exporting the first component library of the second version to the first target path, acquiring at least one target component from the first component library of the second version according to the first target path, exporting the target component to the target sub-application; according to the component library updating method realized by the scheme, the micro-front-end system can be completely compatible with the old version codes, the coexistence of multiple versions of the first component library of the same micro-front-end system is realized, the upgrading of the component library can be realized on the premise of not modifying the old codes, no leak is introduced before and after the upgrading of the versions, the development period is short, the real-time cost is low, and the upgrading of the component library is quick.
In some embodiments of the present invention, optionally, the target sub-application is a first sub-application, and the first sub-application is installed with a first component library of a first version.
In the embodiment of the invention, when the target sub-application is provided with the first sub-application of the first component library of the first version, the first sub-application can obtain the target component from the first component library of the second version and import the target component to realize the functional use of the component of the second version; when the first sub application needs to use the component in the first component library of the first version, calling the component library of the first sub application to realize the operation, and when the component in the first component library of the second version needs to be used, importing a target component or a target component package from the second sub application provided with the first component library of the second version; the complete compatibility of the multi-version components on the same sub-application is realized, the component libraries of different versions are also placed in different sub-applications for isolation, and the seamless switching from the first version to the second version is realized on the premise of not modifying any first version service codes; the method has the advantages of no vulnerability introduced before and after version upgrading, short development period, low real-time cost and quick component library upgrading.
In some embodiments of the present invention, optionally, the target sub-application is a third sub-application, and the third sub-application does not install the first component library of the first version.
In the embodiment of the invention, when the target sub-application is the third sub-application without the first component library, the target component can be directly obtained from the first component library of the second version through the first target path and is imported, so that the application of the component of the second version on the third sub-application is realized.
In some embodiments of the present invention, optionally, an import module 34 is further included;
the execution module 32 is further configured to export a first component library of a first version from the first sub-application to a second target path of the first sub-application;
if the component of the first version needs to be used in the second sub-application, the importing module 34 is configured to obtain at least one target component from the first component library of the first version according to the second target path, and import the target component into the second sub-application.
Specifically, when the old version of the component library is installed in the newly created second sub-application, the second target path of the first sub-application is acquired, and the second sub-application is imported into the second sub-application, so that the use of the new version of the component in the second sub-application is realized, wherein the new version of the component library is installed in the first sub-application. In this case, if the second sub-application needs to use the component of the old version, the component in the component library of the old version installed by the second sub-application may be called. In the embodiment of the invention, when the target sub-application is provided with the first sub-application of the first component library of the first version, the second sub-application can obtain the target component from the first component library of the first version and can be led in to realize the functional use of the first version component; when the second sub application needs to use the component in the first component library of the second version, the component library of the second sub application can be called, and when the component in the first component library of the first version needs to be used, the target component or the target component package is led in from the first sub application provided with the first component library of the first version; the complete compatibility of the multi-version components on the same sub-application is realized, the component libraries of different versions are also placed in different sub-applications for isolation, and the seamless switching from the first version to the second version is realized on the premise of not modifying any first version service codes; the method has the advantages of no vulnerability introduced before and after version upgrading, short development period, low real-time cost and quick component library upgrading.
Referring to fig. 4, fig. 4 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.
The electronic device 40 includes: the processor 41, the memory 42, and the program stored in the memory 42 and capable of running on the processor 41, where the program, when executed by the processor 41, implements each process of the embodiment of the component library updating method as described above, and can achieve the same technical effect, and in order to avoid repetition, the details are not repeated here.
The embodiment of the present invention further provides a readable storage medium, where a computer program is stored on the readable storage medium, and when the computer program is executed by a processor, the computer program implements each process of any one of the embodiments of the component library updating method described above, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.
The computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.
While the present invention has been described with reference to the embodiments shown in the drawings, the present invention is not limited to the embodiments, which are illustrative and not restrictive, and it will be apparent to those skilled in the art that various changes and modifications can be made therein without departing from the spirit and scope of the invention as defined in the appended claims.
Claims (10)
1. A component library update method applied to a micro-front-end system composed of a plurality of sub-applications, the method comprising:
newly building a second sub-application, wherein the second sub-application is provided with a first component library of a second version; the first component library comprises a plurality of components;
deriving a first target path from the second version of the first component library to the second sub-application;
and acquiring at least one target component from the first component library of the second version according to the first target path, and exporting the target component to a target sub-application in the plurality of sub-applications.
2. The component library updating method according to claim 1, wherein the target sub-application is a first sub-application, and the first sub-application is installed with a first version of the first component library.
3. The component library updating method according to claim 1, wherein the target sub-application is a third sub-application, and the first component library is not installed in the third sub-application.
4. The component library update method according to claim 2, further comprising:
exporting a first component library of a first version from the first sub-application to a second target path of the first sub-application;
if the second sub-application needs to use the component of the first version, the method further includes:
and acquiring at least one target component from the first component library of the first version according to the second target path, and importing the target component to the second sub-application for use.
5. A component library update apparatus, comprising:
the component library module is used for newly building a second sub application, and the second sub application is provided with a first component library of a second version; the first component library comprises a plurality of components;
an execution module to export the second version of the first component library to a first target path of the second sub-application;
and the export module is used for acquiring at least one target component from the first component library of the second version according to the first target path and exporting the target component to a target sub-application in the plurality of sub-applications.
6. The component library update apparatus according to claim 5, wherein the target sub-application is a first sub-application, and the first sub-application is installed with a first component library of a first version.
7. The component library update apparatus according to claim 5, wherein the target sub-application is a third sub-application, and the first component library is not installed in the third sub-application.
8. The component library updating apparatus according to claim 6, further comprising an import module;
the execution module is further configured to export a first component library of a first version from the first sub-application to a second target path of the first sub-application;
if the component of the first version needs to be used in the second sub-application, the importing module is configured to obtain at least one target component from the first component library of the first version according to the second target path, and import the target component into the second sub-application.
9. An electronic device, comprising: processor, memory and program stored on the memory and executable on the processor, which when executed by the processor implements the steps of the component library update method of any one of claims 1 to 4.
10. A readable storage medium, characterized in that the readable storage medium has stored thereon a program which, when executed by a processor, implements the steps of the component library updating method according to any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110303244.7A CN112965733A (en) | 2021-03-22 | 2021-03-22 | Component library updating method and device, electronic equipment and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110303244.7A CN112965733A (en) | 2021-03-22 | 2021-03-22 | Component library updating method and device, electronic equipment and readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112965733A true CN112965733A (en) | 2021-06-15 |
Family
ID=76279469
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110303244.7A Pending CN112965733A (en) | 2021-03-22 | 2021-03-22 | Component library updating method and device, electronic equipment and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112965733A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114398065A (en) * | 2022-03-24 | 2022-04-26 | Tcl通讯科技（成都）有限公司 | Micro front-end system updating method and device, electronic equipment and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120047185A1 (en) * | 2010-08-17 | 2012-02-23 | Sap Ag | Component load procedure for setting up systems |
| WO2015028538A1 (en) * | 2013-09-02 | 2015-03-05 | Agfa Healthcare | A method and system for upgrading software |
| CN104572054A (en) * | 2013-10-22 | 2015-04-29 | 中国移动通信集团公司 | Capability calling method and capability calling equipment |
| US20170010952A1 (en) * | 2015-07-10 | 2017-01-12 | Ca, Inc. | Selecting application wrapper logic components for wrapping a mobile application based on wrapper performance feedback from user electronic devices |
| CN108241500A (en) * | 2018-01-15 | 2018-07-03 | 腾讯科技（深圳）有限公司 | A kind of restorative procedure of hardware component, device, system and storage medium |
-
2021
- 2021-03-22 CN CN202110303244.7A patent/CN112965733A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120047185A1 (en) * | 2010-08-17 | 2012-02-23 | Sap Ag | Component load procedure for setting up systems |
| WO2015028538A1 (en) * | 2013-09-02 | 2015-03-05 | Agfa Healthcare | A method and system for upgrading software |
| CN104572054A (en) * | 2013-10-22 | 2015-04-29 | 中国移动通信集团公司 | Capability calling method and capability calling equipment |
| US20170010952A1 (en) * | 2015-07-10 | 2017-01-12 | Ca, Inc. | Selecting application wrapper logic components for wrapping a mobile application based on wrapper performance feedback from user electronic devices |
| CN108241500A (en) * | 2018-01-15 | 2018-07-03 | 腾讯科技（深圳）有限公司 | A kind of restorative procedure of hardware component, device, system and storage medium |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114398065A (en) * | 2022-03-24 | 2022-04-26 | Tcl通讯科技（成都）有限公司 | Micro front-end system updating method and device, electronic equipment and storage medium |
| CN114398065B (en) * | 2022-03-24 | 2022-07-08 | Tcl通讯科技（成都）有限公司 | Micro front-end system updating method and device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR100952251B1 (en) | Servicing a component base software product | |
| CN106933609B (en) | Android application program installation package generation method and device | |
| CN110096424B (en) | Test processing method and device, electronic equipment and storage medium | |
| CN110413259B (en) | Android service framework, method and device for realizing extended service | |
| CN104133676A (en) | Function execution method and function execution device based on scripts | |
| CN111679852B (en) | Detection method and device for conflict dependency library | |
| CN110221840B (en) | Function implementation method and device of application program, equipment and storage medium | |
| CN112965733A (en) | Component library updating method and device, electronic equipment and readable storage medium | |
| CN114895935A (en) | Method and device for flashing vehicle ECU, electronic equipment and storage medium | |
| CN111580847B (en) | GPU (graphics processing unit) driving updating method and device, computer storage medium and electronic equipment | |
| CN111200744A (en) | Multimedia playing control method and device and intelligent equipment | |
| CN110968339B (en) | Method and device for front-end building tool and electronic equipment | |
| CN114490103A (en) | Operating system interface calling method and device and electronic equipment | |
| CN108536429B (en) | Method and device for developing software, storage medium and electronic equipment | |
| CN111427582A (en) | Management method, device and equipment of RT L code and computer readable storage medium | |
| CN115437700A (en) | Method, device, system and medium for automatically configuring hardware resources of driver | |
| CN110309000B (en) | Application update prompting method and terminal equipment | |
| CN106681914B (en) | Television picture quality debugging method and device | |
| CN112148376A (en) | Terminal starting method and device | |
| CN111240752B (en) | Operating system self-adaption method and system | |
| CN107632934B (en) | Function copying method and device in C-sharp | |
| CN117591153A (en) | Method and device for dynamically loading JS objects by IOS | |
| CN114911509A (en) | Configuration method, equipment and storage medium of patch package | |
| CN117472407A (en) | Platform upgrading method, device, equipment and medium based on k8s cluster construction | |
| CN104090845A (en) | Automatic game testing method and system and related device |
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 |