Plug-in configuration method and apparatus, and device and storage medium

Abstract

A plug-in configuration method and apparatus, and a device and a storage medium. The method comprises: presenting a management panel in a development interface of a plug-in, wherein the management panel is used for displaying or editing metadata of at least one function associated with the plug-in (210); in response to a request to deploy the plug-in, on the basis of the metadata, generating description information corresponding to a target application platform (220); and providing the description information to the target application platform, so as to set at least one configuration parameter of the plug-in in the target application platform (230). Therefore, the efficiency of plug-in configuration is improved.

Description

Method, device, equipment and storage medium for configuring plug-in Technical Field

[0001] Example embodiments of the present disclosure generally relate to the field of computers, and more particularly, to a method, apparatus, device, and computer-readable storage medium for configuring a plug-in. Background Art

[0002] With the advancement of computer technology, people can develop various applications based on machine learning models, such as bots and intelligent agents. Plugins are a crucial capability for these applications. Plugin developers can develop and release plugins for users to use to build applications.

[0003] Summary of the Invention

[0004] In a first aspect of the present disclosure, a method for configuring a plug-in is provided. The method comprises: presenting a management panel in a plug-in development interface, the management panel being used to display or edit metadata of at least one function associated with the plug-in; generating, in response to a request to deploy the plug-in, description information corresponding to a target application platform based on the metadata; and providing the description information to the target application platform to set at least one configuration parameter of the plug-in in the target application platform.

[0005] In a second aspect of the present disclosure, a device for configuring a plug-in is provided. The device includes: a presentation module configured to present a management panel in a plug-in development interface, the management panel being used to display or edit metadata of at least one function associated with the plug-in; a generation module configured to generate, in response to a request to deploy the plug-in, description information corresponding to a target application platform based on the metadata; and a provision module configured to provide the description information to the target application platform to set at least one configuration parameter of the plug-in in the target application platform.

[0006] In a third aspect of the present disclosure, an electronic device is provided. The device includes at least one processing unit; and at least one memory coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit. When executed by the at least one processing unit, the instructions cause the device to perform the method of the first aspect.

[0007] In a fourth aspect of the present disclosure, a computer-readable storage medium is provided, wherein a computer program is stored on the computer-readable storage medium, and the computer program can be executed by a processor to implement the method of the first aspect.

[0008] It should be understood that the content described in this summary section is not intended to limit the key features or important features of the embodiments of the present disclosure, nor is it intended to limit the scope of the present disclosure. Other features of the present disclosure will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] The above and other features, advantages and aspects of the embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. In the accompanying drawings, the same or similar reference numerals represent the same or similar elements, wherein:

[0010] FIG1 shows a schematic diagram of an example environment capable of implementing some embodiments of the present disclosure;

[0011] FIG2 shows a flowchart of a process for configuring a plug-in according to some embodiments of the present disclosure;

[0012] 3A and 3B illustrate example development interfaces according to some embodiments of the present disclosure;

[0013] FIG4 shows a schematic diagram of developing a plug-in according to some embodiments of the present disclosure;

[0014] FIG5 shows a schematic structural block diagram of an example apparatus for configuring a plug-in according to some embodiments of the present disclosure; and

[0015] FIG6 illustrates a block diagram of an electronic device capable of implementing various embodiments of the present disclosure. DETAILED DESCRIPTION

[0016] The following describes embodiments of the present disclosure in more detail with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as limited to the embodiments described herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are for illustrative purposes only and are not intended to limit the scope of protection of the present disclosure.

[0017] It should be noted that the titles of any section / subsection provided herein are not limiting. Various embodiments are described throughout this document, and any type of embodiment may be included under any section / subsection. Furthermore, the embodiments described in any section / subsection may be combined in any manner with any other embodiments described in the same section / subsection and / or in different sections / subsections.

[0018] In the description of the embodiments of the present disclosure, the term "including" and similar terms should be understood as open inclusion, that is, "including but not limited to". The term "based on" should be understood as "based at least in part on". The term "one embodiment" or "the embodiment" should be understood as "at least one embodiment". The term "some embodiments" should be understood as "at least some embodiments". Other explicit and implicit definitions may be included below. The terms "first", "second", etc. may refer to different or the same objects. Other explicit and implicit definitions may be included below.

[0019] The embodiments of the present disclosure may involve user data, data acquisition and / or use, etc. These aspects shall comply with the corresponding laws, regulations and relevant provisions. In the embodiments of the present disclosure, all data collection, acquisition, processing, processing, forwarding, use, etc. are carried out on the premise that the user is aware of and confirms them. Accordingly, when implementing the various embodiments of the present disclosure, the types, scope of use, and usage scenarios of the data or information that may be involved should be informed to the user and the user's authorization should be obtained in an appropriate manner in accordance with the relevant laws and regulations. The specific notification and / or authorization method may vary according to the actual situation and application scenario, and the scope of the present disclosure is not limited in this respect.

[0020] If this specification and the solutions in the examples involve the processing of personal information, such processing will be done only with a legitimate basis (such as with the consent of the subject of personal information or as necessary for the performance of a contract) and only within the prescribed or agreed scope. A user's refusal to process personal information other than that required for basic functions will not affect the user's use of basic functions.

[0021] As briefly mentioned above, plugins are a crucial capability for applications. Plugin developers can develop and publish plugins for users to use to build applications. Traditionally, when developers want to publish a plugin on an application platform, they need to manually configure the relevant information for the plugin's functions, which greatly reduces plugin development efficiency.

[0022] Embodiments of the present disclosure provide a solution for configuring a plug-in. According to this solution, a management panel can be presented within the plug-in's development interface, used to display or edit metadata for at least one function associated with the plug-in. Furthermore, in response to a request to deploy the plug-in, descriptive information corresponding to a target application platform can be generated based on the metadata. Additionally, the descriptive information can be provided to the target application platform to set at least one configuration parameter for the plug-in within the target application platform.

[0023] In this way, the embodiments of the present disclosure can connect the plug-in development environment and the application platform, so that metadata can be synchronized to the application platform to complete the automatic configuration and release of the plug-in, thereby improving the efficiency of plug-in development and configuration.

[0024] Various example implementations of this solution are described in detail below in conjunction with the accompanying drawings.

[0025] Sample Environment

[0026] FIG1 shows a schematic diagram of an example environment 100 in which embodiments of the present disclosure can be implemented. As shown in FIG1 , the example environment 100 may include an electronic device 110 .

[0027] In some embodiments, the electronic device 110 may be deployed with an integrated development environment (IDE), or may support users to access an online development environment through a browser. Accordingly, the user may utilize the electronic device 110 to complete the development of the code for the plug-in 120 and may deploy the plug-in 120 to a deployment platform 130 (e.g., a cloud platform).

[0028] Furthermore, as will be described in detail below, the electronic device 110 may also automatically generate description information 140 during the deployment of the plug-in 120 , and such description information 140 may indicate metadata of one or more functions in the plug-in 120 .

[0029] Such description information 140 can be provided to the application platform 150 for setting configuration parameters of the plug-in 120 in the application platform 150 and publishing the plug-in 120 as a plug-in type or an action type. Furthermore, the application 160 created via the application platform 150 can be configured to have the ability to call the plug-in 120 and can call the plug-in 120 by accessing the deployment platform 130 to execute the corresponding processing.

[0030] In some embodiments, the application platform 150 may include, for example, a platform for developing an agent. Accordingly, the application 160 may include, for example, an agent or bot developed based on the application platform 150.

[0031] In some examples, the electronic device 110 can be any type of mobile terminal, fixed terminal or portable terminal, including a mobile phone, a desktop computer, a laptop computer, a notebook computer, a netbook computer, a tablet computer, a media computer, a multimedia tablet, a handheld computer, a portable game terminal, a VR / AR device, a personal communication system (PCS) device, a personal navigation device, a personal digital assistant (PDA), an audio / video player, a digital camera / camcorder, a positioning device, a television receiver, a radio broadcast receiver, an e-book device, a gaming device or any combination thereof, including accessories and peripherals of these devices or any combination thereof. In some embodiments, the electronic device 110 can also support any type of interface for the user (such as a "wearable" circuit, etc.).

[0032] It should be understood that the structure and function of the various elements in the environment 100 are described for illustrative purposes only and do not imply any limitation on the scope of the present disclosure.

[0033] Some example embodiments of the present disclosure will be described below with continued reference to the accompanying drawings.

[0034] Example Process

[0035] FIG2 shows a flow chart of an example process 200 for configuring a plug-in according to some embodiments of the present disclosure. The process 200 may be implemented, for example, at the electronic device 110 as shown in FIG1 .

[0036] As shown in FIG. 2 , in block 210 , the electronic device 110 presents a management panel in the development interface of the plug-in, where the management panel is used to display or edit metadata of at least one function associated with the plug-in.

[0037] Process 200 will be described below with reference to Figures 3A and 3B. Figures 3A and 3B illustrate example development interfaces 300A and 300B according to some embodiments of the present disclosure.

[0038] As shown in FIG. 3A , the electronic device 110 may use an integrated development environment to provide a development interface 300A as shown in FIG. 3A , and may display a management panel for managing metadata in the development interface 300A.

[0039] In some embodiments, the management panel shown in Figure 3A can display metadata of at least one function in the plug-in. As an example, such metadata can include basic information 305 of the function, such as the function's identifier (e.g., name) and a functional description of the function.

[0040] Additionally, the metadata may include function input information 310. As an example, the management panel may display one or more input parameters of the function, and display the name, description, type, and whether the input parameter is required, etc.

[0041] Additionally, the metadata may include function output information 315. As an example, the management panel may display one or more output parameters of the function, and display the name, description, type, whether it is a required item, etc. of the output parameter.

[0042] In some embodiments, the integrated development environment can automatically determine the above metadata based on analysis of the code representation of the function. For example, the integrated development environment can extract the corresponding metadata according to preset grammatical rules, or can determine the corresponding metadata using a language model.

[0043] In some embodiments, the electronic device 110 may also support the user to manually input metadata or edit metadata through the management panel. For example, the user may add new parameters or modify parameter information through the input controls provided in the management panel.

[0044] In this way, the embodiments of the present disclosure can support visual management of metadata, thereby improving the efficiency of metadata management.

[0045] 2 , in block 220 , in response to the request to deploy the plug-in, the electronic device 110 generates description information corresponding to the target application platform based on the metadata.

[0046] Furthermore, as shown in FIG3B , after receiving the request to deploy the plug-in, the electronic device 110 may present an interface 300B as shown in FIG3B to display deployment information.

[0047] As shown in FIG. 3B , the interface 300B may display function information 320 in the plug-in, for example, one or more functions included in the plug-in and their access paths.

[0048] Additionally, electronic device 110 may also display descriptive information 325 generated based on the metadata in the management panel in interface 300B. In some embodiments, such descriptive information 325 is, for example, structured data generated based on the metadata. For example, the specific data format of such structured data may depend on the type of target application platform to be published.

[0049] For example, different application platforms may correspond to different plug-in configuration interfaces or plug-in configuration rules. The format of the structured data generated by the electronic device 110 may match such configuration interfaces or configuration rules.

[0050] Continuing with reference to FIG. 2 , in block 230 , the electronic device 110 provides the description information to the target application platform to set at least one configuration parameter of the plug-in in the target application platform.

[0051] In some embodiments, if the target application platform supports configuring the plug-in through an interface, the electronic device 110 can use the interface corresponding to the target application platform to provide the description information to the target application platform. Accordingly, the target application platform can automatically set one or more configuration parameters of the plug-in to be published based on the metadata indicated in the description information.

[0052] In some further embodiments, the electronic device 110 may access the corresponding integrated development environment through a browser, for example, and the electronic device 110 may utilize a target tool of the browser to store such description information.

[0053] Furthermore, when the browser displays a configuration interface for configuring the plug-in in the target application platform, the electronic device 110 can use the browser's target tool to automatically fill in the corresponding information items in the configuration interface, thereby completing the setting of one or more configuration parameters of the plug-in.

[0054] In some other embodiments, the electronic device 110 may further generate and provide an access address 330 corresponding to the description information 325. Furthermore, the user may enter or paste the access address 330 in the target application platform (for example, by clicking a copy button 335), so that the target application platform can obtain the description information based on the access address and set one or more configuration parameters of the plug-in to be published.

[0055] Based on this approach, the embodiments of the present disclosure can connect the plug-in development platform and the application platform, thereby realizing the linkage between plug-in development and plug-in release, thereby reducing the development costs of developers.

[0056] Figure 4 further illustrates a schematic diagram 400 of developing a plug-in according to some embodiments of the present disclosure. As shown in Figure 4, the development lifecycle of a plug-in may include, for example, four stages, namely, a plug-in development stage, a plug-in deployment stage, a linkage agent platform stage, and an online operation stage.

[0057] As shown in FIG4 , during the development phase, a developer 410 may, for example, create an agent project and write plugin code accordingly. For example, the developer may utilize an integrated development platform to write the plugin code. In some examples, the code may also be managed using a BaaS service for data storage or file storage.

[0058] Furthermore, as described above, such code can be synchronized and managed using an integrated development environment (IDE). For example, the IDE can automatically generate metadata for all functions in the interface file and synchronize them.

[0059] After completing the plugin code editing, the developer 410 can further test the code. As an example, such a test run can include running specific test cases to evaluate whether the results are accurate. In response, after the test passes, the plugin development can enter the deployment phase.

[0060] During the deployment phase, upon receiving a deployment request, the integrated development environment can build code based on the code in the plug-in and, for example, package the code before uploading it to a deployment platform. Such a deployment platform can, for example, be implemented based on a cloud service. Accordingly, such a code package can be deployed as a cloud function, allowing other devices to call the cloud function via a network address.

[0061] Furthermore, as discussed above, depending on the type of agent platform, the IDE can provide the function metadata to the agent platform via an API, or can import the metadata into the agent platform via a browser tool (e.g., a plug-in). Thus, the IDE can complete the plug-in deployment process.

[0062] 4, in the linkage agent platform stage, agent user 420 can create a corresponding agent in the agent platform. Further, agent user 420 can configure the agent of the homepage so that other can call the plug-in or action published in the agent platform.

[0063] As described above, plugins or actions published in the agent platform can be automatically configured based on the metadata of the plugin code's function. Thus, such an agent can call the published plugin or action. During the specific calling process, the agent can call the corresponding cloud function based on the access address of the deployment platform where the plugin is deployed, thereby triggering the deployment platform to execute the corresponding function code. Furthermore, the agent can obtain the execution result of the cloud function from the deployment platform as a response result.

[0064] Furthermore, the agent can consume the results of the plug-in code and provide the user with corresponding response content, thereby completing the operation of the agent. For example, the agent can generate a corresponding reply message based on the results of the plug-in code as a response content to a specific user request.

[0065] Based on the process described above, the embodiments of the present disclosure can connect the plug-in development environment and the application platform, so that metadata can be synchronized to the application platform to complete the automatic configuration and release of the plug-in, thereby improving the efficiency of plug-in development and configuration.

[0066] Example devices and equipment

[0067] Embodiments of the present disclosure also provide corresponding apparatuses for implementing the above-described methods or processes. Figure 5 shows a schematic block diagram of an example apparatus 500 for configuring a plug-in according to certain embodiments of the present disclosure. Apparatus 500 may be implemented as or included in an electronic device. Each module / component in apparatus 500 may be implemented using hardware, software, firmware, or any combination thereof.

[0068] As shown in Figure 5, the device 500 includes a presentation module 510, which is configured to present a management panel in the development interface of the plug-in, and the management panel is used to display or edit metadata of at least one function associated with the plug-in; a generation module 520, which is configured to generate description information corresponding to the target application platform based on the metadata in response to a request to deploy the plug-in; and a provision module 530, which is configured to provide description information to the target application platform to set at least one configuration parameter of the plug-in in the target application platform.

[0069] In some embodiments, the metadata includes at least one of the following: an identification of at least one function; a functional description of at least one function; input information of at least one function; and output information of at least one function.

[0070] In some embodiments, the metadata of the at least one function is determined based on an analysis of a code representation of the at least one function.

[0071] In some embodiments, the description information includes structured data generated based on metadata.

[0072] In some embodiments, the EMUI module 530 is further configured to: provide description information to the target application platform using an interface corresponding to the target application platform, wherein the description information has a data format that matches the interface.

[0073] In some embodiments, the development interface is provided by a browser, and the providing module 530 is also configured to: use the browser's target tool to store description information; and in response to the browser displaying a configuration interface for configuring the plug-in in the target application platform, use the target tool to fill in the corresponding information items in the configuration interface.

[0074] In some embodiments, the providing module 530 is further configured to: generate an access address corresponding to the description information, so that the target application platform obtains the description information based on the access address.

[0075] In some embodiments, the apparatus 500 further includes a deployment module configured to: deploy the plug-in on a deployment platform to support calling at least one function in the plug-in by way of a cloud function.

[0076] In some embodiments, the target application platform includes a platform for developing an agent, and the agent is configured to be able to call a plug-in.

[0077] FIG6 shows a block diagram of an electronic device 600 in which one or more embodiments of the present disclosure may be implemented. It should be understood that the electronic device 600 shown in FIG6 is merely exemplary and should not be construed as limiting the functionality and scope of the embodiments described herein. The electronic device 600 shown in FIG6 can be used in an electronic device.

[0078] As shown in FIG6 , electronic device 600 is a general-purpose electronic device. Components of electronic device 600 may include, but are not limited to, one or more processors or processing units 610, memory 620, storage device 630, one or more communication units 640, one or more input devices 650, and one or more output devices 660. Processing unit 610 may be a real or virtual processor and is capable of performing various processes according to programs stored in memory 620. In a multi-processor system, multiple processing units execute computer-executable instructions in parallel to enhance the parallel processing capabilities of electronic device 600.

[0079] The electronic device 600 typically includes a plurality of computer storage media. Such media can be any accessible media that can be obtained by the electronic device 600, including but not limited to volatile and non-volatile media, removable and non-removable media. The memory 620 can be a volatile memory (e.g., registers, cache, random access memory (RAM)), a non-volatile memory (e.g., read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory), or some combination thereof. The storage device 630 can be a removable or non-removable medium and can include a machine-readable medium, such as a flash drive, a disk, or any other medium that can be used to store information and / or data and can be accessed within the electronic device 600.

[0080] The electronic device 600 may further include additional removable / non-removable, volatile / non-volatile storage media. Although not shown in FIG6 , a disk drive for reading or writing from a removable, non-volatile disk (e.g., a “floppy disk”) and an optical drive for reading or writing from a removable, non-volatile optical disk may be provided. In these cases, each drive may be connected to a bus (not shown) by one or more data media interfaces. The memory 620 may include a computer program product 625 having one or more program modules configured to perform various methods or actions of various embodiments of the present disclosure.

[0081] The communication unit 640 enables communication with other electronic devices via a communication medium. Additionally, the functions of the components of the electronic device 600 can be implemented in a single computing cluster or multiple computing machines that can communicate via a communication connection. Thus, the electronic device 600 can operate in a networked environment using a logical connection with one or more other servers, a network personal computer (PC), or another network node.

[0082] The input device 650 may be one or more input devices, such as a mouse, keyboard, or trackball. The output device 660 may be one or more output devices, such as a display, a speaker, or a printer. The electronic device 600 may also communicate with one or more external devices (not shown) through the communication unit 640 as needed, such as a storage device, a display device, or the like, with one or more devices that allow a user to interact with the electronic device 600, or with any device that allows the electronic device 600 to communicate with one or more other electronic devices (e.g., a network card, a modem, etc.). Such communication may be performed via an input / output (I / O) interface (not shown).

[0083] According to an exemplary implementation of the present disclosure, a computer-readable storage medium is provided, on which computer-executable instructions are stored, wherein the computer-executable instructions are executed by a processor to implement the method described above. According to an exemplary implementation of the present disclosure, a computer program product is also provided, which is tangibly stored on a non-transitory computer-readable medium and includes computer-executable instructions, and the computer-executable instructions are executed by a processor to implement the method described above.

[0084] Various aspects of the present disclosure are described herein with reference to flowcharts and / or block diagrams of methods, apparatuses, devices, and computer program products implemented according to the present disclosure. It should be understood that each block of the flowcharts and / or block diagrams, and combinations of blocks in the flowcharts and / or block diagrams, can be implemented by computer-readable program instructions.

[0085] These computer-readable program instructions can be provided to a processing unit of a general-purpose computer, a special-purpose computer, or other programmable data processing device, thereby producing a machine, such that when these instructions are executed by the processing unit of the computer or other programmable data processing device, a device is generated that implements the functions / actions specified in one or more blocks in the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium, where these instructions cause the computer, programmable data processing device, and / or other device to operate in a specific manner. Thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing various aspects of the functions / actions specified in one or more blocks in the flowchart and / or block diagram.

[0086] Computer-readable program instructions can be loaded onto a computer, other programmable data processing apparatus, or other device so that a series of operational steps are performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions executed on the computer, other programmable data processing apparatus, or other device to implement the functions / actions specified in one or more boxes in the flowchart and / or block diagram.

[0087] The flow charts and block diagrams in the accompanying drawings show the possible architecture, functions and operations of the systems, methods and computer program products according to multiple implementations of the present disclosure. In this regard, each box in the flow chart or block diagram can represent a part for a module, program segment or instruction, and a part for a module, program segment or instruction comprises one or more executable instructions for realizing the logical function of the specification. In some alternative implementations, the functions marked in the box can also occur in a sequence different from that marked in the accompanying drawings. For example, two continuous boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flow chart, and the combination of the boxes in the block diagram and / or flow chart can be realized by a special hardware-based system that performs the function or action of the specification, or can be realized by a combination of special hardware and computer instructions.

[0088] While various implementations of the present disclosure have been described above, the foregoing description is intended to be illustrative, not exhaustive, and not limited to the disclosed implementations. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described implementations. The terminology used herein is selected to best explain the principles of the implementations, their practical applications, or improvements to existing technologies, or to enable others skilled in the art to understand the various implementations disclosed herein.

Claims

1. A method for configuring a plug-in, comprising: Presenting a management panel in a development interface of the plug-in, the management panel being used to display or edit metadata of at least one function associated with the plug-in; In response to a request to deploy the plug-in, generating description information corresponding to a target application platform based on the metadata; as well as The description information is provided to the target application platform to set at least one configuration parameter of the plug-in in the target application platform.

2. The method according to claim 1, wherein the metadata comprises at least one of the following: an identification of the at least one function; a functional description of the at least one function; input information of the at least one function; Output information of the at least one function. 3 . The method of claim 1 , wherein the metadata of the at least one function is determined based on an analysis of a code representation of the at least one function. The method according to claim 1 , wherein the description information comprises structured data generated based on the metadata.

5. The method according to claim 1, wherein providing the description information to the target application platform comprises: The description information is provided to the target application platform by using an interface corresponding to the target application platform, wherein the description information has a data format matching the interface.

6. The method according to claim 1, wherein the development interface is provided by a browser, and providing the description information to the target application platform comprises: Using a target tool of the browser to store the description information; as well as In response to the browser displaying a configuration interface for configuring the plug-in in the target application platform, the target tool is used to fill in corresponding information items in the configuration interface.

7. The method according to claim 1, wherein providing the description information to the target application platform comprises: An access address corresponding to the description information is generated, so that the target application platform obtains the description information based on the access address.

8. The method according to claim 1, further comprising: The plug-in is deployed on a deployment platform to support calling the at least one function in the plug-in by means of a cloud function.

9. The method according to claim 1, wherein the target application platform comprises a platform for developing an agent, and the agent is configured to be able to call the plug-in.

10. A device for configuring a plug-in, comprising: A presentation module, configured to present a management panel in a development interface of the plug-in, wherein the management panel is used to display or edit metadata of at least one function associated with the plug-in; a generating module configured to generate description information corresponding to a target application platform based on the metadata in response to a request to deploy the plug-in; as well as The providing module is configured to provide the description information to the target application platform to set at least one configuration parameter of the plug-in in the target application platform.

11. An electronic device, comprising: at least one processing unit; as well as At least one memory, the at least one memory being coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit, the instructions causing the electronic device to perform the method according to any one of claims 1 to 9 when executed by the at least one processing unit.

12. A computer-readable storage medium having a computer program stored thereon, wherein the computer program can be executed by a processor to implement the method according to any one of claims 1 to 9.

Images