CN113934405A

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

Info

Publication number: CN113934405A
Application number: CN202111237981.8A
Authority: CN
Inventors: 杨浩彬; 黄维
Original assignee: Shenzhen Tencent Domain Computer Network Co Ltd
Current assignee: Shenzhen Tencent Domain Computer Network Co Ltd
Priority date: 2021-10-21
Filing date: 2021-10-21
Publication date: 2022-01-14

Abstract

The application provides a plug-in processing method, a device, equipment, a storage medium and a computer program product, which can be applied to various fields or scenes such as cloud technology, artificial intelligence, block chains, vehicle-mounted, intelligent transportation, intelligent home, games and the like, and the method comprises the following steps: acquiring plug-in version information, wherein the plug-in version information comprises function information of a target plug-in to be generated; acquiring a plug-in template associated with a target plug-in, and determining a reserved function module and a function module to be processed from function modules included in the plug-in template according to function information; comparing the configuration file included by the functional module to be processed with the configuration file included by the reserved functional module, and determining a configuration file to be emptied; carrying out vacancy processing on the configuration file to be vacancy to obtain a vacancy configuration file; and generating the target plug-in according to the blank configuration file and the configuration file included by the reserved function module. Through the embodiment of the application, the development efficiency of the plug-in can be effectively improved.

Description

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

Technical Field

The present application relates to the field of computer technologies, 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

The plug-in is a program written by an application program interface following a certain specification and used for realizing an extended function on the basis of the original function of the application program, and the plug-in can only operate depending on the application program and cannot normally operate only depending on the plug-in. In the process of plug-in development, all codes are written manually, so that the problems of low development efficiency and the like exist.

Disclosure of Invention

The embodiment of the application provides a plug-in processing method, a plug-in processing device, a plug-in processing equipment, a storage medium and a computer program product, and the plug-in processing method, the plug-in processing device, the storage medium and the computer program product can effectively improve the development efficiency of plug-ins.

In one aspect, an embodiment of the present application provides a plug-in processing method, where the method includes:

acquiring plug-in version information, wherein the plug-in version information comprises function information of a target plug-in to be generated;

acquiring a plug-in template associated with the target plug-in, and determining a reserved function module and a function module to be processed from function modules included in the plug-in template according to the function information;

comparing the configuration file included by the functional module to be processed with the configuration file included by the reserved functional module, and determining a configuration file to be emptied, wherein the configuration file to be emptied is a configuration file which belongs to the functional module to be processed and does not belong to the reserved functional module;

carrying out vacancy processing on the configuration file to be vacant to obtain a vacancy configuration file;

and generating the target plug-in according to the vacancy configuration file and the configuration file included by the reserved function module.

In another aspect, an embodiment of the present application provides a plug-in processing apparatus, where the apparatus includes:

the system comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for acquiring plug-in version information which comprises 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 reserved function module and a function module to be processed from function modules included in the plug-in template according to the function information;

the processing unit is used for comparing the configuration file included by the functional module to be processed with the configuration file included by the reserved functional module and determining a configuration file to be emptied, wherein the configuration file to be emptied is the configuration file which belongs to the functional module to be processed and does not belong to the reserved functional module;

the processing unit is further configured to perform blanking processing 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 blanking configuration file and the configuration file included in the reserved function module.

Accordingly, an embodiment of the present application provides a computer device, where the computer device includes a processor, a communication interface, and a memory, where the processor, the communication interface, and the memory are connected to each other, where the memory stores a computer program, and the processor is configured to call the computer program to execute the plug-in processing method according to any one of the foregoing possible implementation manners.

Accordingly, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program, and a processor executes the computer program related to the plug-in processing method of any one of the foregoing possible implementations.

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

Accordingly, the embodiment of the present application further provides a computer program, where the computer program includes computer instructions, the computer instructions are stored in a computer-readable storage medium, a processor of a 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 by the embodiment of the present application.

In the embodiment of the application, a reserved function module and a function module to be processed are determined from a plug-in template associated with a target plug-in according to the function information of the target plug-in, a configuration file which belongs to the function module to be processed and does not belong to the reserved function module is determined as a configuration file to be nulled, and the target plug-in is generated according to a nulled configuration file obtained by carrying out nulled processing on the configuration file to be nulled and the configuration file included by the reserved function module; according to the plug-in processing method, only the configuration files which are not needed are processed by adopting the reverse thinking, so that the existing codes do not need to be reconstructed during plug-in development, and the development efficiency of the plug-ins can be effectively improved.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

Fig. 1 is a network architecture to which a plug-in processing method according to an embodiment of the present invention is applied;

FIG. 2 is a schematic diagram of a plug-in processing method according to an embodiment of the present disclosure;

fig. 3 is a schematic flowchart of a plug-in processing method according to an embodiment of the present application;

FIG. 4 is a schematic view of an interposer template provided in an embodiment of the present application;

fig. 5 is a schematic flowchart of another plug-in processing method according to an embodiment of the present application;

FIG. 6 is a schematic diagram of dependencies between analysis modules provided in an embodiment of the present application;

FIG. 7 is a diagram illustrating configuration items provided by an embodiment of the present application;

fig. 8 is a schematic flowchart of another plug-in processing method according to an embodiment of the present application;

fig. 9 is a schematic structural diagram of a card processing apparatus according to an embodiment of the present application;

fig. 10 is a schematic structural diagram of a computer device according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

It should be noted that the descriptions of "first", "second", etc. referred to in the embodiments of the present application are only for descriptive purposes and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a technical feature defined as "first," "second," etc. may explicitly or implicitly include at least one of the feature.

For a better understanding of the embodiments of the present application, some terms referred to in the embodiments of the present application will be described below:

WXML or filename WXML: the structure file is represented, and the structure file can be used for constructing a page by combining a basic component and an event system.

WXSS or filename. WXSS: a presentation style file, typically used with a structure file, describes the component styles, i.e., describes how the components defined in the structure file should be displayed.

JS or filename. JS: representing a logic file, the business logic responsible for the page, such as lifecycle, binding process of events, initialization of data, etc.

JSON or filename JSON: a presentation property file for configuring static data such as background color of a window, background color of a navigation bar, title text content of a navigation bar, etc.

Plug-in components: is a program written in an application program interface following a certain specification.

A functional module: is a collection of program elements, such as data descriptions, executable statements, etc., that are functional components capable of performing one or more functions. When the plug-in is developed, the plug-in can be generated by modularized processing and an application program formed by packaging different functional modules.

In order to effectively improve the development efficiency of the plug-ins, the application provides a plug-in processing method, which performs blanking processing (or deletion processing) on modules in the plug-ins based on module deletion to generate different plug-in versions (or new plug-ins), so that the development efficiency of the plug-ins is effectively improved. The plug-in processing method may be implemented based on Cloud technology (Cloud technology). The cloud technology is a general term of network technology, information technology, integration technology, management platform technology, application technology and the like applied based on a cloud computing business model, can form a resource pool, is used as required, and is flexible and convenient. Cloud computing technology will become an important support. Background services of the technical network system require a large amount of computing and storage resources, such as video websites, picture-like websites and more web portals. With the high development and application of the internet industry, each article may have its own identification mark and needs to be transmitted to a background system for logic processing, data in different levels are processed separately, and various industrial data need strong system background support and can only be realized through cloud computing.

In a possible embodiment, the plug-in processing method provided in the embodiment of the present application may also be implemented based on Artificial Intelligence (AI) and/or block chain technology. And particularly, the method can relate to one or more of distributed storage and big data processing technology in the artificial intelligence basic technology. For example, the generated plug-ins are stored in a distributed manner on a plurality of independent devices. For another example, the data required to execute the plug-in processing method may be stored in the form of blocks on a block chain; data (such as configuration files, file information, file storage paths and the like) generated by executing the data processing method can be stored on the block chain in the form of blocks; in addition, the computer device executing the plug-in processing method may be a node device in a blockchain network.

The plug-in processing method provided by the embodiment of the application can be applied to the network architecture shown in fig. 1. The computer device 10 shown in fig. 1 may be a server or a terminal having a data processing function, where the server may be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, or a cloud server providing basic cloud computing services such as a cloud service, a cloud database, cloud computing, a cloud function, a cloud storage, a network service, cloud communication, a middleware service, a domain name service, a security service, a CDN, and a big data and artificial intelligence platform. The terminal may be, but is not limited to, a smart phone, a tablet computer, a notebook computer, a desktop computer, an intelligent voice interaction device, an intelligent appliance, a vehicle-mounted terminal, and the like. The terminal 11 shown in fig. 1 is connected to the computer device 10 via a network. The plug-in processing method provided by the embodiment of the present application may be executed by the computer device 10, specifically:

the computer device 10 determines a reserved function module and a function module to be processed from a plug-in template associated with the target plug-in according to the function information of the target plug-in, determines a configuration file that belongs to the function module to be processed and does not belong to the reserved function module as a configuration file to be nulled, generates the target plug-in according to the nulled configuration file obtained by nulled processing on the configuration file to be nulled and the configuration file included in the reserved function module, for example, as shown in fig. 2, for a component R (which may be understood as a plug-in template), the component R includes the configuration file: wxml, a.wxss, a.js, a.json, expansion wxml and entry wxml, when the expansion wxml is determined to be the configuration file to be emptied, emptying can be carried out on the expansion wxml in the component R, and the component R after emptying can be used as a new plug-in; therefore, the reverse thinking is adopted to process only the unnecessary configuration files, so that the existing codes do not need to be reconstructed during the plug-in development, and the development efficiency of the plug-ins can be effectively improved.

In an embodiment, the computer device 10 may provide the target plug-in to the terminal 11, and the terminal 11 may deploy the target plug-in on the application to provide the extended function for the application. Or, the computer device 10 may receive a deployment request for the target plug-in sent by the terminal 11, and after the audit is passed, the computer device 10 deploys the target plug-in on the application program. The application program may specifically be an applet, a browser program, or the like.

It should be understood that the network architecture diagram described in the embodiment of the present application is for more clearly illustrating the technical solution of the embodiment of the present application, and does not constitute a limitation to the technical solution provided in the embodiment of the present application, and as a person having ordinary skill in the art knows that along with the evolution of the system architecture and the appearance of a new service scenario, the technical solution provided in the embodiment of the present application is also applicable to similar technical problems.

The plug-in processing method provided by the embodiment of the present application is briefly introduced above, and a specific implementation manner of the plug-in processing method is explained in detail below.

Referring to fig. 3, fig. 3 is a schematic flowchart illustrating a plug-in processing method according to an embodiment of the present disclosure. The plug-in processing method includes but is not limited to the following steps:

s301, obtaining plug-in version information, wherein the plug-in version information comprises function information of a target plug-in to be generated.

In the embodiment of the present application, the target plug-in to be generated is any type of plug-in, for example, the target plug-in may include an applet plug-in, a browser plug-in, and the like. The plug-in version information is version information of the target plug-in, and may include one or more of a plug-in name, a plug-in version number, a plug-in version identification, and a plug-in type as an identity of the target plug-in. In addition, the plug-in version information also includes function information of the target plug-in, which is used to indicate a target that the target plug-in needs to reach or a function that is implemented, for example, the target plug-in is a live plug-in, and the function information may be a function module that is needed by live broadcast or described as a plug-in for live broadcast.

In the embodiment of the application, the computer device can output the configuration interface, a developer of the plug-in can configure the function information of the target plug-in the configuration interface, and the computer device obtains the function information of the target plug-in configured by the developer and automatically generates the target plug-in based on a subsequent process according to the guidance of the function information.

In one embodiment, the configuration interface can provide options of various functional modules for a developer of the plug-in to select, and the functional module selected by the developer is used as the functional information of the target plug-in; and a developer can input the functional module required by the target plug-in as the requirement information of the target plug-in on a configuration interface.

In another embodiment, the developer may define a function module required by the target plug-in a project configuration file of the target plug-in, and use the function module as function information of the target plug-in (where one or more of a plug-in name, a plug-in version number, a plug-in version identification, and a plug-in type may also be defined in the project configuration file), for example, the project configuration file may be a package json file, and the developer may configure the function module required by the target plug-in by configuring a script field in the package json file, as shown below as an example configured for the script field in the package json file:

“scripts”:{

“build-expand”:“gulp build—-expand”

}

in an embodiment, the computer device may perform entry processing on the project configuration file to obtain the function module required by the target plug-in, for example, the computer device may execute a packet by running a gulp tool through npm to obtain an execution script npm run built-extended, and may obtain a parameter extended in the execution script to determine that the function module required by the target plug-in is an extended function (extended).

Wherein, gulp is a flow-based automated building tool; nmp is a package management tool installed along with NodeJS.

S302, obtaining a plug-in template associated with the target plug-in, and determining a reserved function module and a function module to be processed from function modules included in the plug-in template according to the function information.

In this embodiment of the application, the plug-in template associated with the target plug-in includes one or more function modules, and some or all of all functions indicated by the function information of the target plug-in can be implemented by a function module in the one or more function modules, that is, one function module can implement all functions indicated by the function information, or one function module can implement part of functions indicated by the function information, and a plurality of function modules can implement all functions indicated by the function information together.

In an embodiment, the manner for the computer device to obtain the plug-in template associated with the target plug-in is specifically: one is that: acquiring function information of a target plug-in and function information of a plurality of plug-in modules, comparing the function information of the target plug-in with function information of a plurality of plug-in templates, and if the function information of the plug-in template is matched with the function information of the target plug-in (namely the plug-in template includes all functions required by the target plug-in), determining the plug-in template as a plug-in template associated with the target plug-in, for example, the function information of the target plug-in A indicates that the function module required by the target plug-in A is: function module 1, function module 2, the function information instruction plug-in components template B of plug-in components template B includes the function module be: the functional module 1, the functional module 2 and the functional module 3, the plug-in module B comprises all functions required by the target plug-in A, and the plug-in module B is used as a plug-in template associated with the target plug-in A; one is that: the plug-in version number of the plug-in template may be taken as the common version number, and when the common version number of the plug-in template is included in the plug-in version number of the target plug-in, 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 the 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 common version number 11.102.112 is included in the plug-in version number of the target plug-in a, and the plug-in module B is taken as the plug-in template associated with the target plug-in a.

In an embodiment, determining the reserved function module and the function module to be processed from the function modules included in the plug-in template according to the function information specifically includes: and determining a matching function module matched with the function information of the target plug-in from the function modules (the plug-in version associated with the target plug-in) included by the plug-in template, determining the matching function module as a reserved function module, and determining the function modules except the matching function module in the function modules included by the plug-in template as the function modules to be processed.

In the embodiment of the present application, the matching function module may implement part or all of all functions indicated by the function information of the target plug-in. And taking the matched functional module as a reserved functional module, namely the reserved functional module can realize part or all of all functions indicated by the functional information of the target plug-in. That is, one reservation module (or matching function) may implement all functions indicated by the function information, or one reservation module (or matching function) may implement part of the functions indicated by the function information, and a plurality of reservation modules (or matching functions) may collectively implement all the functions indicated by the function information. The function module to be processed is a function module which cannot realize part or all of the functions indicated by the function information of the target plug-in, and may be understood as a function module which is not required by the target plug-in when the target plug-in is generated.

Although all functions indicated by the function information of the target plug-in can be realized by using the required function module, because there is often coupling between function modules, if all configuration files included in the function module to be processed are directly cleaned up, an error may be reported because the required configuration files cannot be found when the plug-in is compiled (because the function modules share the same configuration file by using the same file storage path). Please refer to fig. 4, fig. 4 is an exemplary diagram of a plug-in template, which includes an expansion function module, a reflow function module, an entry function module, and a privileged function module, and it can be seen that the expansion function module and the entry function module exist in a common component a, so that a coupled component a exists between the expansion function module and the entry function module, when a target plug-in only needs to expand the function module and the reflow function module, if a configuration file of the entry function module is directly deleted, when the expansion function module in the target plug-in is compiled, a configuration file of the component a pointed by a file storage path does not exist, an error is reported, and therefore, after determining to retain the function module and the function module to be processed, a coupling relationship (or a dependency relationship) between the modules can be further analyzed.

S303, comparing the configuration file included in the to-be-processed function module with the configuration file included in the reserved function module, and determining a to-be-nulled configuration file, where the to-be-nulled configuration file is a configuration file that belongs to the to-be-processed function module and does not belong to the reserved function module.

In the embodiment of the application, the configuration file of the functional module is reserved as the configuration file required by the target plug-in; the configuration file of the module to be processed is a functional module which is not needed by the target plug-in; the configuration file to be emptied is a configuration file which belongs to the function module to be processed and does not belong to the reserved function module, and is not needed by the target plug-in.

In one embodiment, in order to analyze the dependency relationship between the reserved function module and the function module to be processed, the configuration file included in the function module to be processed may be compared with the configuration file included in the reserved function module to determine the configuration file belonging to the function module to be processed but not to the reserved function module, and be used as the configuration file to be emptied, for example, the reserved function module a includes the configuration file a.wxml, the reserved function module B includes the configuration file b.wxml, and the function module C to be processed includes the configuration files a.wxml and c.wxml, it can be seen that there is a common configuration file a.wxml for the reserved function module a and the function module C to be processed, the configuration file belongs to the function module to be processed and belongs to the reserved function 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 function module C and does not belong to the reserved function module a, and does not belong to reserved function module B, so the configuration file c.wxml is the to-be-nulled configuration file.

In an embodiment, comparing the configuration file included in the to-be-processed function module with the configuration file included in the reserved function module, and determining the to-be-nulled configuration file specifically includes: the file information of each configuration file included by the reserved function module is stored in a first storage space, the file information of the configuration file to be detected included by the function module to be processed is obtained, whether the file information of the configuration file to be detected is contained in the first storage space or not is detected, and if the file information of the configuration file to be detected is not contained in the first storage space, the configuration file to be detected is determined to be the configuration file to be empty.

In the embodiment of the application, the configuration file to be detected is any configuration file in the functional module to be processed. The file information is an identifier of the configuration file, for example, a file storage path, such as a file indicated by a file storage path indicated by components/hello-components, where the configuration file is a file indicated by a directory hello-component in directory components, an encryption password of the file storage path, or a file name (at this time, it is ensured that the file name of the configuration file is unique). The first storage space is a storage space created for the reserved function module and used for storing file information of the configuration file included in the reserved function module, and the storage space may be a container (a group of processes that are limited by resources and isolated from each other).

In an embodiment, a first storage space is created for the reserved function module, file information of a configuration file included in the reserved function module is stored in the first storage space, whether the file information of the configuration file to be detected is included in the first storage space is detected for a configuration file to be detected (any configuration file in the function modules to be processed) in the function modules to be processed, if the file information of the configuration file to be detected is included in the first storage space, it is indicated that the configuration file to be detected belongs to the reserved function module, and if the file information of the configuration file to be detected is not included in the first storage space, it is indicated that the configuration file to be detected belongs to the function module to be processed, and does not belong to the reserved function module, and is the configuration file to be emptied.

In the embodiment of the application, the file information of the configuration files is compared to determine the configuration files to be emptied, rather than directly comparing the configuration files, so that the determining efficiency of the configuration files to be emptied can be improved, and the generation efficiency of the plug-ins is improved.

S304, carrying out vacancy processing on the configuration file to be vacant to obtain a vacancy configuration file.

It should be explained that the to-be-nulled configuration file is a configuration file that is not needed by the target plugin, but if the to-be-nulled configuration file is directly deleted, error reporting may also occur when the plugin is compiled, because the present application compiles the target plugin according to the compiling rule of the plugin template (considering that there is a problem of low efficiency in re-formulating the compiling rule of the target plugin by developers), the compiling rule of the plugin template still indicates to compile the to-be-nulled configuration file, and if the to-be-nulled configuration file is directly deleted, an error reporting may occur because the to-be-nulled configuration file cannot be found, so the nulled configuration file that only the null statement is retained by the computer device may be processed according to the compiling rule of the plugin template by the nulled processing.

In an embodiment of the present application, the to-be-nulled configuration files include a first type of file or a second type of file (i.e., a target file), and in an embodiment, different nulling processing manners are adopted for different types of to-be-nulled configuration files, specifically: the step of blanking the first type of files comprises deleting the file contents of the first type of files, and the step of blanking the second type of files comprises deleting the file contents of the second type of files except the sounding information.

In the embodiment of the application, the first type of files comprise structure files and style files, and the second type of files comprise logic files and attribute files. The process of blanking the structure file and the style file is to delete the file contents of the structure file and the style file, which is equivalent to changing the structure file and the style file into empty characters.

In an embodiment, the emptying processing for the logic file included in the second class of files is to delete the file contents of the logic file except the first declaration information (declared according to the program specification defined by the logic file), for example, as shown in the following, the code in the logic file declares Page ({ }) as the first declaration information, and the empty configuration file obtained by the logic file only includes Page ({ }).

In an embodiment, the property file included in the second class of files is subjected to blanking processing, namely, the file contents of the property file except the second declaration information (declaration defined according to the program specification indicated by the property file) are deleted, for example, if the Page declaration { "Page": true } in the property file of the component is the second declaration information, the blanking configuration file finally obtained for the property file only includes { "Page": true }.

S305, generating the target plug-in according to the blank configuration file and the configuration file included by the reserved function module.

In an embodiment, the configuration file included in the blank configuration file and the configuration file included in the reserved function module are compressed to obtain a package of the target plug-in, and the package of the target plug-in is installed on an application program (for example, an applet) to provide an extension function for the application program.

In an embodiment, the target plug-in may further comprise a configuration file that does not belong to the reserved function module and does not belong to the pending function module, i.e. that belongs exclusively to the target plug-in.

In the embodiment of the application, the reserved function module and the function module to be processed are determined from the plug-in template associated with the target plug-in through the function information of the target plug-in, the configuration file which belongs to the function module to be processed and does not belong to the reserved function module is determined as the configuration file to be vacant, the vacant configuration file obtained by performing vacant processing on the vacant configuration file and the configuration file included by the reserved function module generates the target plug-in, only the configuration file which is not needed is processed by adopting reverse thinking, so that the existing code is not needed to be reconstructed during plug-in development, the development efficiency of the plug-in can be effectively improved, meanwhile, the problem that different developers have different abilities and influence the plug-in code quality is solved, and the plug-in code quality can be effectively guaranteed.

Referring to fig. 5, fig. 5 is a schematic flowchart illustrating another plug-in processing method according to an embodiment of the present disclosure. The plug-in processing method includes but is not limited to the following steps:

s501, obtaining plug-in version information, wherein the plug-in version information comprises function information of a target plug-in to be generated.

S502, obtaining a plug-in template associated with the target plug-in, and determining a reserved function module and a function module to be processed from function modules included in the plug-in template according to the function information.

For details of the implementation processes of steps S501 and S502, reference may be made to steps S301 and S302, which are not described again in this embodiment.

S503, saving the file storage paths of the configuration files included in the reserved function module to a first storage space, if the file storage paths of the configuration files to be detected are not included in the first storage space, determining the configuration files to be detected as configuration files to be emptied, and saving the file storage paths of the configuration files to be emptied to a second storage space, wherein the configuration files to be detected are any configuration files included in the function modules to be processed.

In this embodiment of the present application, the first storage space is a storage space of the reserved function module and may be used to store a file storage path of the configuration file of the reserved function module, the second storage space is a storage space for the function module to be processed and may be used to store a file storage path of the configuration file to be emptied, and the first storage space and the second storage space may be containers.

In an embodiment, the computer device saves the file storage path of the configuration file included in the reserved function module to the first storage space, please refer to fig. 6, in fig. 6, the file storage path of the configuration file a.wxml included in the reserved function module a and the file storage path of the configuration file b.wxml included in the reserved function module B are saved to the first storage space, 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 emptied, and the file storage path of the configuration file to be emptied is saved to the second storage space, for example, the file storage path of the configuration file a.wxml included in the functional module C to be processed shown in fig. 6 is in the first storage space, then the configuration file a.wxml to be detected is not a configuration file to be emptied, and if the file storage path of the to-be-detected configuration file c.wxml included in the to-be-processed functional module C is not in the first storage space, the to-be-detected configuration file c.wxml is a to-be-nulled configuration file, and the file storage path of the to-be-nulled configuration file c.wxml is stored in the second storage space.

S504, obtaining a path configuration file of the plug-in template, wherein the path configuration file comprises file storage paths of all configuration files included in the plug-in template.

In this embodiment of the present application, the path configuration file of the plug-in template includes file storage paths of all configuration files included in the plug-in template, and the computer device may 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 compiling rule of the plug-in template.

S505, in the process of acquiring each configuration file included in the plug-in template according to the path configuration file, if it is detected that a first file storage path included in the path configuration file is included in the second storage space, performing vacancy processing on the configuration file corresponding to the acquired first file storage path to obtain a vacancy configuration file.

In this 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 to-be-nulled configuration file.

In an embodiment, a computer device executes a compiling task of a target plug-in according to a path configuration file (that is, obtains all configuration files included in a plug-in template), and when detecting that a first file storage path included in the path configuration file is in a second storage space, indicates that the configuration file corresponding to the first file storage path is a to-be-nulled configuration file, obtains the configuration file corresponding to the first file storage path, and performs nulled processing on the configuration file corresponding to the first file storage path to obtain a nulled configuration file.

S506, generating the target plug-in according to the vacancy configuration file and the configuration file corresponding to the second file storage path included in the acquired path configuration file.

In this embodiment of the 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 the retention function module.

In an embodiment, when it is detected that a 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 the configuration file of the reserved function module, the configuration file corresponding to the second file storage path is obtained.

In an embodiment, the path configuration file may include a configuration file that belongs exclusively to the plug-in template and does not belong to the reserved function module and the function module to be processed, and 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 the file storage path may be acquired as the configuration file included in the target plug-in.

In the embodiment of the application, the file storage path included by the plug-in template is saved in the corresponding storage space, so that when the target plug-in is compiled, whether to perform the vacancy processing or not can be determined through the storage space to which the file storage path of the configuration file belongs, the generation efficiency of the target plug-in can be improved, meanwhile, the vacancy processing is performed on the configuration file to be vacancy in the plug-in template, so that the existing code does not need to be reconstructed during plug-in development, and the development efficiency of the plug-in can be effectively improved.

In one embodiment, the function module includes one or more configuration items, each configuration item includes one or more configuration files, please refer to fig. 7, and the function module shown in fig. 7 includes configuration items: component entry, page entry, WXML full path, WXSS full path, Behaviour full path, and JS full path.

In the embodiment of the application, the component entry comprises all components in the functional module, and each component comprises one or more of a structure file, a style file, a logic file and a property file; the page entry comprises all pages in the functional module, and each page comprises one or more of a structure file, a style file, a logic file and a property file; the WXML full path comprises one or more of a structure file of the component and a structure file of the page; the WXSS full path comprises one or more of a style file of the component and a style file of the page; the Behaviour full path comprises logic files (such as an initialization component and a destruction component) related to the life cycle and data initialization in the functional module; the JS full path includes the logical files in the function module that are relevant to the binding process of the event (e.g., component trigger events).

In an embodiment, the computer device may generate a target plug-in based on the configuration project, specifically: determining a first sub-storage space corresponding to each configuration item in the one or more configuration items, for example, setting corresponding first sub-storage spaces for a configuration item component entry, a page entry, a WXML full path, a WXSS full path, a Behaviour full path, and a JS full path in fig. 8, respectively, and saving a file storage path of a configuration file included in the retention function module to the corresponding first sub-storage space according to the configuration item to which each configuration file included in the retention function module belongs, for example, saving a file storage path of a configuration file included in a page entry to a storage space to which the page entry belongs.

In another embodiment, each configuration item may directly include a file storage path for one or more configuration files, e.g., a configuration item directly includes a file storage path for all components in a functional module.

Further, the computer device determines a configuration item to which the configuration file to be detected belongs, detects whether a file storage path of the configuration file to be detected is included in a first sub-storage space corresponding to the configuration item to which the configuration file to be detected belongs, determines the configuration file to be detected as a configuration file to be nulled if the file storage path of the configuration file to be detected is not included in the first storage space, and stores the file storage path of the configuration file to be nulled to a second storage space. Each of the first sub-storage spaces constitutes a first storage space.

In another embodiment, the computer device may determine a second sub-storage space corresponding to each configuration item in the one or more configuration items, determine a configuration item to which the configuration file to be detected belongs, detect whether a file storage path of the configuration file to be detected is included in a first sub-storage space corresponding to the configuration item to which the configuration file to be detected belongs, determine the configuration file to be detected as a configuration file to be nulled if the file storage path of the configuration file to be detected is not included in the first storage space, and store the file storage path of the configuration file to be nulled to the second sub-storage space to which the configuration file to be nulled belongs. Wherein each second sub-storage space constitutes a second storage space.

Through the embodiment, a corresponding second sub-storage space can be created for the configuration item of the function module to be processed, and the second sub-storage space can be used for storing the file storage path of the to-be-nulled configuration file of the function module to be processed.

Further, in the process that the computer device obtains each configuration file included in the plug-in template according to the path configuration file, if it is detected that a 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 subjected to vacancy processing to obtain a vacancy 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 a second file storage path included in the path configuration file is obtained, and the target plug-in is generated according to the vacancy configuration file and the configuration file corresponding to the second file storage path included in the obtained path configuration file.

Specifically, as shown in fig. 8, the computer device may detect whether a file storage path included in the path configuration file is in a storage space (including a first storage space and a second storage space), and if not, indicate that the configuration file corresponding to the file storage path does not belong to the reserved function module or the to-be-processed function module, and directly compress the configuration file corresponding to the file storage path; 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, and 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 subjected to vacancy processing to obtain a vacancy configuration file, and the vacancy configuration file is subjected to compression processing, so that the target plug-in is obtained.

In an embodiment, each configuration item of the target plug-in may correspond to a sub-path configuration file (including file storage paths of all configuration files in each configuration item), and the computer device may compile the target plug-in using parallel tasks, where each task is responsible for traversing one configuration item to generate the target plug-in, and may improve generation efficiency of the target plug-in.

In the embodiment of the application, the file storage paths of all the configuration files included in the configuration project are stored in the corresponding sub-storage spaces, and the sub-storage spaces are respectively used for determining the configuration files to be nulled, so that the generation efficiency of the template plug-in can be improved, and meanwhile, only the configuration files to be nulled in the plug-in template are processed, so that the existing codes do not need to be reconstructed during plug-in development, and the development efficiency of the plug-in can be effectively improved.

While the method of the embodiments of the present application has been described in detail above, to facilitate better implementation of the above-described aspects of the embodiments of the present application, the apparatus of the embodiments of the present application is provided below accordingly. Referring to fig. 9, fig. 9 is a schematic structural diagram of a card processing apparatus according to an exemplary embodiment of the present application, where the card processing apparatus 90 may include:

an obtaining unit 91, configured to obtain plug-in version information, where the plug-in version information includes function information of a target plug-in to be generated;

the obtaining unit 91 is further configured to obtain a plug-in template associated with the target plug-in, and determine a reserved function module and a function module to be processed from function modules included in the plug-in template according to the function information;

the processing unit 92 is configured to compare a configuration file included in the to-be-processed functional module with a configuration file included in the reserved functional module, and determine a to-be-nulled configuration file, where the to-be-nulled configuration file is a configuration file that belongs to the to-be-processed functional module and does not belong to the reserved functional module;

the processing unit 92 is further configured to perform blanking processing on the configuration file to be blanked to obtain a blanking configuration file;

the processing unit 92 is further configured to generate the target plug-in according to the blanking configuration file and the configuration file included in the reserved function module.

In an embodiment, the processing unit 92 is specifically configured to:

storing the file information of each configuration file included in the reserved function module to a first storage space;

the obtaining unit 91 is specifically configured to:

acquiring file information of a to-be-detected configuration file included by the to-be-processed function module, and detecting whether the file information of the to-be-detected configuration file is contained in the first storage space, wherein the to-be-detected configuration file is any one configuration file included by the to-be-processed function module;

the processing unit 92 is further configured to:

if the file information of the configuration file to be detected is not contained in the first storage space, determining the configuration file to be detected as a configuration file to be emptied;

and storing the file information of the configuration file to be emptied into a second storage space.

In one embodiment, the function module includes one or more configuration items, each configuration item including one or more configuration files; the processing unit 92 is specifically configured to:

determining a first sub-storage space corresponding to each configuration item in the one or more configuration items, wherein each first sub-storage space constitutes a first storage space;

and according to the configuration items to which the configuration files included in the reserved function module belong, storing the file information of the configuration files included in the reserved function module to the corresponding first sub-storage space.

In an embodiment, the processing unit 92 is specifically configured to:

determining a configuration item to which the configuration file to be detected belongs;

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

wherein the processing unit 92 is further configured to:

and if the file information of the configuration file to be detected is not contained in the first sub-storage space corresponding to the configuration project to which the configuration file to be detected belongs, determining that the file information of the configuration file to be detected is not contained in the first storage space.

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

acquiring a path configuration file of the plug-in template, wherein the path configuration file comprises a file storage path of each configuration file included in the plug-in template;

the processing unit 92 is specifically configured to:

in the process of acquiring each configuration file included in the plug-in template according to the path configuration file, if it is detected that a first file storage path included in the path configuration file is included in the second storage space, performing null processing on the configuration file corresponding to the acquired first file storage path to obtain a null configuration file;

generating the target plug-in according to the vacancy configuration file and a configuration file corresponding to a second file storage path included in the acquired path configuration file;

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 for the first file storage path; the configuration file corresponding to the first file storage path comprises the configuration file to be emptied, and the configuration file corresponding to the second file storage path comprises the configuration file of the reserved function module.

In an embodiment, the processing unit 92 is specifically configured to:

performing vacancy processing on a target file included in the configuration file to be vacant to obtain a vacancy configuration file;

wherein the target file comprises one or more of a first type of file and a second type of file; the blank processing of the first type of file comprises deleting the file content of the first type of file; the blank processing of the second type of file comprises deleting the file contents of the second type of file except the declaration information.

In an embodiment, the processing unit 92 is specifically configured to:

determining matched function modules matched with the function information from function modules included in the plug-in template, wherein each matched function module can realize part or all of all functions indicated by the function information;

and determining the matched function module as a reserved function module, and determining the function modules except the matched function module in the function modules included in the plug-in template as function modules to be processed.

It can be understood that the functions of the functional units of the plug-in processing device described in the embodiment of the present application may be specifically implemented according to the method in the foregoing method embodiment, and the specific implementation process may refer to the description related to the foregoing method embodiment, which is not described herein again.

In the embodiment of the application, the reserved function module and the function module to be processed are determined from the plug-in template associated with the target plug-in through the function information of the target plug-in, the configuration file which belongs to the function module to be processed and does not belong to the reserved function module is determined as the configuration file to be nulled, the nulled configuration file obtained by carrying out nulled processing on the configuration file to be nulled and the configuration file included by the reserved function module are used for generating the target plug-in, and therefore the development efficiency of the plug-in can be effectively improved.

As shown in fig. 10, fig. 10 is a schematic structural diagram of a computer device provided in an embodiment of the present application, and an internal structure of the computer device 100 is shown in fig. 10, and includes: one or more processors 101, memory 102, and a communication interface 103. The processor 101, the memory 102 and the communication interface 103 may be connected by a bus 104 or other means, and the embodiment of the present application is exemplified by being connected by the bus 104.

The processor 101 (or CPU) is a computing core and a control core of the computer device 100, and can analyze various instructions in the computer device 100 and process various data of the computer device 100, for example: the CPU may be configured to analyze a power on/off instruction sent by the user to the computer device 100, and control the computer device 100 to perform power on/off operation; the following steps are repeated: the CPU may transfer various types of interactive data between the internal structures of the computer device 100, and so on. The communication interface 103 may optionally include a standard wired interface, a wireless interface (e.g., Wi-Fi, mobile communication interface, etc.), controlled by the processor 101 for transceiving data. The Memory 102(Memory) is a Memory device in the computer device 100 for storing computer programs and data. It is understood that the memory 102 herein may comprise both the built-in memory of the computer device 100 and, of course, the expansion memory supported by the computer device 100. Memory 102 provides storage space that stores an operating system of computer device 100, which may include, but is not limited to: windows system, Linux system, etc., which are not limited in this application. Specifically, the processor 101 executes the following operations by executing the computer program stored in the memory 102:

in an embodiment, the processor 101 is specifically configured to:

In an embodiment, the processor 101 is specifically configured to:

wherein the processor 101 is further configured to:

In one embodiment, the function module includes one or more configuration items, each configuration item including one or more configuration files; the processor 101 is specifically configured to:

In an embodiment, the processor 101 is specifically configured to:

wherein, still be used for:

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

In an embodiment, the processor 101 is specifically configured to:

In a specific implementation, the processor 101, the communication interface 102, and the memory 103 described in this embodiment of the present application may execute an implementation manner of a computer device described in a plug-in processing method provided in this embodiment of the present application, and may also execute an implementation manner described in a plug-in processing apparatus provided in this embodiment of the present application, which is not described herein again.

The embodiment of the present application further provides a computer-readable storage medium, in which instructions are stored, and when the computer-readable storage medium runs on a computer, the computer is caused to execute the plug-in processing method according to the embodiment of the present application. For specific implementation, reference may be made to the foregoing description, which is not repeated herein.

Embodiments of the present application further provide a computer program product, where the computer program product includes a computer program or computer instructions, and when the computer program or the computer instructions are executed by a processor, the steps of the data processing method provided in the embodiments of the present application are implemented. For specific implementation, reference may be made to the foregoing description, which is not repeated herein.

The embodiment of the present application further provides a computer program, where the computer program includes computer instructions, the computer instructions are stored in a computer-readable storage medium, a processor of a 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 data processing method provided in the embodiment of the present application. For specific implementation, reference may be made to the foregoing description, which is not repeated herein.

It should be noted that, for simplicity of description, the above-mentioned embodiments of the method are described as a series of acts or combinations, but those skilled in the art should understand that the present application is not limited by the order of acts described, as some steps may be performed in other orders or simultaneously according to the present application. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required in this application.

Those skilled in the art will appreciate that all or part of the steps in the methods of the above embodiments may be implemented by associated hardware instructed by a program, which may be stored in a computer-readable storage medium, and the storage medium may include: flash disks, Read-Only memories (ROMs), Random Access Memories (RAMs), magnetic or optical disks, and the like.

The above disclosure is only a few examples of the present application, and certainly should not be taken as limiting the scope of the present application, which is therefore intended to cover all modifications that are within the scope of the present application and which are equivalent to the claims.

Claims

1. A method for plug-in processing, the method comprising:

2. The method according to claim 1, wherein the comparing the configuration file included in the functional module to be processed with the configuration file included in the reserved functional module to determine a configuration file to be nulled comprises:

wherein the method further comprises:

3. The method of claim 2, wherein the function module comprises one or more configuration items, each configuration item comprising one or more configuration files;

the saving the file information of each configuration file included in the reserved function module to a first storage space includes:

4. The method according to claim 3, wherein the detecting whether the file information of the configuration file to be detected is contained in the first storage space comprises:

wherein the method further comprises:

5. The method according to any of claims 2-4, wherein the file information comprises a file storage path of the configuration file;

the step of performing blanking processing 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:

6. The method according to claim 1, wherein the nulling the to-be-nulled configuration file to obtain a nulling configuration file comprises:

7. The method according to claim 1, wherein the determining a reserved function module and a function module to be processed from the function modules included in the plug-in template according to the function information comprises:

8. A card handling apparatus, the apparatus comprising:

9. A computer device comprising a memory, a communication interface, and a processor, wherein the memory, the communication interface, and the processor are interconnected; the memory stores a computer program, and the processor calls the computer program stored in the memory for executing the plug-in processing method of any one of claims 1 to 7.

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

11. A computer program product, characterized in that it comprises a computer program or computer instructions which, when executed by a processor, implement the steps of the plug-in processing method according to any one of claims 1 to 7.