CN111258563A - Interface document generation method and device, storage medium and electronic equipment - Google Patents
Interface document generation method and device, storage medium and electronic equipment Download PDFInfo
- Publication number
- CN111258563A CN111258563A CN202010046518.4A CN202010046518A CN111258563A CN 111258563 A CN111258563 A CN 111258563A CN 202010046518 A CN202010046518 A CN 202010046518A CN 111258563 A CN111258563 A CN 111258563A
- Authority
- CN
- China
- Prior art keywords
- interface
- document
- target interface
- source code
- code data
- 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.)
- Withdrawn
Links
- 238000000034 method Methods 0.000 title claims abstract description 52
- 238000004590 computer program Methods 0.000 claims description 8
- 238000012423 maintenance Methods 0.000 abstract description 3
- 239000002609 medium Substances 0.000 description 13
- 238000010586 diagram Methods 0.000 description 8
- 238000011161 development Methods 0.000 description 4
- 230000006870 function Effects 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 3
- 230000009545 invasion Effects 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 2
- 239000000284 extract Substances 0.000 description 2
- 238000013461 design Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 239000012120 mounting media Substances 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 230000008707 rearrangement Effects 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/31—Programming languages or programming paradigms
- G06F8/315—Object-oriented languages
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computing Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The embodiment of the application discloses a method and a device for generating an interface document, a storage medium and electronic equipment. The method comprises the following steps: reading source code data of a target interface through a JavaDoc plug-in, and determining document parameters of the target interface according to the source code data; and generating a Maven plugin based on the document parameters so as to generate a target interface document by using the Maven plugin when a command is executed in a project. By operating the technical scheme provided by the application, the purpose of automatically generating the interface document to reduce the management and maintenance cost of the interface document can be realized.
Description
Technical Field
The embodiment of the application relates to the technical field of computers, in particular to a method and a device for generating an interface document, a storage medium and electronic equipment.
Background
With the rapid development of the technology level, various platforms are continuously launching new software and updating the existing software to meet the needs of users.
In the software development process, interface documents need to be maintained between an interface provider and an interface user, but the interface documents are maintained, so that the problems that manpower is input, real-time updating cannot be achieved and the like are caused. The interface provider needs to manually update the interface document when the interface changes, and if the interface document is not updated in time, the interface provider can recall errors; the interface provider writes the document at the source code level and rewrites the document on an interface common platform, which is inefficient.
Disclosure of Invention
The embodiment of the application provides a method and a device for generating an interface document, a storage medium and electronic equipment, so as to achieve the purpose of automatically generating the interface document and reduce the management and maintenance cost of the interface document.
In a first aspect, an embodiment of the present application provides a method for generating an interface document, where the method includes:
reading source code data of a target interface through a JavaDoc plug-in, and determining document parameters of the target interface according to the source code data;
and generating a Maven plugin based on the document parameters so as to generate a target interface document by using the Maven plugin when a command is executed in a project.
Optionally, the document parameters of the target interface include: request mode, request path, entry and return values.
Optionally, determining a document parameter of the target interface according to the source code data includes:
determining the type of a target interface according to the source code data;
determining a Java class corresponding to the target interface class according to the target interface class;
and acquiring the document parameters of the target interface according to a preset strategy matched with the Java class.
Optionally, if the target interface is an REST interface, the Java class of the target interface is a Controller;
and if the target Interface is an RPC Interface, the Java class of the target Interface is an Interface.
Optionally, obtaining the document parameter of the target interface according to a preset policy matched with the Java class includes:
and obtaining according to a preset strategy matched with the Java class, and sequentially obtaining a target interface request path, a request mode, a reference type and a return value type so as to obtain the document parameters of the target interface.
Optionally, reading the source code data of the target interface through the JavaDoc plug-in includes:
and reading the source code data of the target interface through a Doclet interface provided by the JavaDoc plug-in.
In a second aspect, an embodiment of the present application provides an apparatus for generating an interface document, where the apparatus includes:
the document parameter determining module is used for reading the source code data of the target interface through the JavaDoc plug-in and determining the document parameter of the target interface according to the source code data;
and the interface document generation module is used for generating a Maven plugin based on the document parameters so as to generate a target interface document by using the Maven plugin when a command is executed in a project.
Optionally, the document parameters of the target interface include: request mode, request path, entry and return values.
In a third aspect, an embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored, where the computer program is executed by a processor to implement the interface document generation method according to the embodiment of the present application.
In a fourth aspect, an embodiment of the present application provides an electronic device, which includes a memory, a processor, and a computer program stored on the memory and executable by the processor, where the processor executes the computer program to implement the interface document generation method according to the embodiment of the present application.
According to the technical scheme provided by the embodiment of the application, source code data of a target interface are read through a JavaDoc plug-in, and document parameters of the target interface are determined according to the source code data; and generating a Maven plugin based on the document parameters so as to generate a target interface document by using the Maven plugin when a command is executed in a project. By adopting the technical scheme provided by the application, the aim of dynamically generating the interface document in a plug-in mode without invasion can be achieved by directly using a widely used Maven plug-in through Javadoc.
Drawings
FIG. 1 is a flowchart of a method for generating an interface document according to an embodiment of the present application;
FIG. 2 is a schematic diagram of a process for generating an interface document according to an embodiment of the present application;
FIG. 3 is a diagram illustrating an interface document generation architecture according to an embodiment of the present application;
FIG. 4 is a schematic structural diagram of an interface document generation apparatus according to a second embodiment of the present application;
fig. 5 is a schematic structural diagram of an electronic device according to a fourth embodiment of the present application.
Detailed Description
The present application will be described in further detail with reference to the following drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the application and are not limiting of the application. It should be further noted that, for the convenience of description, only some of the structures related to the present application are shown in the drawings, not all of the structures.
Before discussing exemplary embodiments in more detail, it should be noted that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although a flowchart may describe the steps as a sequential process, many of the steps can be performed in parallel, concurrently or simultaneously. In addition, the order of the steps may be rearranged. The process may be terminated when its operations are completed, but may have additional steps not included in the figure. The processes may correspond to methods, functions, procedures, subroutines, and the like.
Example one
Fig. 1 is a flowchart of a method for generating an interface document according to an embodiment of the present application, where the present embodiment is suitable for a case of generating an interface file, and the method may be executed by an apparatus for generating an interface document according to an embodiment of the present application, where the apparatus may be implemented by software and/or hardware, and may be integrated in an electronic device such as an intelligent terminal.
As shown in fig. 1, the method for generating the interface document includes:
s110, reading source code data of a target interface through a JavaDoc plug-in, and determining document parameters of the target interface according to the source code data.
The development specifications of most companies can specify that developers write Javadoc documents for each interface, and the Javadoc documents are the most familiar interface document writing modes and the most intuitive interface document writing modes for the developers. The source code data for the target interface may be data that programs the interface.
In this embodiment, preferably, reading the source code data of the target interface through the JavaDoc plug-in includes: and reading the source code data of the target interface through a Doclet interface provided by the JavaDoc plug-in.
JavaDoc is a technology provided by Sun company, which extracts comments of classes, methods, members, etc. from program source code to form an API help document matching with the source code. That is, only a specific set of tags is used for annotation when the program is written, and after the program is written, the development document of the program can be formed simultaneously through the JavaDoc. The JavaDoc command is used for generating the API document of the user, and the use mode is as follows: and inputting Java doc + file name java in the directory where the target file is located by using the command line.
After reading the source code data of the target interface through the JavaDoc plug-in, the document parameters of the target interface can be determined according to the source code data.
In this embodiment, optionally, the document parameters of the target interface include: request mode, request path, entry and return values. The request mode and the request path may be determined by detection, and the entry and the return value may include the entry itself and the parameter type of the entry. According to the technical scheme, after the document parameters of the target interface are obtained, all the document parameters of the target interface are obtained to serve as a description basis of the target interface. The advantage of this setting is that all document parameters of the target interface can be easily and flexibly acquired.
In this embodiment, preferably, determining the document parameter of the target interface according to the source code data includes: determining the type of a target interface according to the source code data; determining a Java class corresponding to the target interface class according to the target interface class; and acquiring the document parameters of the target interface according to a preset strategy matched with the Java class.
In this embodiment, optionally, if the target interface is an REST interface, the Java class of the target interface is a Controller; and if the target Interface is an RPC Interface, the Java class of the target Interface is an Interface.
The target Interface category may include REST and PRC categories, where an Interface corresponding to the REST Interface is classified as a Controller, and an Interface corresponding to the RPC Interface is classified as an Interface. In the implementation process, the JavaDoc mainly analyzes and processes two classes, namely a Controller class and an Interface class, and can quickly and accurately describe the document parameters of the target interfaces of various classes.
And S120, generating a Maven plugin based on the document parameters so as to generate a target interface document by using the Maven plugin when a command is executed in a project.
After reading, the type of the API (REST/RPC), the request mode, the request path, the entry and the return value can be analyzed, and the Maven plug-in is generated. In the Maven project, Maven instructions may be executed to use Maven plug-ins to retrieve document parameters therein and generate target interface documents.
On the basis of the above technical solutions, optionally, obtaining the document parameter of the target interface according to the preset policy matched with the Java class includes: and obtaining according to a preset strategy matched with the Java class, and sequentially obtaining a target interface request path, a request mode, a reference type and a return value type so as to obtain the document parameters of the target interface.
Specifically, fig. 2 is a schematic diagram of a generation flow of an interface document according to an embodiment of the present application. As shown in FIG. 2, after reading all the class information, the class type is determined, including two classes, Controller and Interface. And traversing the method to obtain the assembly API path of each class. And then obtaining the information of the request mode and reading the method annotation. Reading parameters and parameter annotations, and judging the types of the parameters, wherein the types of the parameters can comprise a clearly-recorded basic type and an array, a basic type packaging class and an array, and a reference type and an array, and the reference type can be a type comprising a reference entity object. When the reference type and the array are used, the attribute information of the reference object needs to be analyzed to obtain a return value. And judging the type of the return value, wherein the type of the return value is similar to that of the input parameter. After determining the type of return value, the API information may be assembled and an API document generated.
According to the technical scheme provided by the embodiment of the application, source code data of a target interface are read through a JavaDoc plug-in, and document parameters of the target interface are determined according to the source code data; and generating a Maven plugin based on the document parameters so as to generate a target interface document by using the Maven plugin when a command is executed in a project. By adopting the technical scheme provided by the application, the aim of dynamically generating the interface document in a plug-in mode without invasion can be achieved by directly using a widely used Maven plug-in through Javadoc.
In order to make the technical solution more obvious for those skilled in the art, the present application also provides a specific embodiment.
Fig. 3 is a schematic diagram of a generation architecture of an interface document according to an embodiment of the present application. As shown in FIG. 3, the present invention is mainly divided into three modules, API classification, method analysis and data type analysis.
1) API classes.
The API is mainly divided into two categories of REST and PRC, wherein an Interface corresponding to the REST Interface is classified into a Controller, and an Interface corresponding to the RPC Interface is classified into an Interface. In the implementation process, the JavaDoc mainly analyzes and processes two classes, namely a Controller class and an Interface class.
2) And (4) analyzing the method.
The API mainly comprises a request mode, a request path, a parameter, a return value and the like, and the JavaDoc analyzes and extracts the contents.
3) And analyzing the data type.
The analysis of the entry and return values of the method mainly aims at analyzing the data types of the entry and return values to obtain detailed information of all attributes.
The technical scheme provided by the invention is realized by dynamically generating the design of the API document in real time through the Doclet capability of Javadoc and a technology which can be integrated with any API platform. The technical scheme is simple and easy to use, has no learning cost, and developers only need to pay attention to the annotation information of the development interfaces. And moreover, the API file can be easily integrated with other API management platforms, and the CD platform can be utilized to update the API file in time through the capability of the Maven plug-in unit during integration.
Example two
Fig. 4 is a schematic structural diagram of an interface document generation apparatus according to a second embodiment of the present application. As shown in fig. 4, the interface document generating apparatus includes:
the document parameter determining module 410 is configured to read source code data of a target interface through a JavaDoc plug-in, and determine a document parameter of the target interface according to the source code data;
and the interface document generation module 420 is used for generating a Maven plugin based on the document parameters so as to generate a target interface document by using the Maven plugin when a command is executed in a project.
According to the technical scheme provided by the embodiment of the application, source code data of a target interface are read through a JavaDoc plug-in, and document parameters of the target interface are determined according to the source code data; and generating a Maven plugin based on the document parameters so as to generate a target interface document by using the Maven plugin when a command is executed in a project. By adopting the technical scheme provided by the application, the aim of dynamically generating the interface document in a plug-in mode without invasion can be achieved by directly using a widely used Maven plug-in through Javadoc.
On the basis of the above technical solution, optionally, the document parameters of the target interface include: request mode, request path, entry and return values.
The product can operate the method provided by any embodiment of the application, and has the corresponding functional modules and beneficial effects of the operation method.
EXAMPLE III
Embodiments of the present application also provide a storage medium containing computer executable instructions, which when executed by a computer processor, are configured to perform a method for generating an interface document, the method comprising:
reading source code data of a target interface through a JavaDoc plug-in, and determining document parameters of the target interface according to the source code data;
and generating a Maven plugin based on the document parameters so as to generate a target interface document by using the Maven plugin when a command is executed in a project.
Storage medium-any of various types of memory devices or storage devices. The term "storage medium" is intended to include: mounting media such as CD-ROM, floppy disk, or tape devices; computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Lanbas (Rambus) RAM, etc.; non-volatile memory such as flash memory, magnetic media (e.g., hard disk or optical storage); registers or other similar types of memory elements, etc. The storage medium may also include other types of memory or combinations thereof. In addition, the storage medium may be located in the computer system in which the program is executed, or may be located in a different second computer system connected to the computer system through a network (such as the internet). The second computer system may provide the program instructions to the computer for execution. The term "storage medium" may include two or more storage media that may reside in different locations, such as in different computer systems that are connected by a network. The storage medium may store program instructions (e.g., embodied as a computer program) that are executable by one or more processors.
Of course, the storage medium containing computer executable instructions provided in the embodiments of the present application is not limited to the generation operation of the interface document described above, and may also execute related operations in the generation method of the interface document provided in any embodiments of the present application.
Example four
The embodiment of the application provides electronic equipment, and the electronic equipment can be integrated with a generation device of the interface document provided by the embodiment of the application. Fig. 5 is a schematic structural diagram of an electronic device according to a fourth embodiment of the present application. As shown in fig. 5, the present embodiment provides an electronic device 500, which includes: one or more processors 520; the storage 510 is configured to store one or more programs, and when the one or more programs are executed by the one or more processors 520, the one or more processors 520 implement the method for generating an interface document according to the embodiment of the present application, the method includes:
reading source code data of a target interface through a JavaDoc plug-in, and determining document parameters of the target interface according to the source code data;
and generating a Maven plugin based on the document parameters so as to generate a target interface document by using the Maven plugin when a command is executed in a project.
The electronic device 500 shown in fig. 5 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present application.
As shown in fig. 5, the electronic device 500 includes a processor 520, a storage 510, an input 530, and an output 540; the number of the processors 520 in the electronic device may be one or more, and one processor 520 is taken as an example in fig. 5; the processor 520, the storage 510, the input device 530, and the output device 540 in the electronic apparatus may be connected by a bus or other means, and are exemplified by a bus 550 in fig. 5.
The storage device 510 is a computer-readable storage medium, and can be used to store software programs, computer executable programs, and module units, such as program instructions corresponding to the interface document generation method in the embodiment of the present application.
The storage device 510 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store data created according to the use of the terminal, and the like. Further, the storage 510 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device. In some examples, storage 510 may further include memory located remotely from processor 520, which may be connected via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The input device 530 may be used to receive input numbers, character information, or voice information, and to generate key signal inputs related to user settings and function control of the electronic apparatus. The output device 540 may include a display screen, speakers, etc.
The electronic device provided by the embodiment of the application can realize the purpose of automatically generating the interface document so as to reduce the management and maintenance cost of the interface document.
The interface document generation device, the storage medium, and the electronic device provided in the above embodiments may be capable of operating the interface document generation method provided in any embodiment of the present application, and have corresponding functional modules and beneficial effects for operating the method. For technical details that are not described in detail in the above embodiments, reference may be made to a method for generating an interface document provided in any embodiment of the present application.
It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present application and the technical principles employed. It will be understood by those skilled in the art that the present application is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the application. Therefore, although the present application has been described in more detail with reference to the above embodiments, the present application is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present application, and the scope of the present application is determined by the scope of the appended claims.
Claims (10)
1. A method for generating an interface document, comprising:
reading source code data of a target interface through a JavaDoc plug-in, and determining document parameters of the target interface according to the source code data;
and generating a Maven plugin based on the document parameters so as to generate a target interface document by using the Maven plugin when a command is executed in a project.
2. The method of claim 1, wherein the document parameters of the target interface comprise: request mode, request path, entry and return values.
3. The method of claim 1, wherein determining document parameters for a target interface based on the source code data comprises:
determining the type of a target interface according to the source code data;
determining a Java class corresponding to the target interface class according to the target interface class;
and acquiring the document parameters of the target interface according to a preset strategy matched with the Java class.
4. The method of claim 3, wherein if the target interface is a REST interface, the Java class of the target interface is a Controller;
and if the target Interface is an RPC Interface, the Java class of the target Interface is an Interface.
5. The method according to claim 3, wherein obtaining the document parameters of the target interface according to the preset policy matching with the Java class comprises:
and obtaining according to a preset strategy matched with the Java class, and sequentially obtaining a target interface request path, a request mode, a reference type and a return value type so as to obtain the document parameters of the target interface.
6. The method of claim 2, wherein reading the source code data of the target interface through the JavaDoc plug-in comprises:
and reading the source code data of the target interface through a Doclet interface provided by the JavaDoc plug-in.
7. An interface document generation apparatus, comprising:
the document parameter determining module is used for reading the source code data of the target interface through the JavaDoc plug-in and determining the document parameter of the target interface according to the source code data;
and the interface document generation module is used for generating a Maven plugin based on the document parameters so as to generate a target interface document by using the Maven plugin when a command is executed in a project.
8. The apparatus of claim 7, wherein the document parameters of the target interface comprise: request mode, request path, entry and return values.
9. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the method of generating an interface document according to any one of claims 1 to 6.
10. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the method of generating an interface document according to any one of claims 1-6 when executing the computer program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010046518.4A CN111258563A (en) | 2020-01-16 | 2020-01-16 | Interface document generation method and device, storage medium and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010046518.4A CN111258563A (en) | 2020-01-16 | 2020-01-16 | Interface document generation method and device, storage medium and electronic equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111258563A true CN111258563A (en) | 2020-06-09 |
Family
ID=70950641
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010046518.4A Withdrawn CN111258563A (en) | 2020-01-16 | 2020-01-16 | Interface document generation method and device, storage medium and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111258563A (en) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111767096A (en) * | 2020-06-29 | 2020-10-13 | 深圳前海微众银行股份有限公司 | Interface document generation method, device, equipment and computer readable storage medium |
| CN111880778A (en) * | 2020-06-30 | 2020-11-03 | 百度在线网络技术（北京）有限公司 | Interface document generation method and device, electronic equipment and storage medium |
| CN112015468A (en) * | 2020-09-25 | 2020-12-01 | 北京百度网讯科技有限公司 | Interface document processing method and device, electronic equipment and storage medium |
| CN112148303A (en) * | 2020-09-28 | 2020-12-29 | Oppo（重庆）智能科技有限公司 | File generation method, device, terminal and storage medium |
| CN112230988A (en) * | 2020-10-16 | 2021-01-15 | 蜂助手股份有限公司 | Interface document generation method and device, computer equipment and storage medium |
| CN112988224A (en) * | 2021-01-21 | 2021-06-18 | 中信银行股份有限公司 | Interface file generation method of micro-service framework, electronic device and storage medium |
| CN113590234A (en) * | 2021-07-12 | 2021-11-02 | 远光软件股份有限公司 | Method, device and equipment for automatically acquiring data and storage medium |
| CN113703781A (en) * | 2021-07-16 | 2021-11-26 | 苏州浪潮智能科技有限公司 | Storage system interface generation method and device, electronic equipment and readable storage medium |
| CN114443129A (en) * | 2021-12-30 | 2022-05-06 | 广东南方新媒体科技有限公司 | Project document automatic generation method, device and storage medium |
-
2020
- 2020-01-16 CN CN202010046518.4A patent/CN111258563A/en not_active Withdrawn
Cited By (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111767096A (en) * | 2020-06-29 | 2020-10-13 | 深圳前海微众银行股份有限公司 | Interface document generation method, device, equipment and computer readable storage medium |
| CN111767096B (en) * | 2020-06-29 | 2024-08-16 | 深圳前海微众银行股份有限公司 | Method, device and equipment for generating interface document and computer readable storage medium |
| CN111880778B (en) * | 2020-06-30 | 2023-12-22 | 百度在线网络技术（北京）有限公司 | Method and device for generating interface document, electronic equipment and storage medium |
| CN111880778A (en) * | 2020-06-30 | 2020-11-03 | 百度在线网络技术（北京）有限公司 | Interface document generation method and device, electronic equipment and storage medium |
| CN112015468A (en) * | 2020-09-25 | 2020-12-01 | 北京百度网讯科技有限公司 | Interface document processing method and device, electronic equipment and storage medium |
| CN112015468B (en) * | 2020-09-25 | 2024-05-14 | 北京百度网讯科技有限公司 | Interface document processing method and device, electronic equipment and storage medium |
| CN112148303A (en) * | 2020-09-28 | 2020-12-29 | Oppo（重庆）智能科技有限公司 | File generation method, device, terminal and storage medium |
| CN112148303B (en) * | 2020-09-28 | 2024-05-28 | Oppo（重庆）智能科技有限公司 | File generation method, device, terminal and storage medium |
| CN112230988A (en) * | 2020-10-16 | 2021-01-15 | 蜂助手股份有限公司 | Interface document generation method and device, computer equipment and storage medium |
| CN112988224A (en) * | 2021-01-21 | 2021-06-18 | 中信银行股份有限公司 | Interface file generation method of micro-service framework, electronic device and storage medium |
| CN113590234A (en) * | 2021-07-12 | 2021-11-02 | 远光软件股份有限公司 | Method, device and equipment for automatically acquiring data and storage medium |
| CN113703781B (en) * | 2021-07-16 | 2023-07-21 | 苏州浪潮智能科技有限公司 | Storage system interface generation method and device, electronic equipment and readable storage medium |
| CN113703781A (en) * | 2021-07-16 | 2021-11-26 | 苏州浪潮智能科技有限公司 | Storage system interface generation method and device, electronic equipment and readable storage medium |
| CN114443129A (en) * | 2021-12-30 | 2022-05-06 | 广东南方新媒体科技有限公司 | Project document automatic generation method, device and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111258563A (en) | Interface document generation method and device, storage medium and electronic equipment | |
| CN109947635B (en) | Data reporting method, device, storage medium and terminal equipment | |
| CN110968305A (en) | Applet visualization generation method, device, equipment and storage medium | |
| US11580228B2 (en) | Coverage of web application analysis | |
| CN114138244A (en) | Method and device for automatically generating model files, storage medium and electronic equipment | |
| WO2024016850A1 (en) | Method and system for processing data conflict, and electronic device and computer-readable storage medium | |
| CN114356964A (en) | Data blood margin construction method and device, storage medium and electronic equipment | |
| CN111078228A (en) | Method and device for converting webpage into small program, server and storage medium | |
| CN111475150B (en) | Cross-language binding method, device, equipment and storage medium | |
| CN110659210A (en) | Information acquisition method and device, electronic equipment and storage medium | |
| CN112970011B (en) | Pedigree in record query optimization | |
| WO2015003452A1 (en) | Methods and systems for file processing | |
| US20150020056A1 (en) | Methods and systems for file processing | |
| CN113741864B (en) | Automatic semantic service interface design method and system based on natural language processing | |
| CN111061522A (en) | Method, device, equipment and storage medium for generating front-end card assembly based on back end | |
| CN113238739A (en) | Plug-in development and data acquisition method, device, electronic equipment and medium | |
| CN111581098B (en) | Method, device, server and storage medium for transferring and storing interface data | |
| CN113050987A (en) | Interface document generation method and device, storage medium and electronic equipment | |
| WO2024124833A1 (en) | Calculation function construction method, calculation engine, electronic device and readable storage medium | |
| CN112416333A (en) | Software model training method, device, system, equipment and storage medium | |
| US11977473B2 (en) | Providing a pseudo language for manipulating complex variables of an orchestration flow | |
| CN113687880B (en) | Method, device, equipment and medium for calling component | |
| CN116414689A (en) | Interface parameter verification method and system based on reflection mechanism | |
| CN115129598A (en) | Risk detection method, device, system and medium for SQL (structured query language) statements | |
| CN114995790A (en) | Component development method and device, computer readable medium and electronic equipment |
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 | ||
| WW01 | Invention patent application withdrawn after publication | ||
| WW01 | Invention patent application withdrawn after publication |
Application publication date: 20200609 |