CN114003486A - Plug-in debugging method, client, server and storage medium - Google Patents
Plug-in debugging method, client, server and storage medium Download PDFInfo
- Publication number
- CN114003486A CN114003486A CN202111093265.7A CN202111093265A CN114003486A CN 114003486 A CN114003486 A CN 114003486A CN 202111093265 A CN202111093265 A CN 202111093265A CN 114003486 A CN114003486 A CN 114003486A
- Authority
- CN
- China
- Prior art keywords
- interface
- plug
- data specification
- calling
- debugging
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 36
- 238000011161 development Methods 0.000 claims abstract description 53
- 230000003993 interaction Effects 0.000 claims description 17
- 238000001514 detection method Methods 0.000 claims description 10
- 230000003044 adaptive effect Effects 0.000 claims description 7
- 230000005540 biological transmission Effects 0.000 claims description 7
- 230000005856 abnormality Effects 0.000 claims description 3
- 230000006835 compression Effects 0.000 description 10
- 238000007906 compression Methods 0.000 description 10
- 230000006837 decompression Effects 0.000 description 10
- 238000012360 testing method Methods 0.000 description 10
- 230000006870 function Effects 0.000 description 7
- 238000012795 verification Methods 0.000 description 4
- 230000004048 modification Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 230000000694 effects Effects 0.000 description 2
- 238000004088 simulation Methods 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/362—Software debugging
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
- G06F9/44526—Plug-ins; Add-ons
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a plug-in debugging method, a client, a server and a storage medium, wherein the method comprises the following steps: acquiring a data specification and a calling interface corresponding to the service of the plug-in; sending the data specification and the calling interface to a client; and receiving request information of calling the plug-in by the development interface generated by the client according to the data specification and the related information of the calling interface, and debugging the plug-in. According to the embodiment of the invention, only the data specification and the calling interface corresponding to the service of the plug-in are acquired in the server and used as the service query of the plug-in, and then the debugging of the plug-in is realized by receiving the request information of calling the plug-in by the client, so that a complete platform is not required to be built locally, the development time is saved, and the development efficiency is improved.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a plug-in debugging method, a client, a server and a storage medium.
Background
In a scheduling system, plug-ins are often newly built for project requirements. In practice, after the development of a plug-in is completed, it is found that a platform is required to run it. And platform building can be difficult along with the complexity of projects, which greatly influences development efficiency. If a complete platform is built locally for the purpose of debugging the plug-in, a lot of time is wasted.
Thus, there is still a need for improvement and development of the prior art.
Disclosure of Invention
The technical problem to be solved by the present invention is to provide a plug-in debugging method, a client, a server and a storage medium for solving the above-mentioned defects in the prior art, and to solve the problem in the prior art that a complete platform is built locally for debugging a plug-in, which wastes a lot of time.
The technical scheme adopted by the invention for solving the problems is as follows:
in a first aspect, an embodiment of the present invention provides a plug-in debugging method, where the method includes:
acquiring a data specification and a calling interface corresponding to the service of the plug-in;
sending the data specification and the calling interface to a client;
and receiving request information of calling the plug-in by the development interface generated by the client according to the data specification and the related information of the calling interface, and debugging the plug-in.
In an implementation manner, the obtaining of the data specification and the call interface corresponding to the service of the plug-in includes:
extracting a service code corresponding to the plug-in;
and updating the service code according to the service of the plug-in to obtain a data specification and a calling interface corresponding to the service of the plug-in.
In one implementation, the calling interface includes: the system comprises an initialization interface, a control interface, a parameter setting interface, a conflict detection interface and an abnormality detection interface.
In an implementation manner, the obtaining of the data specification and the call interface corresponding to the service of the plug-in includes:
and placing the plug-in into a preset position.
In one implementation, the receiving request information of a development interface calling plug-in generated by the client according to the data specification and the related information of the calling interface, and after debugging the plug-in, the method includes:
and destroying the plug-in.
In a second aspect, an embodiment of the present invention further provides a plug-in debugging client, where the plug-in debugging client includes: a data interaction interface, an interface generation module and a user interface, wherein,
the data interaction interface is used for receiving a data specification and a calling interface which are sent from a server and correspond to the service of the plug-in;
the interface generation module is used for generating a development interface according to the data specification and the related information of the calling interface;
the user interface is used for receiving data which are input by a requester in the development interface and are adaptive to the data specification and a calling interface corresponding to the service selected by the requester in the development interface and sending the data to the server.
In one implementation manner, the number of the clients is several.
In a third aspect, an embodiment of the present invention further provides a plug-in debugging server, where the plug-in debugging server includes: a data specification and call interface acquisition module, a data specification and call interface transmission module and a request information receiving module, wherein,
the data specification and calling interface acquisition module is used for acquiring the data specification and calling interface corresponding to the service of the plug-in;
the data specification and calling interface sending module is used for sending the data specification and the calling interface to a client;
and the request information receiving module is used for receiving the request information of the development interface calling plug-in generated by the client according to the data specification and the related information of the calling interface and debugging the plug-in.
In a fourth aspect, an embodiment of the present invention further provides a plug-in debugging system, where the system includes a plug-in debugging client and a plug-in debugging server, where the plug-in debugging client includes:
a data interaction interface, an interface generation module and a user interface, wherein,
the data interaction interface is used for receiving a data specification and a calling interface which are sent from a server and correspond to the service of the plug-in;
the interface generation module is used for generating a development interface according to the data specification and the related information of the calling interface;
the user interface is used for receiving data which is input by a requester in the development interface and is adaptive to the data specification and a calling interface corresponding to the service selected by the requester in the development interface and sending the data to the server;
the plug-in debugging server comprises: a data specification and call interface acquisition module, a data specification and call interface transmission module and a request information receiving module, wherein,
the data specification and calling interface acquisition module is used for acquiring the data specification and calling interface corresponding to the service of the plug-in;
the data specification and calling interface sending module is used for sending the data specification and the calling interface to a client;
and the request information receiving module is used for receiving the request information of the development interface calling plug-in generated by the client according to the data specification and the related information of the calling interface and debugging the plug-in.
In a fifth aspect, embodiments of the present invention further provide a non-transitory computer-readable storage medium, where instructions in the storage medium, when executed by a processor of an electronic device, enable the electronic device to perform a plug-in debugging method as described in any one of the above.
The invention has the beneficial effects that: the embodiment of the invention firstly obtains the data specification and the calling interface corresponding to the service of the plug-in; then sending the data specification and the calling interface to a client; finally, receiving request information of the development interface calling plug-in generated by the client according to the data specification and the related information of the calling interface, and debugging the plug-in; therefore, the embodiment of the invention only needs to acquire the data specification and the calling interface corresponding to the service of the plug-in the server to be used as the service query of the plug-in, and then realizes the debugging of the plug-in by receiving the request information of calling the plug-in by the client, and a complete platform does not need to be built locally, thereby saving the development time and improving the development efficiency.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a schematic flowchart of a plug-in debugging method according to an embodiment of the present invention.
Fig. 2 is a flowchart illustrating an embodiment of a plug-in debugging method according to an embodiment of the present invention.
Fig. 3 is a schematic block diagram of a plug-in debugging server according to an embodiment of the present invention.
Detailed Description
The invention discloses a plug-in debugging method, a client, a server and a storage medium, and in order to make the purpose, technical scheme and effect of the invention clearer and more clear, the invention is further described in detail below by referring to the attached drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
As used herein, the singular forms "a", "an", "the" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. It will be understood that when an element is referred to as being "connected" or "coupled" to another element, it can be directly connected or coupled to the other element or intervening elements may also be present. Further, "connected" or "coupled" as used herein may include wirelessly connected or wirelessly coupled. As used herein, the term "and/or" includes all or any element and all combinations of one or more of the associated listed items.
It will be understood by those skilled in the art that, unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the prior art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.
In the prior art, plug-ins are often newly built in a scheduling system for project requirements. Because the plug-in unit is manufactured by the user, the plug-in unit can be used for solving some operational inconveniences or adding new functions.
The platform + plug-in software structure divides a target software to be developed into two parts, wherein one part is a main body or a framework of the software, namely the platform, which is a program compiled in advance.
The other part is a function or supplementary module, namely a plug-in. This is the plug-in that is to be installed later.
However, in practice such situations are encountered: after the development of the plug-in is completed, it is found that a platform is required to run it. And platform building can be difficult along with the complexity of projects, which greatly influences development efficiency. If a complete platform is built locally for debugging the plug-in, a lot of time is wasted and is not worth paying.
In order to solve the problems in the prior art, the embodiment provides a plug-in debugging method, a client, a server and a storage medium, by the method, only the data specification and the call interface corresponding to the service of the plug-in are acquired in the server to serve as the service query of the plug-in, and then the plug-in is debugged by receiving the request information for calling the plug-in by the client, so that a complete platform does not need to be built locally, the development time is saved, and the development efficiency is improved. When the method is implemented specifically, firstly, a data specification and a calling interface corresponding to the service of the plug-in are obtained; then sending the data specification and the calling interface to a client; and finally, receiving request information of calling the plug-in unit for the development interface generated by the client according to the data specification and the related information of the calling interface, and debugging the plug-in unit.
Exemplary method
The embodiment provides a plug-in debugging method which can be applied to a server of a computer. As shown in fig. 1 in detail, the method includes:
s100, acquiring a data specification and a calling interface corresponding to the service of the plug-in;
specifically, in this embodiment, the plug-in refers to a software plug-in, and the service of the plug-in refers to a transaction that implements sales through the plug-in, such as compression/decompression, FLASH, and PHOTOSHOP. The data specification is a predefined semantic in the server, for example, a similar semantic such as cannload ═ 1 or 0 may be predefined, and is used to indicate that the specified plug-in can be uninstalled at any time. Of course, the present invention is not limited thereto. The data specification can include all data for developers, such as codes for guiding developers to write codes which can be recognized by the plug-in configuration system, so that the business capability of the configuration system is expanded, and software codes can adapt to more business functions without being modified. The invocation interface may include, but is not limited to: an initialization interface, a control interface, a parameter setting interface, a conflict detection interface, an anomaly detection interface and the like.
In order to obtain the data specification and the call interface corresponding to the service of the plug-in, the obtaining of the data specification and the call interface corresponding to the service of the plug-in includes the following steps:
s101: extracting a service code corresponding to the plug-in;
s102: and updating the service code according to the service of the plug-in to obtain a data specification and a calling interface corresponding to the service of the plug-in.
Specifically, in order to simplify the environment of plug-in operation, a complete platform is not required to be built locally, and only the service codes corresponding to the plug-in are extracted, for example, when the plug-in includes a compression/decompression plug-in, a FLASH plug-in, a PHOTOSHOP plug-in, and the like, only the service codes related to the compression/decompression plug-in, the FLASH plug-in, the PHOTOSHOP plug-in, and the like are extracted, and the main body of software is not required to be extracted. In one implementation, the simulation client (i.e., the client in the embodiment of the present invention) and the simulation server (i.e., the server in the embodiment of the present invention) are constructed according to the service code corresponding to the plug-in. And then updating the service code according to the service of the plug-in to obtain a data specification and a calling interface corresponding to the service of the plug-in. For example, when the services of the plug-in are compression/decompression, FLASH, and PHOTOSHOP, etc., the corresponding data specifications and the call interfaces are different, and for the convenience of subsequent debugging, it is necessary to continue to add and write codes so as to establish that the services of each plug-in correspond to the respective data specifications and call interfaces, and after the service codes are updated in this way, the data specifications and call interfaces corresponding to the services of the plug-in are obtained. The invocation interface may include, but is not limited to: an initialization interface, a control interface, a parameter setting interface, a conflict detection interface, an anomaly detection interface and the like. Taking compression/decompression as an example, the call interface corresponding to compression/decompression may include: an initialization interface and a de-initialization interface, an inquiry interface of compression/decompression capability, a job control interface for controlling the start, stop, pause and continue, a setting interface of compression/decompression parameters, a setting interface of inputting a target file to be compressed/decompressed, a setting interface of a path of an output file, a collision detection interface, an abnormality detection interface, a bundling setting interface, and the like.
In one implementation, the obtaining of the data specification and the call interface corresponding to the service of the plug-in includes:
and placing the plug-in into a preset position.
Specifically, when a plug-in is developed, the plug-in may involve menus, for example, a top Menu Test, a first-level directory Test1 under the Test, a second-level Menu under the Test1, which includes a Test Button, whether the Menu or the Button exists depending on groups, 2 groups, two Menu (one Test at the top and one Test1) and one Button to achieve corresponding business effects. Thus, unique identification GUID and ID need to be defined, and each control can be distinguished after having its own unique identification. And then storing the unique identification GUID and the ID in a registry in one-to-one correspondence with the plug-ins of the corresponding service. The preset location is also the location of the unique identifier GUID and ID corresponding to the service of the plug-in the registry. That is, after the plug-in is developed, the plug-in is placed in the registry at the unique identifier GUID and ID corresponding to the plug-in service.
After obtaining the data specification and the call interface corresponding to the service of the plug-in, the following steps as shown in fig. 1 may be performed: s200, sending the data specification and the calling interface to a client;
specifically, because debugging of the plug-in is to debug the server and the client together, the user calls the plug-in at the client, but the service code of the plug-in is in the server. After the data specification and the call interface corresponding to the service of the plug-in are obtained, the server is operated, and then the data specification and the call interface are sent to the clients through the interactive interface.
After the data specification and the call interface are sent to the client, the client generates request information after running, and therefore, the server needs to execute the following steps as shown in fig. 1: s300, receiving request information of the development interface calling plug-in generated by the client according to the data specification and the related information of the calling interface, and debugging the plug-in.
Specifically, as shown in fig. 2, after the user operates the operation interface of the client, an interface feedback is sent to the server, the server receives request information for invoking the plug-in by the client, for example, an invocation request is made for the compressed/decompressed plug-in, the server invokes the compressed/decompressed plug-in, then if the compression/decompression function is implemented, and if there is no BUG, the plug-in function is successful, and if there is a BUG, the code is modified until the plug-in function is successful.
In one implementation, the receiving request information of a development interface calling plug-in generated by the client according to the data specification and the related information of the calling interface, and after debugging the plug-in, the method includes:
and destroying the plug-in.
Specifically, after a user successfully debugs the function of one plug-in, the plug-in needs to be replaced for debugging, and at this time, the currently debugged plug-in needs to be destroyed when the user leaves the page, so that another plug-in is debugged. The specific destroying steps are as follows: go back to the top button or scroll bar and then destroy the plug-in. When the plug-in is destroyed, the stock generates the DOM, and the DOM is hidden.
Exemplary device
The embodiment of the present invention further provides a plug-in debugging client, where the plug-in debugging client includes: a data interaction interface, an interface generation module and a user interface, wherein,
the data interaction interface is used for receiving a data specification and a calling interface which are sent from a server and correspond to the service of the plug-in;
the interface generation module is used for generating a development interface according to the data specification and the related information of the calling interface;
the user interface is used for receiving data which are input by a requester in the development interface and are adaptive to the data specification and a calling interface corresponding to the service selected by the requester in the development interface and sending the data to the server.
Specifically, on the basis of testing and debugging of the virtual operating environment, testing and debugging based on the real environment are added, at this time, the data interaction interface can also send a request to the server to test and debug the plug-in based on the real operating environment, wherein the plug-in passing the testing and debugging based on the real environment is provided with a verification identifier. The verification identifier is used for marking the plug-in as a legal plug-in which passes the test and debugging. The verification identifier may be an MD5 code, thereby providing integrity protection for the message and making the transmission complete and consistent. It should be noted that the authentication identification code is not limited to MD5, and other identification codes that can serve the same purpose may implement the present invention.
The data interaction interface sends a request to the server so as to access the server, wherein the request can carry account information, and meanwhile, when the data interaction interface uploads the data and calling interface information to the server to generate a plug-in, the data interaction interface also uploads the account information to the server to be stored corresponding to the plug-in, and is also used for sending a browsing request carrying the account information to the server and receiving the plug-in corresponding to the account information and relevant information of the plug-in fed back by the server; the related information may be, but is not limited to: number of downloads, date of generation, current version information, etc.
The interface generating module is used for generating a development interface according to the data specification and the related information of the calling interface, so that a user can operate in the development interface of the client section, call the plug-in related to the service and debug.
The user interface is used for receiving data which are input by a requester in the development interface and are adaptive to the data specification and a calling interface corresponding to the service selected by the requester in the development interface and sending the data to the server. For example, the requester inputs data adapted to the compressed/decompressed data specification in the development interface, or the requester selects a call interface corresponding to the compression/decompression in the development interface, and then sends the data adapted to the compressed/decompressed data specification to the server through the data interaction interface, so that the combined debugging of the plug-in can be realized together with the server.
In the actual debugging process, whether the plug-in runs with errors is checked, if the plug-in runs with errors, a debugging verification tool positions the position of the error, analyzes the reason of the error, prompts modification so as to correct the error, and returns to the test after the error is corrected until the debugging is successful.
In one implementation, the number of the clients is several. Therefore, the server can be simultaneously connected with a plurality of clients so as to debug the plug-ins of different services on different clients.
As shown in fig. 3, an embodiment of the present invention further provides a plug-in debugging server, where the plug-in debugging server includes: a data specification and call interface acquisition module, a data specification and call interface transmission module and a request information receiving module, wherein,
the data specification and calling interface acquisition module is used for acquiring the data specification and calling interface corresponding to the service of the plug-in;
the data specification and calling interface sending module is used for sending the data specification and the calling interface to a client;
and the request information receiving module is used for receiving the request information of the development interface calling plug-in generated by the client according to the data specification and the related information of the calling interface and debugging the plug-in.
The embodiment of the present invention further provides a plug-in debugging system, where the system includes a plug-in debugging client and a plug-in debugging server, where the plug-in debugging client includes:
a data interaction interface, an interface generation module and a user interface, wherein,
the data interaction interface is used for receiving a data specification and a calling interface which are sent from a server and correspond to the service of the plug-in;
the interface generation module is used for generating a development interface according to the data specification and the related information of the calling interface;
the user interface is used for receiving data which is input by a requester in the development interface and is adaptive to the data specification and a calling interface corresponding to the service selected by the requester in the development interface and sending the data to the server;
the plug-in debugging server comprises: a data specification and call interface acquisition module, a data specification and call interface transmission module and a request information receiving module, wherein,
the data specification and calling interface acquisition module is used for acquiring the data specification and calling interface corresponding to the service of the plug-in;
the data specification and calling interface sending module is used for sending the data specification and the calling interface to a client;
and the request information receiving module is used for receiving the request information of the development interface calling plug-in generated by the client according to the data specification and the related information of the calling interface and debugging the plug-in.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, databases, or other media used in embodiments provided herein may include non-volatile and/or volatile memory. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
In summary, the present invention discloses a plug-in debugging method, a client, a server and a storage medium, wherein the method comprises: acquiring a data specification and a calling interface corresponding to the service of the plug-in; sending the data specification and the calling interface to a client; and receiving request information of calling the plug-in by the development interface generated by the client according to the data specification and the related information of the calling interface, and debugging the plug-in. According to the embodiment of the invention, only the data specification and the calling interface corresponding to the service of the plug-in are acquired in the server and used as the service query of the plug-in, and then the debugging of the plug-in is realized by receiving the request information of calling the plug-in by the client, so that a complete platform is not required to be built locally, the development time is saved, and the development efficiency is improved.
Based on the above embodiments, the present invention discloses a plug-in debugging method, it should be understood that the application of the present invention is not limited to the above examples, and those skilled in the art can make modifications or changes according to the above description, and all such modifications and changes should fall within the protection scope of the appended claims.
Claims (10)
1. A method for debugging a plug-in, the method comprising:
acquiring a data specification and a calling interface corresponding to the service of the plug-in;
sending the data specification and the calling interface to a client;
and receiving request information of calling the plug-in by the development interface generated by the client according to the data specification and the related information of the calling interface, and debugging the plug-in.
2. The plugin debugging method according to claim 1, wherein the obtaining of the data specification and the call interface corresponding to the service of the plugin includes:
extracting a service code corresponding to the plug-in;
and updating the service code according to the service of the plug-in to obtain a data specification and a calling interface corresponding to the service of the plug-in.
3. The plug-in debugging method according to claim 2, wherein said calling interface comprises: the system comprises an initialization interface, a control interface, a parameter setting interface, a conflict detection interface and an abnormality detection interface.
4. The plugin debugging method according to claim 2, wherein the obtaining of the data specification and the call interface corresponding to the service of the plugin includes:
and placing the plug-in into a preset position.
5. The plugin debugging method according to claim 1, wherein the receiving request information of the development interface calling plugin generated by the client according to the data specification and the relevant information of the calling interface, and after debugging the plugin, the method includes:
and destroying the plug-in.
6. A plug-in debug client, comprising: a data interaction interface, an interface generation module and a user interface, wherein,
the data interaction interface is used for receiving a data specification and a calling interface which are sent from a server and correspond to the service of the plug-in;
the interface generation module is used for generating a development interface according to the data specification and the related information of the calling interface;
the user interface is used for receiving data which are input by a requester in the development interface and are adaptive to the data specification and a calling interface corresponding to the service selected by the requester in the development interface and sending the data to the server.
7. The plug-in debugging client according to claim 6, wherein the number of said clients is several.
8. A plug-in debug server, comprising: a data specification and call interface acquisition module, a data specification and call interface transmission module and a request information receiving module, wherein,
the data specification and calling interface acquisition module is used for acquiring the data specification and calling interface corresponding to the service of the plug-in;
the data specification and calling interface sending module is used for sending the data specification and the calling interface to a client;
and the request information receiving module is used for receiving the request information of the development interface calling plug-in generated by the client according to the data specification and the related information of the calling interface and debugging the plug-in.
9. The plug-in debugging system is characterized by comprising a plug-in debugging client and a plug-in debugging server, wherein the plug-in debugging client comprises:
a data interaction interface, an interface generation module and a user interface, wherein,
the data interaction interface is used for receiving a data specification and a calling interface which are sent from a server and correspond to the service of the plug-in;
the interface generation module is used for generating a development interface according to the data specification and the related information of the calling interface;
the user interface is used for receiving data which is input by a requester in the development interface and is adaptive to the data specification and a calling interface corresponding to the service selected by the requester in the development interface and sending the data to the server;
the plug-in debugging server comprises: a data specification and call interface acquisition module, a data specification and call interface transmission module and a request information receiving module, wherein,
the data specification and calling interface acquisition module is used for acquiring the data specification and calling interface corresponding to the service of the plug-in;
the data specification and calling interface sending module is used for sending the data specification and the calling interface to a client;
and the request information receiving module is used for receiving the request information of the development interface calling plug-in generated by the client according to the data specification and the related information of the calling interface and debugging the plug-in.
10. A non-transitory computer readable storage medium, wherein instructions in the storage medium, when executed by a processor of an electronic device, enable the electronic device to perform the steps of the method of any of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111093265.7A CN114003486A (en) | 2021-09-17 | 2021-09-17 | Plug-in debugging method, client, server and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111093265.7A CN114003486A (en) | 2021-09-17 | 2021-09-17 | Plug-in debugging method, client, server and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114003486A true CN114003486A (en) | 2022-02-01 |
Family
ID=79921458
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111093265.7A Pending CN114003486A (en) | 2021-09-17 | 2021-09-17 | Plug-in debugging method, client, server and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114003486A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116303096A (en) * | 2023-05-15 | 2023-06-23 | 安元科技股份有限公司 | Method for debugging local component code of low-code designer |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100106849A1 (en) * | 2008-10-28 | 2010-04-29 | Pixel8 Networks, Inc. | Network-attached media plug-in |
| CN102413022A (en) * | 2011-12-31 | 2012-04-11 | 北京新媒传信科技有限公司 | Application debugging method and system |
| CN103152327A (en) * | 2013-02-01 | 2013-06-12 | 北京奇虎科技有限公司 | Configuration method, client and system for plug-in unit compressing and uncompressing |
-
2021
- 2021-09-17 CN CN202111093265.7A patent/CN114003486A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100106849A1 (en) * | 2008-10-28 | 2010-04-29 | Pixel8 Networks, Inc. | Network-attached media plug-in |
| CN102413022A (en) * | 2011-12-31 | 2012-04-11 | 北京新媒传信科技有限公司 | Application debugging method and system |
| CN103152327A (en) * | 2013-02-01 | 2013-06-12 | 北京奇虎科技有限公司 | Configuration method, client and system for plug-in unit compressing and uncompressing |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116303096A (en) * | 2023-05-15 | 2023-06-23 | 安元科技股份有限公司 | Method for debugging local component code of low-code designer |
| CN116303096B (en) * | 2023-05-15 | 2023-08-11 | 安元科技股份有限公司 | Method for debugging local component code of low-code designer |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108446116B (en) | Application program page generation method and device, computer equipment and storage medium | |
| CN109460527B (en) | Product data configuration method, device, computer equipment and storage medium | |
| CN110633160A (en) | Interface calling method and device, computer equipment and storage medium | |
| CN111078339B (en) | Interface element positioning method and device, computer equipment and storage medium | |
| CN109474662B (en) | Product data publishing method and device, computer equipment and storage medium | |
| EP2990942B1 (en) | Service extraction and application composition | |
| CN109814854B (en) | Project framework generation method, device, computer equipment and storage medium | |
| US20200183683A1 (en) | Application architecture generation | |
| US20140208169A1 (en) | Domain scripting language framework for service and system integration | |
| CN113238850A (en) | RPA implementation method, device, equipment and medium based on browser | |
| US20140208294A1 (en) | Domain scripting language framework for service and system integration | |
| CN109284106A (en) | Method for release management, electronic device and the readable storage medium storing program for executing of business rule | |
| CN111008132B (en) | Application debugging method and device for Android system, computer equipment and storage medium | |
| CN111984228A (en) | Interface document processing method and device, computer equipment and storage medium | |
| CN108228190B (en) | Persistent integration and delivery methods, systems, devices, and computer-readable storage media | |
| EP3447635A1 (en) | Application architecture generation | |
| CN112363745A (en) | Rule file management method and device, computer equipment and storage medium | |
| CN115543419A (en) | Method, device, equipment and storage medium for generating software development kit | |
| CN112148699A (en) | Log management method, device, equipment and medium | |
| CN114003486A (en) | Plug-in debugging method, client, server and storage medium | |
| CN115185821A (en) | Version labeling method, system, equipment and storage medium in program test | |
| CN114564385A (en) | Software testing method and device, computer equipment and storage medium | |
| CN114115967A (en) | Service data processing method and device, computer equipment and storage medium | |
| CN112699023B (en) | Project interface testing method and device, computer equipment and storage medium | |
| CN115374083A (en) | Data source switching method and device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |