Plug-in processing method, device, equipment, storage medium and computer program product

Abstract

The present application proposes a plug-in processing method, device, equipment, storage medium and computer program product, which can be applied to various fields or scenarios such as cloud technology, artificial intelligence, blockchain, vehicle-mounted, smart transportation, smart home, and games. The method includes: obtaining plug-in version information, the plug-in version information includes functional information of the target plug-in to be generated; obtaining a plug-in template associated with the target plug-in, and determining the reserved functional modules and the to-be-processed functional modules from the functional modules included in the plug-in template according to the functional information; comparing the configuration file included in the to-be-processed functional module with the configuration file included in the reserved functional module to determine the configuration file to be cleared; clearing the configuration file to be cleared to obtain a cleared configuration file; generating the target plug-in according to the cleared configuration file and the configuration file included in the reserved functional module. Through the embodiments of the present application, the development efficiency of the plug-in can be effectively improved.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a plug-in processing method, a plug-in processing apparatus, a computer device, a computer-readable storage medium, and a computer program product. Background Art

[0002] A plug-in is a program written using a standardized application programming interface (API). It extends the functionality of an application. A plug-in must rely on the application to function; it cannot function properly on its own. During plug-in development, all code is manually written, which leads to low development efficiency. Summary of the Invention

[0003] The embodiments of the present application provide a plug-in processing method, apparatus, device, storage medium, and computer program product, which can effectively improve the efficiency of plug-in development.

[0004] In one aspect, an embodiment of the present application provides a plug-in processing method, the method comprising:

[0005] Obtaining plug-in version information, wherein the plug-in version information includes function information of the target plug-in to be generated;

[0006] Acquire a plug-in template associated with the target plug-in, and determine a reserved function module and a to-be-processed function module from the function modules included in the plug-in template according to the function information;

[0007] Comparing the configuration file included in the to-be-processed functional module with the configuration file included in the reserved functional module to determine the configuration file to be cleared, wherein the configuration file to be cleared is a configuration file belonging to the to-be-processed functional module and not belonging to the reserved functional module;

[0008] Performing a blanking process on the configuration file to be blanked to obtain a blanking configuration file;

[0009] The target plug-in is generated according to the blank configuration file and the configuration file included in the reserved function module.

[0010] On the other hand, an embodiment of the present application provides a plug-in processing device, the device comprising:

[0011] An acquiring unit, configured to acquire plug-in version information, wherein the plug-in version information includes function information of a target plug-in to be generated;

[0012] The acquisition unit is further configured to acquire a plug-in template associated with the target plug-in, and determine a retained function module and a to-be-processed function module from the function modules included in the plug-in template according to the function information;

[0013] a processing unit, configured to compare the configuration file included in the to-be-processed functional module with the configuration file included in the reserved functional module, and determine a configuration file to be cleared, wherein the configuration file to be cleared is a configuration file belonging to the to-be-processed functional module and not belonging to the reserved functional module;

[0014] The processing unit is further configured to perform a blanking process on the configuration file to be blanked to obtain a blanking configuration file;

[0015] The processing unit is further configured to generate the target plug-in according to the cleared configuration file and the configuration file included in the reserved function module.

[0016] Accordingly, an embodiment of the present application provides a computer device, which includes a processor, a communication interface and a memory, wherein the processor, the communication interface and the memory are interconnected, wherein the memory stores a computer program, and the processor is used to call the computer program to execute the plug-in processing method of any possible implementation method mentioned above.

[0017] Accordingly, an embodiment of the present application provides a computer-readable storage medium storing a computer program, and a processor executes the computer program involved in the plug-in processing method of any possible implementation manner described above.

[0018] Accordingly, an embodiment of the present application further provides a computer program product, which includes a computer program or computer instructions, and when the computer program or computer instructions are executed by a processor, the steps of the plug-in processing method provided in the embodiment of the present application are implemented.

[0019] Accordingly, an embodiment of the present application also provides a computer program, which includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the plug-in processing method provided in the embodiment of the present application.

[0020] In an embodiment of the present application, a reserved functional module and a to-be-processed functional module are determined from a plug-in template associated with the target plug-in through functional information of the target plug-in, and a configuration file belonging to the to-be-processed functional module and not belonging to the reserved functional module is determined as a to-be-emptied configuration file, and a target plug-in is generated using the to-be-emptied configuration file obtained by emptying the to-be-emptied configuration file and the configuration file included in the reserved functional module; the above-mentioned plug-in processing method adopts reverse thinking to process only unnecessary configuration files, so that there is no need to reconstruct existing code during plug-in development, which can effectively improve the development efficiency of the plug-in. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following is a brief introduction to the drawings required for use in the description of the embodiments. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0022] Figure 1 A network architecture applicable to a plug-in processing method provided in an embodiment of the present application;

[0023] Figure 2 A schematic diagram of a plug-in processing method provided in an embodiment of the present application;

[0024] Figure 3 A flowchart of a plug-in processing method provided in an embodiment of the present application;

[0025] Figure 4 A schematic diagram of a plug-in template provided in an embodiment of the present application;

[0026] Figure 5 A flowchart of another plug-in processing method provided in an embodiment of the present application;

[0027] Figure 6 A schematic diagram illustrating the dependency relationship between analysis modules provided in an embodiment of the present application;

[0028] Figure 7 A schematic diagram of the configuration items provided in the embodiment of the present application;

[0029] Figure 8 A flowchart of another plug-in processing method provided in an embodiment of the present application;

[0030] Figure 9 A schematic diagram of the structure of a plug-in processing device provided in an embodiment of the present application;

[0031] Figure 10 A schematic diagram of the structure of a computer device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0032] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0033] It should be noted that the terms "first," "second," and so on, used in the embodiments of this application are for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Therefore, technical features designated as "first," "second," and so on may explicitly or implicitly include at least one such feature.

[0034] To better understand the embodiments of the present application, some terms involved in the embodiments of the present application are introduced below:

[0035] WXML or file name .wxml: represents a structural file, which can be used to build the structure of the page in combination with basic components and event systems.

[0036] WXSS or file name .wxss: indicates a style file, which is usually used together with a structure file to describe the component style, that is, how the components defined in the structure file should be displayed.

[0037] JS or file name .js: represents the logic file, which is responsible for the business logic of the page, such as life cycle, event binding processing, data initialization, etc.

[0038] JSON or filename.json: indicates a properties file used to configure static data, such as the window background color, navigation bar background color, navigation bar title text, etc.

[0039] Plug-in: A program written in accordance with a certain standard application program interface.

[0040] Functional modules are a collection of program elements, such as data descriptions and executable statements, that implement one or more functions. When developing plugins, you can approach them modularly, creating plugins by packaging different functional modules into an application.

[0041] In order to effectively improve the development efficiency of plug-ins, the present application proposes a plug-in processing method, which is based on the module deletion method to perform blank processing (or deletion processing) on the modules in the plug-in to generate different plug-in versions (or new plug-ins), thereby effectively improving the development efficiency of the plug-in. The plug-in processing method can be implemented based on cloud technology. Cloud technology is a general term for network technology, information technology, integration technology, management platform technology, application technology, etc. based on the application of cloud computing business model. It can form a resource pool that can be used on demand and is flexible and convenient. Cloud computing technology will become an important support. The background services of technical network systems require a large amount of computing and storage resources, such as video websites, picture websites and more portal websites. With the rapid development and application of the Internet industry, in the future, each item may have its own identification mark, and all need to be transmitted to the background system for logical processing. Data of different levels will be processed separately. All kinds of industry data require strong system backing support, which can only be achieved through cloud computing.

[0042] In feasible embodiments, the plug-in processing method provided in the embodiments of the present application can also be implemented based on artificial intelligence (AI) and / or blockchain technology. Specifically, it can involve one or more of distributed storage and big data processing technologies in the foundational AI technologies. For example, the generated plug-in can be stored in a distributed manner on multiple independent devices. In another example, the data required to execute the plug-in processing method can be stored in the form of blocks on the blockchain; the data generated by executing the data processing method (such as configuration files, file information, file storage paths, etc.) can be stored in the form of blocks on the blockchain; and the computer device executing the plug-in processing method can be a node device in the blockchain network.

[0043] The plug-in processing method provided in the embodiment of the present application can be applied to Figure 1 The network architecture shown. Figure 1 The computer device 10 shown can be a server or terminal with data processing capabilities. The server can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms. The terminal can be a smartphone, tablet computer, laptop computer, desktop computer, intelligent voice interaction device, smart home appliance, in-vehicle terminal, etc., but is not limited to these. Figure 1 The terminal 11 is connected to the computer device 10 via a network. The plug-in processing method provided in the embodiment of the present application can be executed by the computer device 10, specifically:

[0044] The computer device 10 determines the reserved function module and the to-be-processed function module from the plug-in template associated with the target plug-in through the function information of the target plug-in, determines the configuration files belonging to the to-be-processed function module and not belonging to the reserved function module as the to-be-emptied configuration files, and generates the target plug-in by emptying the configuration files obtained by emptying the to-be-emptied configuration files and the configuration files included in the reserved function modules, for example, Figure 2 As shown, for component R (which can be understood as a plug-in template), component R includes configuration files: a.wxml, a.wxss, a.js, a.json, expansion.wxml and entry.wxml. When it is determined that the expansion.wxml is a configuration file to be cleared, only the expansion.wxml in component R can be cleared, and the component R after clearing can be used as a new plug-in. It can be seen that the reverse thinking is used to process only unnecessary configuration files, so that there is no need to reconstruct existing code during plug-in development, which can effectively improve the development efficiency of the plug-in.

[0045] In one embodiment, computer device 10 may provide a target plug-in to terminal 11, which may then deploy the target plug-in on an application to provide extended functionality for the application. Alternatively, computer device 10 may receive a deployment request for the target plug-in from terminal 11 and, upon approval, deploy the target plug-in on the application. The application may specifically be a mini-program, a browser application, or the like.

[0046] It can be understood that the network architecture diagram described in the embodiment of the present application is for the purpose of more clearly illustrating the technical solution of the embodiment of the present application, and does not constitute a limitation on the technical solution provided in the embodiment of the present application. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution provided in the embodiment of the present application is also applicable to similar technical problems.

[0047] The above briefly introduces the plug-in processing method provided in the embodiment of the present application. The specific implementation of the plug-in processing method is described in detail below.

[0048] See also Figure 3 , Figure 3 This is a flow chart of a plug-in processing method provided in an embodiment of the present application. The plug-in processing method includes but is not limited to the following steps:

[0049] S301: Obtain plug-in version information, where the plug-in version information includes function information of a target plug-in to be generated.

[0050] In an embodiment of the present application, the target plug-in to be generated is a plug-in of any type, for example, a mini-program plug-in, a browser plug-in, and so on. The plug-in version information is the version information of the target plug-in, and may include one or more of the plug-in name, plug-in version number, plug-in version identifier, and plug-in type as the identity of the target plug-in. In addition, the plug-in version information also includes the functional information of the target plug-in, which is used to indicate the goals or functions that the target plug-in needs to achieve. For example, if the target plug-in is a live broadcast plug-in, the functional information may be the functional modules required for live broadcast or a description of the plug-in used for live broadcast.

[0051] In an embodiment of the present application, the computer device can output a configuration interface, and the plug-in developer can configure the functional information of the target plug-in in the configuration interface. The computer device obtains the functional information of the target plug-in configured by the developer, and automatically generates the target plug-in based on the subsequent process according to the guidance of this functional information.

[0052] In one embodiment, the configuration interface may provide various functional module options for plug-in developers to select, and the functional modules selected by the developer are used as functional information of the target plug-in; the developer may also input the functional modules required by the target plug-in as the requirement information of the target plug-in in the configuration interface.

[0053] In another embodiment, the developer may define the functional modules required by the target plug-in in the project configuration file of the target plug-in, and use them as the functional information of the target plug-in (wherein, one or more of the plug-in name, plug-in version number, plug-in version identifier, and plug-in type may also be defined in the project configuration file). For example, the project configuration file may be a package.json file. The developer may configure the functional modules required by the target plug-in by configuring the scripts field in the package.json file. The following is an example of configuring the scripts field in the package.json file:

[0054] "scripts":{

[0055] "build-expand":"gulp build--expand"

[0056] }

[0057] In one embodiment, the computer device can perform input processing on the project configuration file to obtain the functional module required by the target plug-in. For example, the computer device can run the gulp tool through npm to execute the package.json file, and obtain the execution script npm run build-expand. The parameter expand can be obtained in the execution script, thereby determining that the functional module required by the target plug-in is the expansion function (expand).

[0058] Among them, gulp is a flow-based automated construction tool; nmp is a package management tool installed with NodeJS.

[0059] S302: Acquire a plug-in template associated with the target plug-in, and determine a reserved functional module and a to-be-processed functional module from the functional modules included in the plug-in template according to the functional information.

[0060] In an embodiment of the present application, the plug-in template associated with the target plug-in includes one or more functional modules, and there is a functional module among the one or more functional modules that can realize part or all of all functions indicated by the functional information of the target plug-in, that is, one functional module can realize all functions indicated by the functional information, or one functional module can realize part of the functions indicated by the functional information, and multiple functional modules can jointly realize all functions indicated by the functional information.

[0061] In one embodiment, a computer device obtains a plug-in template associated with a target plug-in in the following manner: one is to obtain functional information of the target plug-in and functional information of multiple plug-in modules, compare the functional information of the target plug-in with the functional information of multiple plug-in templates, and if there is a plug-in template whose functional information matches the functional information of the target plug-in (that is, there is a plug-in template that includes all functions required by the target plug-in), then the plug-in template is determined to be the plug-in template associated with the target plug-in. For example, the functional information of the target plug-in A indicates that the functional modules required by the target plug-in A are: functional module 1, functional module 2, and the functional information of the plug-in template B indicates that the functional modules included in the plug-in template B are: functional module 1, functional module 2. Module 2, functional module 3, then plug-in module B includes all the functions required by the target plug-in A, and plug-in module B is used as a plug-in template associated with the target plug-in A; one is: the plug-in version number of the plug-in template can be used as the public version number. When the plug-in version number of the target plug-in includes the public version number of the plug-in template, the plug-in template is determined as the plug-in template associated with the target plug-in. For example, the plug-in version number of plug-in template B is 111.102.112, and the plug-in version number of the target plug-in A is 111.102.112.020. Then the plug-in version number of the target plug-in A includes the public version number 11.102.112, and the plug-in module B is used as a plug-in template associated with the target plug-in A.

[0062] In one embodiment, retained functional modules and to-be-processed functional modules are determined from functional modules included in the plug-in template based on functional information, specifically: from the functional modules included in the plug-in template (which are plug-in versions associated with the target plug-in), a matching functional module that matches the functional information of the target plug-in is determined, the matching functional module is determined as the retained functional module, and the functional modules other than the matching functional module in the functional modules included in the plug-in template are determined as to-be-processed functional modules.

[0063] In an embodiment of the present application, the matching function module can realize part or all of all functions indicated by the function information of the target plug-in. The matching function module is used as a reserved function module, that is, the reserved function module can realize part or all of all functions indicated by the function information of the target plug-in. That is, one reserved module (or matching function) can realize all functions indicated by the function information, or one reserved module (or matching function) can realize part of the functions indicated by the function information, and multiple reserved modules (or matching functions) can jointly realize all functions indicated by the function information. The pending function module is a function module that cannot realize part or all of the functions indicated by the function information of the target plug-in, which can be understood as a function module that is not needed by the target plug-in when generating the target plug-in.

[0064] Through analysis, we can get the function modules required by the target plug-in in the plug-in template (i.e., retained function modules) and the function modules not required (i.e., pending function modules). Although the required function modules can realize all the functions indicated by the function information of the target plug-in, due to the coupling between function modules, if all configuration files included in the pending function modules are directly cleared, it may cause errors when compiling the plug-in because the required configuration files cannot be found (this is because the function modules share the same configuration files using the same file storage path). See Figure 4 , Figure 4 This is an example diagram of a plug-in template, which includes an expansion function module, a reflux function module, an entry function module and a privileged function module. It can be seen that the expansion function module and the entry function module share a common component A, so there is a coupled component A between the expansion function module and the entry function module. When the target plug-in only needs the expansion function module and the reflux function module, if the configuration file of the entry function module is directly deleted, then when compiling the expansion function module in the target plug-in, the file storage path does not contain the configuration file pointing to component A, and an error will be reported. Therefore, after determining the retained function modules and the function modules to be processed, the coupling relationship (or dependency relationship) between the modules can be further analyzed.

[0065] S303: Compare the configuration files included in the to-be-processed functional module with the configuration files included in the reserved functional module to determine the configuration files to be cleared, wherein the configuration files to be cleared are configuration files that belong to the to-be-processed functional module and do not belong to the reserved functional module.

[0066] In an embodiment of the present application, the configuration file of the retained functional module is the configuration file required by the target plug-in; the configuration file of the module to be processed is the functional module not required by the target plug-in; the configuration file to be cleared is a configuration file that belongs to the functional module to be processed and does not belong to the retained functional module, and is a configuration file not required by the target plug-in.

[0067] In one embodiment, in order to analyze the dependency relationship between the reserved functional module and the to-be-processed functional module, the configuration file included in the to-be-processed functional module can be compared with the configuration file included in the reserved functional module to determine the configuration file that belongs to the to-be-processed functional module but not to the reserved functional module and to be cleared. For example, the reserved functional module A includes the configuration file a.wxml, the reserved functional module B includes the configuration file b.wxml, and the to-be-processed functional module C includes the configuration files a.wxml and c.wxml. It can be seen that the reserved functional module A and the to-be-processed functional module C have a common configuration file a.wxml. The configuration file a.wxml belongs to the to-be-processed functional module and the reserved functional module. The configuration file a.wxml is the configuration file required by the target plug-in, and the configuration file c.wxml belongs to the to-be-processed functional module C, and does not belong to the reserved functional module A or the reserved functional module B. Therefore, the configuration file c.wxml is the configuration file to be cleared.

[0068] In one embodiment, the configuration file included in the function module to be processed is compared with the configuration file included in the reserved function module to determine the configuration file to be cleared, specifically: the file information of each configuration file included in the reserved function module is saved to the first storage space, the file information of the configuration file to be detected included in the function module to be processed is obtained, and the file information of the configuration file to be detected is detected whether it is included in the first storage space; if the file information of the configuration file to be detected is not included in the first storage space, the configuration file to be detected is determined as the configuration file to be cleared.

[0069] In an embodiment of the present application, the configuration file to be detected is any configuration file in the functional module to be processed. The file information is the identity identifier of the configuration file, for example, the file storage path, such as components / hello-component, which indicates that the configuration file is the file indicated by the directory hello-component in the directory components. It can also be an encrypted password for the file storage path, or a file name (in this case, the file name of the configuration file is guaranteed to be unique). The first storage space is a storage space created for the retained functional module, which is used to store the file information of the configuration file included in the retained functional module. The storage space can be a container (a group of processes that are subject to resource constraints and isolated from each other).

[0070] In one embodiment, a first storage space is created for the reserved functional module, and file information of the configuration file included in the reserved functional module is saved to the first storage space. For the configuration file to be detected in the functional module to be processed (any configuration file in the functional module to be processed), it is detected whether the file information of the configuration file to be detected is contained in the first storage space. If the file information of the configuration file to be detected is contained in the first storage space, it means that the configuration file to be detected belongs to the reserved functional module. If the file information of the configuration file to be detected is not contained in the first storage space, it means that the configuration file to be detected belongs to the functional module to be processed and does not belong to the reserved functional module, and is a configuration file to be cleared.

[0071] In the embodiment of the present application, the configuration files to be emptied are determined by comparing the file information of the configuration files instead of directly comparing the configuration files. This can improve the efficiency of determining the configuration files to be emptied, thereby improving the efficiency of generating the plug-in.

[0072] S304: Perform a blanking process on the configuration file to be blanked to obtain a blanking configuration file.

[0073] It needs to be explained that the configuration file to be cleared is a configuration file that is not needed by the target plug-in, but if the configuration file to be cleared is directly deleted, it may also cause an error when compiling the plug-in, because this application compiles the target plug-in according to the compilation rules of the plug-in template (taking into account the low efficiency of the developer re-establishing the compilation rules of the target plug-in), the compilation rules of the plug-in template will still instruct the compilation of the configuration file to be cleared. If the configuration file to be cleared is directly deleted, an error will be reported because the configuration file to be cleared cannot be found. Therefore, the clearing process can enable the computer device to process the configuration file to be cleared that only retains the empty declaration according to the compilation rules of the plug-in template.

[0074] In an embodiment of the present application, the configuration file to be cleared includes a first type of file or a second type of file (i.e., a target file). In one embodiment, different clearing processing methods are adopted for different types of configuration files to be cleared, specifically: clearing the first type of file includes deleting the file content of the first type of file, and clearing the second type of file includes deleting the file content of the second type of file except the declaration information.

[0075] In the embodiment of the present application, the first type of files includes structure files and style files, and the second type of files includes logic files and attribute files. The blanking process for the structure files and style files is to delete the file contents of the structure files and style files, which is equivalent to converting the structure files and style files into empty characters.

[0076] In one embodiment, the blanking process for the logic files included in the second type of files is to delete the file content of the logic files except for the first declaration information (the declaration defined in the program specification indicated by the logic file). For example, the code in the logic file is as follows, and the page declaration Page({}) is the first declaration information, then the blanking configuration file obtained by the logic file only includes Page({}).

[0077]

[0078]

[0079] In one embodiment, the property files included in the second category of files are cleared by deleting the file contents of the property files except for the second declaration information (the declaration defined in the program specification indicated by the property file). For example, if the page declaration {"Page":true} in the property file of the component is the second declaration information, then the cleared configuration file finally obtained for the property file only includes {"Page":true}.

[0080] S305: Generate the target plug-in according to the cleared configuration file and the configuration file included in the reserved function module.

[0081] In one embodiment, the empty configuration file and the configuration file included in the reserved function module are compressed to obtain a target plug-in program package, and the target plug-in program package is installed on an application (such as a mini-program) to provide extended functions for the application.

[0082] In one embodiment, the target plug-in may further include a configuration file that does not belong to the reserved functional module and does not belong to the to-be-processed functional module, that is, a configuration file that belongs exclusively to the target plug-in.

[0083] In an embodiment of the present application, the reserved function module and the to-be-processed function module are determined from the plug-in template associated with the target plug-in through the function information of the target plug-in, and the configuration file belonging to the to-be-processed function module and not belonging to the reserved function module is determined as the to-be-emptied configuration file. The target plug-in is generated by emptying the configuration file to be empty and the configuration file included in the reserved function module. Reverse thinking is used to process only unnecessary configuration files, so that there is no need to reconstruct the existing code during plug-in development, which can effectively improve the development efficiency of the plug-in. At the same time, it solves the problem that the different capabilities of different developers affect the quality of the plug-in code, and can effectively ensure the quality of the plug-in code.

[0084] See also Figure 5 , Figure 5 This is a flow chart of another plug-in processing method provided in an embodiment of the present application. The plug-in processing method includes but is not limited to the following steps:

[0085] S501: Obtain plug-in version information, where the plug-in version information includes function information of a target plug-in to be generated.

[0086] S502: Acquire a plug-in template associated with the target plug-in, and determine a reserved functional module and a to-be-processed functional module from the functional modules included in the plug-in template according to the functional information.

[0087] The detailed implementation process of steps S501 and S502 can refer to the aforementioned steps S301 and S302, which will not be repeated in this embodiment.

[0088] S503. Save the file storage path of each configuration file included in the retained functional module to the first storage space. If the file storage path of the configuration file to be detected is not included in the first storage space, determine the configuration file to be detected as a configuration file to be cleared, and save the file storage path of the configuration file to be cleared to the second storage space. The configuration file to be detected is any configuration file included in the functional module to be processed.

[0089] In an embodiment of the present application, the first storage space is a storage space for a retained functional module, which can be used to save the file storage path of the configuration file of the retained functional module; the second storage space is a storage space for a function module to be processed, which can be used to save the file storage path of the configuration file to be cleared; the first storage space and the second storage space can be containers.

[0090] In one embodiment, the computer device saves the file storage path of the configuration file included in the reserved function module to the first storage space, see Figure 6 , Figure 6 The file storage path of the configuration file a.wxml included in the retained function module A and the file storage path of the configuration file b.wxml included in the retained function module B are saved to the first storage space, and the computer device detects whether the file storage path of the configuration file to be detected is in the first storage space. When the file storage path of the configuration file to be detected is not included in the first storage space, it is determined that the configuration file to be detected is a configuration file to be cleared, and the file storage path of the configuration file to be cleared is saved to the second storage space, such as Figure 6 If the file storage path of the configuration file a.wxml to be detected included in the function module C to be processed is in the first storage space, then the configuration file a.wxml to be detected is not a configuration file to be cleared, and the file storage path of the configuration file c.wxml to be detected included in the function module C to be processed is not in the first storage space, then the configuration file c.wxml to be detected is a configuration file to be cleared, and the file storage path of the configuration file c.wxml to be cleared is saved to the second storage space.

[0091] S504: Obtain a path configuration file of the plug-in template, where the path configuration file includes a file storage path of each configuration file included in the plug-in template.

[0092] In an embodiment of the present application, the path configuration file of the plug-in template includes the file storage path of all configuration files included in the plug-in template. The computer device can obtain all configuration files included in the plug-in template according to the path configuration file of the plug-in template to compile the plug-in template, which is equivalent to the compilation rules of the aforementioned plug-in template.

[0093] S505. In the process of obtaining the various configuration files included in the plug-in template according to the path configuration file, if it is detected that the first file storage path included in the path configuration file is contained in the second storage space, the configuration file corresponding to the obtained first file storage path is cleared to obtain a cleared configuration file.

[0094] In an embodiment of the present application, the first file storage path is any file storage path included in the path configuration file, and the configuration file corresponding to the first file storage path is a configuration file to be cleared.

[0095] In one embodiment, a computer device executes a compilation task of a target plug-in according to a path configuration file (i.e., obtains all configuration files included in a plug-in template). When it is detected that the first file storage path included in the path configuration file is in a second storage space, it indicates that the configuration file corresponding to the first file storage path is a configuration file to be cleared. The configuration file corresponding to the first file storage path is obtained, and the configuration file corresponding to the first file storage path is cleared to obtain a cleared configuration file.

[0096] S506: Generate the target plug-in according to the cleared configuration file and the configuration file corresponding to the second file storage path included in the acquired path configuration file.

[0097] In an embodiment of the present application, the second file storage path is any file storage path included in the path configuration file except the first file storage path, and the configuration file corresponding to the second file storage path includes a configuration file of a reserved functional module.

[0098] In one embodiment, when it is detected that the second file storage path included in the path configuration file is not in the second storage space, indicating that the configuration file corresponding to the second file storage path is a configuration file of a reserved function module, the configuration file corresponding to the second file storage path is obtained.

[0099] In one embodiment, in one embodiment, the path configuration file may include a configuration file that is unique to the plug-in template and does not belong to the retained functional module and the to-be-processed functional module. When any file storage path is not in the storage space (including the first storage space and the second storage space), the configuration file corresponding to any file storage path can be obtained as the configuration file included in the target plug-in.

[0100] In an embodiment of the present application, by saving the file storage path included in the plug-in template to the corresponding storage space, when compiling the target plug-in, the storage space to which the file storage path of the configuration file belongs can be used to decide whether to perform the blanking process, thereby improving the generation efficiency of the target plug-in. At the same time, the configuration file to be blanked in the plug-in template is blanked, so that there is no need to reconstruct the existing code during plug-in development, which can effectively improve the development efficiency of the plug-in.

[0101] In one embodiment, the functional module includes one or more configuration items, each of which includes one or more configuration files. Figure 7 , Figure 7 The functional modules shown include configuration items: component entry, page entry, WXML full path, WXSS full path, Behaviour full path and JS full path.

[0102] In an embodiment of the present application, the component entry includes all components in the functional module, each component includes one or more of the structure file, style file, logic file and property file; the page entry includes all pages in the functional module, each page includes one or more of the structure file, style file, logic file and property file; the WXML full path includes one or more of the component's structure file and the page's structure file; the WXSS full path includes one or more of the component's style file and the page's style file; the Behaviour full path includes logic files related to life cycle and data initialization in the functional module (such as initializing components and destroying components); the JS full path includes logic files related to event binding processing in the functional module (such as component triggering events).

[0103] In one embodiment, the computer device may generate a target plug-in based on the configuration items, specifically by determining a first sub-storage space corresponding to each configuration item in one or more configuration items, for example, Figure 8Corresponding first sub-storage spaces are set for the configuration project component entry, page entry, WXML full path, WXSS full path, Behaviour full path and JS full path respectively. According to the configuration projects to which the configuration files included in the retained functional modules belong, the file storage paths of the configuration files included in the retained functional modules are saved to the corresponding first sub-storage spaces, such as saving the file storage paths of the configuration files included in the page entry to the storage space to which the page entry belongs.

[0104] In another embodiment, each configuration item may directly include the file storage path of one or more configuration files. For example, the configuration item directly includes the file storage paths of all components in the functional module.

[0105] Furthermore, the computer device determines the configuration item to which the configuration file to be detected belongs, detects whether the file storage path of the configuration file to be detected is contained in the first sub-storage space corresponding to the configuration item to which the configuration file to be detected belongs, and if the file storage path of the configuration file to be detected is not contained in the first storage space, determines the configuration file to be detected as a configuration file to be cleared, and saves the file storage path of the configuration file to be cleared in the second storage space. Each of the first sub-storage spaces constitutes the first storage space.

[0106] In another embodiment, the computer device may determine the second sub-storage space corresponding to each configuration item in one or more configuration items, determine the configuration item to which the configuration file to be detected belongs, detect whether the file storage path of the configuration file to be detected is contained in the first sub-storage space corresponding to the configuration item to which the configuration file to be detected belongs, and if the file storage path of the configuration file to be detected is not contained in the first storage space, determine the configuration file to be detected as a configuration file to be cleared, and save the file storage path of the configuration file to be cleared to the second sub-storage space to which the configuration file to be cleared belongs. Each second sub-storage space constitutes the second storage space.

[0107] Through this embodiment, a corresponding second sub-storage space can be created for the configuration items of the function module to be processed, and can be used to store the file storage path of the configuration file to be cleared of the function module to be processed.

[0108] Furthermore, in the process of the computer device obtaining various configuration files included in the plug-in template according to the path configuration file, if it is detected that the first file storage path included in the path configuration file is included in the second storage space, the configuration file corresponding to the obtained first file storage path is cleared to obtain a cleared configuration file; if it is detected that the first file storage path included in the path configuration file is not included in the second sub-storage space, the configuration file corresponding to the second file storage path included in the path configuration file is obtained, and the target plug-in is generated according to the cleared configuration file and the configuration file corresponding to the second file storage path included in the obtained path configuration file.

[0109] Specifically, if Figure 8 As shown, the computer device can detect whether the file storage path included in the path configuration file is in the storage space (including the first storage space and the second storage space). If it is not in the storage space, it means that the configuration file corresponding to the file storage path does not belong to the retained function module or the to-be-processed function module, and the configuration file corresponding to the file storage path is directly compressed; if it is in the storage space, it is further processed according to the storage space. If the file storage path is in the first storage space (or any first sub-storage space), the configuration file corresponding to the file storage path is compressed; if the file storage path is in the second storage space (or any second sub-storage space), the configuration file corresponding to the file storage path is cleared to obtain a cleared configuration file, and the cleared configuration file is compressed to obtain the target plug-in.

[0110] In one embodiment, each configuration item of the target plug-in may correspond to a sub-path configuration file (including the file storage path of all configuration files in each configuration item). The computer device may use parallel tasks to compile the target plug-in, and each task is responsible for traversing a configuration item to generate the target plug-in, which can improve the generation efficiency of the target plug-in.

[0111] In an embodiment of the present application, the file storage paths of all configuration files included in the configuration project are saved in the corresponding sub-storage space, and then the sub-storage space is used to determine the configuration files to be cleared. This can improve the generation efficiency of the template plug-in. At the same time, only the configuration files to be cleared in the plug-in template are processed, so that there is no need to reconstruct the existing code when developing the plug-in, which can effectively improve the development efficiency of the plug-in.

[0112] The above describes in detail the method of the embodiment of the present application. To facilitate better implementation of the above solution of the embodiment of the present application, the following provides a device of the embodiment of the present application. Figure 9 , Figure 9 : is a schematic diagram of a plug-in processing device provided by an exemplary embodiment of the present application. The plug-in processing device 90 may include:

[0113] An acquiring unit 91 is configured to acquire plug-in version information, wherein the plug-in version information includes function information of a target plug-in to be generated;

[0114] The acquisition unit 91 is further configured to acquire a plug-in template associated with the target plug-in, and determine a retained function module and a to-be-processed function module from the function modules included in the plug-in template according to the function information;

[0115] The processing unit 92 is configured to compare the configuration files included in the to-be-processed functional module with the configuration files included in the reserved functional module to determine the configuration files to be cleared, wherein the configuration files to be cleared are configuration files that belong to the to-be-processed functional module and do not belong to the reserved functional module;

[0116] The processing unit 92 is further configured to perform a blanking process on the configuration file to be blanked to obtain a blanking configuration file;

[0117] The processing unit 92 is further configured to generate the target plug-in according to the cleared configuration file and the configuration file included in the reserved function module.

[0118] In one embodiment, the processing unit 92 is specifically configured to:

[0119] Saving file information of each configuration file included in the retention function module to the first storage space;

[0120] The acquisition unit 91 is specifically configured to:

[0121] Obtaining file information of a configuration file to be detected included in the function module to be processed, and detecting whether the file information of the configuration file to be detected is contained in the first storage space, where the configuration file to be detected is any configuration file included in the function module to be processed;

[0122] The processing unit 92 is further configured to:

[0123] If the file information of the configuration file to be detected is not included in the first storage space, determining the configuration file to be detected as a configuration file to be cleared;

[0124] The file information of the configuration file to be cleared is saved in the second storage space.

[0125] In one embodiment, the functional module includes one or more configuration items, each of which includes one or more configuration files; the processing unit 92 is specifically configured to:

[0126] Determine a first sub-storage space corresponding to each configuration item in the one or more configuration items, wherein each of the first sub-storage spaces constitutes a first storage space;

[0127] According to the configuration items to which the configuration files included in the reserved functional module belong, the file information of the configuration files included in the reserved functional module is saved in the corresponding first sub-storage space.

[0128] In one embodiment, the processing unit 92 is specifically configured to:

[0129] Determine the configuration item to which the configuration file to be detected belongs;

[0130] detecting whether file information of the configuration file to be detected is contained in a first sub-storage space corresponding to the configuration item to which the configuration file to be detected belongs;

[0131] The processing unit 92 is further configured to:

[0132] If the file information of the configuration file to be detected is not included in the first sub-storage space corresponding to the configuration item to which the configuration file to be detected belongs, it is determined that the file information of the configuration file to be detected is not included in the first storage space.

[0133] In one embodiment, the file information includes a file storage path of the configuration file, and the obtaining unit 91 is specifically configured to:

[0134] Obtaining a path configuration file of the plug-in template, wherein the path configuration file includes a file storage path of each configuration file included in the plug-in template;

[0135] The processing unit 92 is specifically configured to:

[0136] In the process of obtaining the various configuration files included in the plug-in template according to the path configuration file, if it is detected that the first file storage path included in the path configuration file is included in the second storage space, the configuration file corresponding to the obtained first file storage path is cleared to obtain a cleared configuration file;

[0137] Generate the target plug-in according to the cleared configuration file and the configuration file corresponding to the second file storage path included in the acquired path configuration file;

[0138] Among them, the first file storage path is any file storage path included in the path configuration file, and the second file storage path is any file storage path included in the path configuration file except the first file storage path; the configuration file corresponding to the first file storage path includes the configuration file to be cleared, and the configuration file corresponding to the second file storage path includes the configuration file of the retained functional module.

[0139] In one embodiment, the processing unit 92 is specifically configured to:

[0140] Performing a blanking process on the target files included in the configuration file to be blanked to obtain a blanking configuration file;

[0141] Among them, the target file includes one or more of the first category of files and the second category of files; the emptying processing of the first category of files includes deleting the file content of the first category of files; the emptying processing of the second category of files includes deleting the file content of the second category of files except the declaration information.

[0142] In one embodiment, the processing unit 92 is specifically configured to:

[0143] Determining, from the function modules included in the plug-in template, matching function modules that match the function information, wherein each matching function module can implement part or all of all functions indicated by the function information;

[0144] The matching functional module is determined as a reserved functional module, and the functional modules other than the matching functional module in the functional modules included in the plug-in template are determined as functional modules to be processed.

[0145] It can be understood that the functions of each functional unit of the plug-in processing device described in the embodiment of the present application can be specifically implemented according to the method in the above method embodiment. The specific implementation process can refer to the relevant description of the above method embodiment and will not be repeated here.

[0146] In an embodiment of the present application, the reserved functional module and the to-be-processed functional module are determined from the plug-in template associated with the target plug-in through the functional information of the target plug-in, and the configuration file belonging to the to-be-processed functional module and not belonging to the reserved functional module is determined as the to-be-emptied configuration file. The target plug-in is generated by emptying the configuration file to be empty and obtaining the empty configuration file, and the configuration file included in the reserved functional module, thereby effectively improving the plug-in development efficiency.

[0147] like Figure 10 As shown, Figure 10 This is a schematic diagram of the structure of a computer device provided by an embodiment of the present application. The internal structure of the computer device 100 is as follows Figure 10 As shown, it includes: one or more processors 101, memory 102, and communication interface 103. The processor 101, memory 102, and communication interface 103 can be connected via a bus 104 or other means. The embodiment of the present application takes the connection via the bus 104 as an example.

[0148] Among them, the processor 101 (or CPU (Central Processing Unit)) is the computing core and control core of the computer device 100. It can parse various instructions in the computer device 100 and process various data of the computer device 100. For example, the CPU can be used to parse the power on and off instructions sent by the user to the computer device 100 and control the computer device 100 to perform power on and off operations; for another example, the CPU can transmit various interactive data between the internal structures of the computer device 100, and so on. The communication interface 103 can optionally include a standard wired interface, a wireless interface (such as Wi-Fi, a mobile communication interface, etc.), which is controlled by the processor 101 to send and receive data. The memory 102 (Memory) is a memory device in the computer device 100 for storing computer programs and data. It can be understood that the memory 102 here can include both the built-in memory of the computer device 100 and the extended memory supported by the computer device 100. The memory 102 provides storage space that stores the operating system of the computer device 100, which may include but is not limited to: Windows system, Linux system, etc., and this application is not limited to this. Specifically, the processor 101 performs the following operations by running the computer program stored in the memory 102:

[0149] In one embodiment, the processor 101 is specifically configured to:

[0150] Obtaining plug-in version information, wherein the plug-in version information includes function information of the target plug-in to be generated;

[0151] Acquire a plug-in template associated with the target plug-in, and determine a reserved function module and a to-be-processed function module from the function modules included in the plug-in template according to the function information;

[0152] Comparing the configuration file included in the to-be-processed functional module with the configuration file included in the reserved functional module to determine the configuration file to be cleared, wherein the configuration file to be cleared is a configuration file belonging to the to-be-processed functional module and not belonging to the reserved functional module;

[0153] Performing a blanking process on the configuration file to be blanked to obtain a blanking configuration file;

[0154] The target plug-in is generated according to the blank configuration file and the configuration file included in the reserved function module.

[0155] In one embodiment, the processor 101 is specifically configured to:

[0156] Saving file information of each configuration file included in the retention function module to the first storage space;

[0157] Obtaining file information of a configuration file to be detected included in the function module to be processed, and detecting whether the file information of the configuration file to be detected is contained in the first storage space, where the configuration file to be detected is any configuration file included in the function module to be processed;

[0158] If the file information of the configuration file to be detected is not included in the first storage space, determining the configuration file to be detected as a configuration file to be cleared;

[0159] The processor 101 is further configured to:

[0160] The file information of the configuration file to be cleared is saved in the second storage space.

[0161] In one embodiment, the functional module includes one or more configuration items, each of which includes one or more configuration files; the processor 101 is specifically configured to:

[0162] Determine a first sub-storage space corresponding to each configuration item in the one or more configuration items, wherein each of the first sub-storage spaces constitutes a first storage space;

[0163] According to the configuration items to which the configuration files included in the reserved functional module belong, the file information of the configuration files included in the reserved functional module is saved in the corresponding first sub-storage space.

[0164] In one embodiment, the processor 101 is specifically configured to:

[0165] Determine the configuration item to which the configuration file to be detected belongs;

[0166] detecting whether file information of the configuration file to be detected is contained in a first sub-storage space corresponding to the configuration item to which the configuration file to be detected belongs;

[0167] Among them, it is also used for:

[0168] If the file information of the configuration file to be detected is not included in the first sub-storage space corresponding to the configuration item to which the configuration file to be detected belongs, it is determined that the file information of the configuration file to be detected is not included in the first storage space.

[0169] In one embodiment, the file information includes a file storage path of the configuration file, and the processor 101 is specifically configured to:

[0170] Obtaining a path configuration file of the plug-in template, wherein the path configuration file includes a file storage path of each configuration file included in the plug-in template;

[0171] In the process of obtaining the various configuration files included in the plug-in template according to the path configuration file, if it is detected that the first file storage path included in the path configuration file is included in the second storage space, the configuration file corresponding to the obtained first file storage path is cleared to obtain a cleared configuration file;

[0172] Generate the target plug-in according to the cleared configuration file and the configuration file corresponding to the second file storage path included in the acquired path configuration file;

[0173] Among them, the first file storage path is any file storage path included in the path configuration file, and the second file storage path is any file storage path included in the path configuration file except the first file storage path; the configuration file corresponding to the first file storage path includes the configuration file to be cleared, and the configuration file corresponding to the second file storage path includes the configuration file of the retained functional module.

[0174] In one embodiment, the processor 101 is specifically configured to:

[0175] Performing a blanking process on the target files included in the configuration file to be blanked to obtain a blanking configuration file;

[0176] Among them, the target file includes one or more of the first category of files and the second category of files; the emptying processing of the first category of files includes deleting the file content of the first category of files; the emptying processing of the second category of files includes deleting the file content of the second category of files except the declaration information.

[0177] In one embodiment, the processor 101 is specifically configured to:

[0178] Determining, from the function modules included in the plug-in template, matching function modules that match the function information, wherein each matching function module can implement part or all of all functions indicated by the function information;

[0179] The matching functional module is determined as a reserved functional module, and the functional modules other than the matching functional module in the functional modules included in the plug-in template are determined as functional modules to be processed.

[0180] In a specific implementation, the processor 101, communication interface 102, and memory 103 described in the embodiment of the present application can execute the implementation of the computer device described in a plug-in processing method provided in an embodiment of the present application, and can also execute the implementation described in a plug-in processing device provided in an embodiment of the present application, which will not be repeated here.

[0181] In an embodiment of the present application, the reserved functional module and the to-be-processed functional module are determined from the plug-in template associated with the target plug-in through the functional information of the target plug-in, and the configuration file belonging to the to-be-processed functional module and not belonging to the reserved functional module is determined as the to-be-emptied configuration file. The target plug-in is generated by emptying the configuration file to be empty and obtaining the empty configuration file, and the configuration file included in the reserved functional module, thereby effectively improving the plug-in development efficiency.

[0182] The present application also provides a computer-readable storage medium that stores instructions that, when executed on a computer, cause the computer to execute the plug-in processing method described in the present application. The specific implementation method can be found in the previous description and will not be repeated here.

[0183] The present application also provides a computer program product, which includes a computer program or computer instructions. When executed by a processor, the computer program or computer instructions implement the steps of the data processing method provided in the present application. The specific implementation method can be found in the above description and will not be repeated here.

[0184] The present application also provides a computer program comprising computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the data processing method provided in the present application. The specific implementation method can be found in the previous description and will not be repeated here.

[0185] It should be noted that for the aforementioned various method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that this application is not limited by the order of the actions described, because according to this application, some steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by this application.

[0186] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be completed by instructing related hardware through a program, and the program can be stored in a computer-readable storage medium, which may include: a flash drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0187] The above disclosure is only part of the embodiments of the present application, and certainly cannot be used to limit the scope of rights of the present application. Therefore, equivalent changes made according to the claims of the present application are still within the scope covered by the present application.

Claims

1. A plug-in processing method, characterized in that: The method comprises: Obtaining plug-in version information, wherein the plug-in version information includes function information of the target plug-in to be generated; Acquire a plug-in template associated with the target plug-in, and determine a reserved function module and a to-be-processed function module from the function modules included in the plug-in template according to the function information; Comparing the configuration file included in the to-be-processed functional module with the configuration file included in the reserved functional module to determine the configuration file to be cleared, wherein the configuration file to be cleared is a configuration file belonging to the to-be-processed functional module and not belonging to the reserved functional module; Performing a blanking process on the configuration file to be blanked to obtain a blanking configuration file; The target plug-in is generated according to the blank configuration file and the configuration file included in the reserved function module.

2. The method according to claim 1, characterized in that The comparing the configuration file included in the to-be-processed functional module with the configuration file included in the reserved functional module to determine the configuration file to be cleared includes: Saving file information of each configuration file included in the retention function module to the first storage space; Obtaining file information of a configuration file to be detected included in the function module to be processed, and detecting whether the file information of the configuration file to be detected is contained in the first storage space, where the configuration file to be detected is any configuration file included in the function module to be processed; If the file information of the configuration file to be detected is not included in the first storage space, determining the configuration file to be detected as a configuration file to be cleared; The method further comprises: The file information of the configuration file to be cleared is saved in the second storage space.

3. The method according to claim 2, characterized in that The functional module includes one or more configuration items, and each configuration item includes one or more configuration files; Saving the file information of each configuration file included in the retention function module to the first storage space includes: Determine a first sub-storage space corresponding to each configuration item in the one or more configuration items, wherein each of the first sub-storage spaces constitutes a first storage space; According to the configuration items to which the configuration files included in the reserved functional module belong, the file information of the configuration files included in the reserved functional module is saved in the corresponding first sub-storage space.

4. The method according to claim 3, characterized in that The detecting whether the file information of the configuration file to be detected is contained in the first storage space includes: Determine the configuration item to which the configuration file to be detected belongs; detecting whether file information of the configuration file to be detected is contained in a first sub-storage space corresponding to the configuration item to which the configuration file to be detected belongs; The method further comprises: If the file information of the configuration file to be detected is not included in the first sub-storage space corresponding to the configuration item to which the configuration file to be detected belongs, it is determined that the file information of the configuration file to be detected is not included in the first storage space.

5. The method according to any one of claims 2 to 4, characterized in that: The file information includes the file storage path of the configuration file; The step of performing a blanking process on the configuration file to be blanked to obtain a blanking configuration file, and generating the target plug-in according to the blanking configuration file and the configuration file included in the reserved function module, includes: Obtaining a path configuration file of the plug-in template, wherein the path configuration file includes a file storage path of each configuration file included in the plug-in template; In the process of obtaining the various configuration files included in the plug-in template according to the path configuration file, if it is detected that the first file storage path included in the path configuration file is included in the second storage space, the configuration file corresponding to the obtained first file storage path is cleared to obtain a cleared configuration file; Generate the target plug-in according to the cleared configuration file and the configuration file corresponding to the second file storage path included in the acquired path configuration file; Among them, the first file storage path is any file storage path included in the path configuration file, and the second file storage path is any file storage path included in the path configuration file except the first file storage path; the configuration file corresponding to the first file storage path includes the configuration file to be cleared, and the configuration file corresponding to the second file storage path includes the configuration file of the retained functional module.

6. The method according to claim 1, characterized in that The step of performing a blanking process on the configuration file to be blanked to obtain a blanking configuration file includes: Performing a blanking process on the target files included in the configuration file to be blanked to obtain a blanking configuration file; Among them, the target file includes one or more of the first category of files and the second category of files; the emptying processing of the first category of files includes deleting the file content of the first category of files; the emptying processing of the second category of files includes deleting the file content of the second category of files except the declaration information.

7. The method according to claim 1, characterized in that The step of determining the reserved functional modules and the to-be-processed functional modules from the functional modules included in the plug-in template according to the functional information includes: Determining, from the function modules included in the plug-in template, matching function modules that match the function information, wherein each matching function module can implement part or all of all functions indicated by the function information; The matching functional module is determined as a reserved functional module, and the functional modules other than the matching functional module in the functional modules included in the plug-in template are determined as functional modules to be processed.

8. A plug-in processing device, characterized in that: The device comprises: An acquiring unit, configured to acquire plug-in version information, wherein the plug-in version information includes function information of a target plug-in to be generated; The acquisition unit is further configured to acquire a plug-in template associated with the target plug-in, and determine a retained function module and a to-be-processed function module from the function modules included in the plug-in template according to the function information; a processing unit, configured to compare the configuration file included in the to-be-processed functional module with the configuration file included in the reserved functional module, and determine a configuration file to be cleared, wherein the configuration file to be cleared is a configuration file belonging to the to-be-processed functional module and not belonging to the reserved functional module; The processing unit is further configured to perform a blanking process on the configuration file to be blanked to obtain a blanking configuration file; The processing unit is further configured to generate the target plug-in according to the cleared configuration file and the configuration file included in the reserved function module.

9. A computer device, characterized in that: It includes a memory, a communication interface and a processor, wherein the memory, the communication interface and the processor are connected to each other; the memory stores a computer program, and the processor calls the computer program stored in the memory to execute the plug-in processing method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that A computer program is stored, and when the computer program is executed by a processor, the plug-in processing method according to any one of claims 1 to 7 is implemented.

11. A computer program product, characterized in that The computer program product includes a computer program or computer instructions, and when the computer program or computer instructions are executed by a processor, the steps of the plug-in processing method according to any one of claims 1 to 7 are implemented.

Images