A patch package configuration method, device and storage medium

Abstract

The present application belongs to the field of computer technology, and proposes a patch package configuration method, device and storage medium, which can effectively solve the problem that different applications cannot be embedded on demand in the process of reusing functional component codes in traditional technologies. The method includes: obtaining a template patch package, replacing the templated parameters in the template patch package with instantiation parameters adapted to the second application, generating a target patch package; and applying the target patch package to the second application.

Description

Technical Field

[0001] The present application belongs to the field of computer technology, and in particular, relates to a configuration method, device and storage medium for a patch package. Background Art

[0002] Currently, application programs in electronic devices are usually developed based on an existing development framework, and each application program usually includes functional modules for implementing different functions.

[0003] Based on a unified development framework, after an electronic device has developed a certain functional module in application A, when application B also needs to develop this functional module, the method usually adopted is to rely on the functional component code corresponding to the functional module in application A to application B in the form of a patch package, so that application B also has this functional module. However, not all functions corresponding to the functional module in application A are necessary for application B. Therefore, when the electronic device applies it to application B, it needs to re-sort the functional component code in system A to obtain the functional component code adapted to system B. It can be seen that application B cannot quickly reuse the functional module developed by application A, and cannot embed components on demand. Summary of the invention

[0004] In view of this, an embodiment of the present application provides a patch package configuration method, device and storage medium to solve the problem in the prior art that different applications cannot be embedded on demand during the process of reusing functional component codes.

[0005] A first aspect of an embodiment of the present application provides a method for configuring a patch package, including: obtaining a template patch package; replacing templated parameters in the template patch package with instantiation parameters adapted to a second application to generate a target patch package; and applying the target patch package to the second application.

[0006] It should be understood that the target patch package is the second patch package mentioned in the embodiment.

[0007] In combination with the first aspect, in a first possible implementation of the first aspect, the template patch package is generated based on a first patch package of a target functional module in a first application; wherein the first application and the second application are developed based on the same development framework.

[0008] In combination with the first aspect, in a second possible implementation of the first aspect, before obtaining the template patch package, the method also includes: creating the first patch package, the first patch package is created based on the change record of the functional component code corresponding to the target functional module in the first application; template processing the first patch package to generate a template patch package.

[0009] In combination with the first aspect, in a third possible implementation of the first aspect, before creating the first patch package, the method also includes: generating initial engineering code for the first application based on the development framework; creating a code management tool for the first application, and submitting the initial engineering code to the code management tool; refining and reconstructing the functional component code corresponding to the target functional module, and submitting the change records generated during the extraction and reconstruction of the functional component code to the code management tool.

[0010] In combination with the first aspect, in a fourth possible implementation of the first aspect, the refining and reconstructing the functional component code corresponding to the target functional module includes: transplanting the source code of the functional component code corresponding to the target functional module into the initial engineering code; and refining and reconstructing the source code of the functional component code.

[0011] In combination with the first aspect, in a fifth possible implementation of the first aspect, the refining and reconstructing the functional component code corresponding to the target functional module includes: transplanting the source code of the functional component code corresponding to the target functional module to the engineering code of another development framework adapted to the target functional module; refining and reconstructing the functional component code in the engineering code of another development framework; and transplanting the refined and reconstructed functional component code to the initial engineering code in the form of code calls.

[0012] In combination with the first aspect, in a sixth possible implementation of the first aspect, the first patch package is created based on a change record submitted in the code management tool of the first application, and the change record includes all changes in the first application from the initial engineering code to the refined and reconstructed functional component code.

[0013] In combination with the first aspect, in a seventh possible implementation of the first aspect, the template processing of the first patch package to generate a template patch package includes: parameterizing the data in the first patch package that changes according to different applications to generate a generalized template patch package.

[0014] A second aspect of an embodiment of the present application provides an electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of any method described in the first aspect when executing the computer program.

[0015] A third aspect of an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the method described in any one of the first aspects are implemented.

[0016] Compared with the prior art, the embodiments of the present application have the following beneficial effects: the embodiments provide a configuration method, device and storage medium of a patch package, in order to realize the reuse of functional component codes of different applications based on the same development framework, based on a template patch package, by replacing the templated parameters in the template patch package, obtaining instantiation parameters adapted to the second application, generating a target patch package, and then applying the target patch package to the second application. The configuration method in the embodiment realizes the rapid sharing and application of component functions, and the implementation code of the component can also be maintained in a unified project, thereby improving the reusability and maintainability of the component. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0018] Figure 1 It is a schematic diagram of the creation process of the first application and its functional components provided in an embodiment of the present application;

[0019] Figure 2 is a flow chart of a method for generating a template patch package provided in an embodiment of the present application;

[0020] Figure 3 is a flow chart of a method for configuring a template patch package provided in an embodiment of the present application;

[0021] Figure 4 It is a schematic diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0022] In the following description, specific details such as specific system structures, technologies, etc. are provided for the purpose of illustration rather than limitation, so as to provide a thorough understanding of the embodiments of the present application. However, it should be clear to those skilled in the art that the present application may also be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to prevent unnecessary details from obstructing the description of the present application.

[0023] The technical solution provided in this application is explained in detail below in conjunction with specific embodiments.

[0024] Based on the existing development framework, the electronic device can develop various applications, each of which has different functional modules built in. Among them, the development framework is created based on the functions to be implemented by different applications. In this embodiment, the application can also be called an application (App).

[0025] Based on the unified development framework, after the developer develops a certain function module 1 in application A, when application B also needs to develop this function module 1, the usual method is to copy and paste the function component code corresponding to function module 1 in application A to application B. In the dependency process, since function module 1 in application A may integrate some functions that application B does not need, it is necessary to modify and reorganize the function component code in application A to obtain the function component code adapted to application B. It can be seen that the function module developed by application A cannot be quickly reused by application B, nor can it embed components on demand, and cannot achieve the purpose of rapid component sharing and unified component maintenance and management.

[0026] Furthermore, when the electronic device applies the functional component code corresponding to the functional module 1 in application A to application B and application C in the above manner, if testing finds that there is a problem with the functional component code in application A, it is necessary to modify the functional component code in all applications (including application B and application C) that use the functional module 1, resulting in increased management and maintenance costs of the system.

[0027] In addition, based on a unified development framework, after an electronic device develops a functional module 1 in application A, when application B also needs to develop this functional module, it can also be redeveloped in application B. This method wastes manpower and material resources, and affects the development efficiency of the functional module, and is not suitable for the actual operation process.

[0028] Based on the above problems, an embodiment of the present application provides a method for configuring a patch package, which is a template patch package containing parameter variables. When applying it to an application, the parameter variables in the template patch package can be modified according to the parameter characteristics of the target application to obtain a patch package adapted to the target application.

[0029] In this embodiment, the electronic device may be a smart phone, a tablet computer, a computer running an operating system, or an intelligent hardware device, etc. This embodiment does not impose any specific restrictions on them.

[0030] The patch package generation and configuration method provided in this embodiment mainly involves three parts, including creation of a first application and its functional components, generation of a template patch package, and configuration process of the template patch package.

[0031] Figure 1 A schematic diagram of the creation process of the first application and its functional components is shown, as shown in Figure 1 As shown, the creation process includes the following steps S11-S14.

[0032] S11. The electronic device generates an initial engineering code of the first application based on a development framework.

[0033] In this embodiment, the development framework may be any template framework having application development functions, such as the Spring Web MVC framework (Spring MVC for short), an open source framework, and the like.

[0034] In some embodiments, the electronic device can generate an initial engineering code for the first application based on the development framework. The initial engineering code is an empty engineering code required to create the first application. It should be understood that all applications (such as application A, application B, or application C) are created based on the empty initial engineering code and generated based on a unified development framework, thereby ensuring the uniformity of the starting point of all applications, so that when the functional component code corresponding to the functional module in application A is applied to application B, the functional module can be reasonably adapted in application B.

[0035] S12: The electronic device creates a code management tool for the first application and submits the initial engineering code of the first application to the code management tool.

[0036] Each application corresponds to a code management tool. In this embodiment, the code management tool is mainly used to record the change records of the engineering code. The code management tool can be an SVN (Subversion) code manager or a distributed version control system Git repository.

[0037] In some embodiments, the electronic device creates a Git repository for the first application in a development framework, and then submits the initial engineering code of the first application to the Git repository.

[0038] It should be understood that in the present embodiment, the Git repository is used to record each change record of the engineering code. For example, for the first application, after the Git repository is initialized, the initial engineering code of the first application is submitted to the Git repository. If the electronic device modifies the initial engineering code in the first application during subsequent use and creates a functional component code belonging to the first application, the modified engineering code is submitted to the Git repository. When other applications need to use the functional component code of the first application, they can call it directly from the Git repository of the first application. Exemplarily, when the second application needs to use the functional component code in the first application, the corresponding functional component submitted by the first application will be pulled from the Git repository of the first application, and after being pulled down, it will automatically be dependent on the local engineering code of the second application, so that the functional component code of the first application and the second application are consistent.

[0039] In other embodiments, if the first application has been created based on a unified development framework, the electronic device does not need to execute the above steps S11-S12, and directly executes step S13.

[0040] S13. The electronic device configures a target functional module for the first application.

[0041] The electronic device can configure different target function modules for the first device according to user needs. In this embodiment, the target function module refers to a module with a specific function in the application program, and the specific function can be a payment function, a search function, or a voice recognition function.

[0042] It should be noted that the above-mentioned target functional module can be developed in the development framework of the first application, or can be developed from another development framework and then dependent on the development framework of the first application.

[0043] During the configuration process, the electronic device extracts and reconstructs the functional component code corresponding to the target functional module so that the functional component code is adapted to the initial engineering code of the first application. The functional component code refers to the component code required for the application to implement the above-mentioned specific function. For example, for the voice search function, when the electronic device needs to provide it in the form of a component for use in the first application, the functional component code corresponding to the voice search function is uploaded to the component market of the first application, and the functional component code needs to be refined and reconstructed before uploading.

[0044] If the target functional module is developed in the development framework of the first application, the electronic device transplants the source code of the functional component code corresponding to the target functional module into the initial engineering code of the first application. Then, the source code of the functional component code is refined according to the actual needs of the first application, the necessary functional code in the first application is retained, and the unnecessary functional code is deleted. Alternatively, when there are some technical problems in the source code of the functional component code, the source code is reconstructed to make the functional component code adapt to the initial engineering code.

[0045] If the target functional module is developed from another development framework and then depends on the development framework of the first application, when the electronic device applies it to the first application, the electronic device transplants the source code of the functional component code corresponding to the target functional module to the engineering code of other development frameworks that are adapted to the target functional module. The engineering code of the other development framework can be any engineering code that can be adapted to the target functional module. The electronic device places the functional component code corresponding to the target functional module in the engineering code for adaptation. After the adaptation is completed, the functional component code adapted by the engineering code is transplanted to the initial engineering code of the development framework for use in the form of code call. That is to say, when applied in the initial engineering code, the applied functional component code does not include the source code, but is the code defined by the above engineering code.

[0046] In this embodiment, the functional component code is first adapted to the initial engineering code, and the functional component code is refined and reconstructed according to the usage requirements of the initial engineering code, thereby improving the maintainability and scalability of the functional code component.

[0047] S14. The electronic device submits the change records generated during the extraction and reconstruction of the functional component codes corresponding to the target functional module to the code management tool.

[0048] In this embodiment, the electronic device also needs to test the component functions of the extracted and reconstructed functional component code to determine whether the functional component code is adaptable to the first application, and submit the change records generated during the extraction and reconstruction of the functional component code to the code management tool.

[0049] The above is the creation process of the first application and its functional components. Next, a method for generating the second patch package is explained in detail.

[0050] Figure 2 A flow chart of a method for generating a template patch package is shown, such as Figure 2 As shown, the method includes the following steps S21-S23.

[0051] S21. The electronic device creates a first patch package according to a functional component code change record of a target functional module in a code management tool of a first application.

[0052] In some embodiments, the first patch package is created based on a change record submitted in a code management tool of the first application, where the change record includes all changes in the first application from the initial engineering code to the refined and refactored functional component code.

[0053] Regardless of the method used by the electronic device to introduce the functional component code into the initial engineering code, the functional component code that is ultimately adapted to the initial engineering code will be changed. The electronic device uses a code management tool to store the change record and generates a first patch package for the functional component based on the change record. When the second application subsequently calls the functional component code based on the first patch package, all change records of the functional component code during the process of refining and reconstructing can be clearly identified, and then the functional component code is adapted to the engineering code of the second application based on the change record.

[0054] S22: The electronic device performs template processing on the first patch package to generate a template patch package, where the template patch package is used to configure functions corresponding to the target function module in the second application program.

[0055] It should be understood that the same patch package contains data that varies according to different applications, such as the package name, class name, application name, etc. Therefore, in this embodiment, the data that varies according to different applications in the first patch package needs to be parameterized to form a generalized template patch package.

[0056] Exemplarily, the electronic device performs template processing on the first patch package, modifies the package name, class name and application name in the first patch package into parameter variables, and generates a template patch package containing parameter variables. When the electronic device applies the template patch package to the second application, it modifies the parameter variables therein into the package name, class name and application name adapted for the second application, and obtains a second patch package adapted for the second application.

[0057] It should be noted that the second application and the first application generate empty development projects based on a unified development framework, and the starting points of the empty development projects based on the two applications are the same, so that patches generated after the same starting point can be applied to the second application.

[0058] S23. The electronic device uploads the template patch package to the component market of the development framework.

[0059] The component market is built into the development framework and is used to store components with different functions and provide technical support for the technical development of different applications.

[0060] The electronic device uploads the template patch package with parameter variables to the component market of the development framework, making the template patch package a universal component patch package. Since the template patch package carries parameter variables and is not instantiated, uploading it to the component market allows other applications to call it as needed.

[0061] This embodiment also provides a patch package configuration method, which is used to configure the template patch package in the configuration process of the second application after generating the template patch package. Figure 3 As shown, the configuration process includes the following steps S31-S35.

[0062] S31. The electronic device obtains a template patch package.

[0063] In some embodiments, when the electronic device needs to configure the target functional module for the second application, the required functional component can be obtained from the component market of the development framework. Exemplarily, when the second application needs to use the template patch package, the template patch package can be found from the component market and downloaded. In this embodiment, the second application can download the corresponding template patch package from the component market according to its own needs, so that in the process of component reuse, its flexibility is better.

[0064] S32: The electronic device replaces the templated parameters in the template patch package with the instantiated parameters in the second application program to generate a second patch package adapted for the second application program.

[0065] Since the template patch package is generated based on the functional component code specific to the first application, it is necessary to replace the parameter variables in the template patch package with the component patch package dedicated to the second application. For example, the parameter variable package name, class name and application name in the template patch package are replaced with the package name, class name and application name dedicated to the second application to generate a second patch package that is adapted to the second application and contains instantiation parameters, thereby realizing the instantiation of the template patch package in the second application.

[0066] S33: The electronic device applies the second patch package to the second application program.

[0067] In some embodiments, the second patch package is a patch package after replacing templated parameters. When applying it to the second application, the second patch package can be directly applied to the engineering code of the second application through the command letter in the code management tool.

[0068] In other embodiments, the electronic device applies the second patch package to the second application program, and can transplant the second patch package to the development tool IDEA through the commonly used development tool IDEA, and the development tool IDEA will display the functional component code change record in the patch package in a visual page. After the development tool IDEA confirms the operation, it will automatically apply the functional component code to the second application program project.

[0069] S34. The electronic device performs secondary development on the second patch package according to the application requirements of the target functional module in the second application program.

[0070] In the second application, the electronic device can modify the second patch package or perform secondary development according to the specific application requirements of the second application, so that the target functional module can develop functional components that are more suitable for the second application.

[0071] In one embodiment, if the functional components in the second application need to be changed, the electronic device can also perform secondary development in the engineering code of the second application to meet the customization requirements.

[0072] S35. The electronic device performs a functional component test in the second application.

[0073] After the second patch package is applied to the second application program, the electronic device verifies through component testing whether the function of the target functional module can operate normally and whether it meets the requirements.

[0074] If the electronic device fails to successfully verify its function during component testing, the first patch package after template processing is modified or the generation process of the first patch package is re-executed, and then the template patch package is re-generated.

[0075] The patch package generation and configuration method provided in this embodiment can realize the rapid sharing and application of functional component codes. At the same time, the functional component codes can also be maintained in a unified development framework, which improves the reusability and maintainability of the components. Applications can select templated components from the component market according to their own needs, which is more flexible. In addition, applications can also perform secondary development of functional component codes according to their own needs to meet customized needs.

[0076] It should be understood that the size of the serial numbers of the steps in the above embodiments does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0077] Figure 4 is a schematic diagram of an electronic device provided by an embodiment of the present application. Figure 4As shown, the electronic device 4 of this embodiment includes: a processor 40, a memory 41, and a computer program 42 stored in the memory 41 and executable on the processor 40, such as a patch package generation program. When the processor 40 executes the computer program 42, the steps in the above-mentioned various patch package configuration method embodiments are implemented. Alternatively, when the processor 40 executes the computer program 42, the functions of the modules / units in the above-mentioned various device embodiments are implemented.

[0078] Exemplarily, the computer program 42 may be divided into one or more modules / units, which are stored in the memory 41 and executed by the processor 40 to complete the present application. The one or more modules / units may be a series of computer program instruction segments capable of completing specific functions, which are used to describe the execution process of the computer program 42 in the electronic device 4.

[0079] The electronic device 4 may be a computing device such as a tablet computer, a tablet computer, a desktop computer, a notebook, a PDA, and a cloud server. The electronic device may include, but is not limited to, a processor 40 and a memory 41. Those skilled in the art will appreciate that Figure 4 It is only an example of the electronic device 4 and does not constitute a limitation of the electronic device 4. It may include more or fewer components than shown in the figure, or a combination of certain components, or different components. For example, the electronic device may also include input and output devices, network access devices, buses, etc.

[0080] The processor 40 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor, etc.

[0081] The memory 41 may be an internal storage unit of the electronic device 4, such as a hard disk or memory of the electronic device 4. The memory 41 may also be an external storage device of the electronic device 4, such as a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the electronic device 4. Further, the memory 41 may also include both an internal storage unit and an external storage device of the electronic device 4. The memory 41 is used to store the computer program and other programs and data required by the electronic device. The memory 41 may also be used to temporarily store data that has been output or is to be output.

[0082] The technicians in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example for illustration. In practical applications, the above-mentioned function allocation can be completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiment can be integrated in a processing unit, or each unit can exist physically separately, or two or more units can be integrated in one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application. The specific working process of the units and modules in the above-mentioned system can refer to the corresponding process in the aforementioned method embodiment, which will not be repeated here.

[0083] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0084] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0085] In the embodiments provided in the present application, it should be understood that the disclosed devices / terminal equipment and methods can be implemented in other ways. For example, the device / terminal equipment embodiments described above are only schematic. For example, the division of the modules or units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0086] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0087] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0088] If the integrated module / unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present application implements all or part of the process in the above-mentioned embodiment method, and can also be completed by hardware related to computer program instructions. The computer program can be stored in a computer-readable storage medium, and the computer program can implement the steps of the above-mentioned various method embodiments when executed by the processor. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, U disk, mobile hard disk, disk, optical disk, computer memory, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), electric carrier signal, telecommunication signal and software distribution medium. It should be noted that the content contained in the computer-readable medium can be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer-readable media do not include electric carrier signals and telecommunication signals.

[0089] The embodiments described above are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, a person skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. Such modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be included in the protection scope of the present application.

Claims

1. A method for configuring a patch package, characterized in that: include: Based on the development framework, generate initial engineering code of the first application; Creating a code management tool for the first application and submitting the initial engineering code to the code management tool; Refining and refactoring the functional component codes corresponding to the target functional module, and submitting the change records generated during the functional component code extraction and refactoring process to the code management tool; Creating a first patch package, wherein the first patch package is created according to a change record of a function component code corresponding to the target function module in the first application program; Performing template processing on the first patch package to generate a template patch package, wherein the template patch package is generated according to the first patch package of the target functional module in the first application program; Obtain the template patch package; Replacing the templated parameters in the template patch package with instantiation parameters adapted to the second application to generate a target patch package, wherein the first application and the second application are developed based on the same development framework; Apply the target patch package to the second application program.

2. The method according to claim 1, characterized in that: The refining and reconstructing of the functional component codes corresponding to the target functional module includes: Transplanting the source code of the functional component code corresponding to the target functional module into the initial engineering code; The source code of the functional component code is refined and reconstructed.

3. The method according to claim 1, characterized in that The refining and reconstructing of the functional component codes corresponding to the target functional module includes: Transplanting the source code of the functional component code corresponding to the target functional module into the engineering code of another development framework adapted to the target functional module; Refining and refactoring the functional component code in the engineering code of another development framework; The refined and reconstructed functional component code is transplanted to the initial engineering code in the form of code calling.

4. The method according to claim 1, characterized in that: The first patch package is created based on a change record submitted in the code management tool of the first application, wherein the change record includes all changes in the first application from the initial engineering code to the refined and reconstructed functional component code.

5. The method according to claim 1, characterized in that: The step of performing template processing on the first patch package to generate a template patch package includes: The data in the first patch package that changes according to different application programs is parameterized to generate a generalized template patch package.

6. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 5 are implemented.

7. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 5 are implemented.

Images