WO2022230191A1 - Web api definition information generation device, web api definition information generation method, and program - Google Patents

Abstract

A web API definition information generation device according to the present invention comprises: an analysis unit that generates, on the basis of the indent width of each row in the source code of a web application, information in which the parent-child relationship and the adjacency relationship between the rows in the source code are maintained; and a generation unit that combines, on the basis of the parent-child relationship and the adjacency relationship, constituent elements of a web API which are included in the source code together to generate definition information pertaining to the web API. Thus, the web API definition information generation device makes it possible to automatically generate web API definition information without depending on a document of a web application.

Description

Web API definition information generation device, Web API definition information generation method and program

The present invention relates to a WebAPI definition information generation device, a WebAPI definition information generation method, and a program.

The web application executes processing according to the content of the requested HTTP request and returns an HTTP response. Web API information indicating what kind of HTTP requests a Web application accepts is necessary when testing a Web application or creating a client application that uses the Web application. Specifically, one web application has zero or more web APIs, and each web API requires definition information about the path of the URL that waits for requests, the HTTP method that is accepted, and the request parameters.

In order to efficiently test web applications and create client applications, it is desirable that web API definition information be provided as a document written in a fixed format so that it can be processed mechanically. For example, as shown in FIG. 1, when the WebAPI definition information is described in YAML format based on the OpenAPI specification, which is a specification for describing the WebAPI definition information, the WebAPI definition information can be mechanically processed. Easy.

On the other hand, it is not always possible to provide a document that describes WebAPI definition information in a fixed format as shown in Figure 1. If it is not provided, the WebAPI definition information is extracted from a file written in a format other than the dedicated format for the WebAPI description. At this time, it is necessary to search the file for individual elements of the WebAPI definition information such as the WebAPI path and HTTP method, and then combine the elements to extract one WebAPI.

At this time, the relationship between individual elements is not specified, so it must be estimated by some means.

As a conventional technique used in such cases, there is a technique for extracting WebAPI definition information from a Web application document written in HTML for the purpose of being read by humans (Non-Patent Document 1). According to this technique, it is possible to discover the path and HTTP method, which are the elements of the WebAPI definition information, from within the HTML document. Further, by using the structure of the DOM tree constructed from the document to estimate the correspondence between each element and linking each element, it is possible to automatically obtain WebAPI definition information. For example, even if WebAPI definition information with a path of "user/{id}" and an HTTP method of "get" is described in any of the three patterns shown in (1) to (3) in FIG. , each element can be associated from the structure of the DOM tree and output as one piece of WebAPI definition information.

However, with the conventional technology, correct WebAPI definition information cannot be obtained when the document of the Web application is not created, is not updated, contains errors, or otherwise deviates from the actual implementation. In addition, since the conventional technology combines the elements of the WebAPI definition information using the DOM tree, it is difficult to apply it to other formats that do not use the DOM tree.

The present invention has been made in view of the above points, and an object of the present invention is to enable automatic generation of WebAPI definition information without depending on Web application documents.

Therefore, in order to solve the above problem, the WebAPI definition information generation device includes an analysis unit that generates information that holds the parent-child relationship and the adjacency relationship of each line in the source code of the Web application, based on the indentation width of each line in the source code of the Web application. and a generation unit that generates definition information of the WebAPI by combining WebAPI components included in the source code based on the parent-child relationship and the adjacency relationship.

It is possible to automatically generate web API definition information without depending on the web application document.

FIG. 3 is a diagram showing an example of WebAPI definition information described in YAML format; FIG. 4 is a diagram showing an example of WebAPI definition information in an HTML document; 1 is a diagram showing a hardware configuration example of a WebAPI definition information generating device 10 according to an embodiment of the present invention; FIG. 1 is a diagram showing a functional configuration example of a WebAPI definition information generating device 10 according to an embodiment of the present invention; FIG. FIG. 4 is a diagram for explaining indentation; 4 is a flowchart for explaining an example of a processing procedure executed by a source code structure analysis unit 11; FIG. 4 is a diagram showing an example of program structure information; FIG. 4 is a diagram showing an example of a path definition in a source code; FIG. FIG. 10 is a diagram showing an example of definition on a source code of WebAPI definition information elements of a path and an HTTP method; 4 is a flowchart for explaining an outline of a processing procedure executed by a WebAPI definition information generation unit 12; FIG. 11 is a flowchart for explaining a processing procedure for adding a WebAPI definition information element to a node of program structure information; FIG. FIG. 10 is a diagram for explaining an example of a processing procedure of path list generation processing; FIG. 11 is a flowchart for explaining an example of a processing procedure for generating a list of WebAPI definition information; FIG.

In the present embodiment, a WebAPI definition information generation device that estimates the relationship between elements of WebAPI definition information searched from the source code of a Web application, combines the elements, and outputs a list of WebAPI definition information. 10 is disclosed. In this embodiment, indentation of the source code is used to analyze the structure of the source code in order to estimate the relationship between the elements of the WebAPI definition information.

Embodiments of the present invention will be described below based on the drawings. FIG. 3 is a diagram showing a hardware configuration example of the WebAPI definition information generation device 10 according to the embodiment of the present invention. The WebAPI definition information generation device 10 of FIG. have.

A program that implements processing in the WebAPI definition information generation device 10 is provided by a recording medium 101 such as a CD-ROM. When the recording medium 101 storing the program is set in the drive device 100 , the program is installed from the recording medium 101 to the auxiliary storage device 102 via the drive device 100 . However, the program does not necessarily need to be installed from the recording medium 101, and may be downloaded from another computer via the network. The auxiliary storage device 102 stores installed programs, as well as necessary files and data.

The memory device 103 reads and stores the program from the auxiliary storage device 102 when a program activation instruction is received. The CPU 104 implements functions related to the WebAPI definition information generation device 10 according to programs stored in the memory device 103 . The interface device 105 is used as an interface for connecting to a network. A display device 106 displays a program-based GUI (Graphical User Interface) or the like. The input device 107 is composed of a keyboard, a mouse, etc., and is used to input various operational instructions.

FIG. 4 is a diagram showing a functional configuration example of the WebAPI definition information generation device 10 according to the embodiment of the present invention. As shown in FIG. 4 , the WebAPI definition information generation device 10 has a source code structure analysis unit 11 and a WebAPI definition information generation unit 12 . Each of these units is realized by processing that one or more programs installed in the WebAPI definition information generation device 10 cause the CPU 104 to execute.

The source code structure analysis unit 11 derives the structure of the source code (generates information indicating the structure of the source code) based on the indentation of the source code of the Web application (hereinafter simply referred to as "source code"). )do.

The WebAPI definition information generation unit 12 receives as inputs the components of the WebAPI definition information (WebAPI definition information elements) searched (extracted) from the source code and the structural information of the source code, estimates the relationship between the elements, and estimates the result. The elements are combined based on to generate the WebAPI definition information.

In FIG. 4, the WebAPI definition information element search device 20 executes the search (extraction) of the WebAPI definition information element from the source code. However, the WebAPI definition information generating device 10 may also perform such a search. The search for the WebAPI definition information element from the source code can be realized using known techniques such as character string search using regular expressions, for example.

Each part will be explained in more detail below.

[Source code structure analysis unit 11]
In many programming languages where source code is written as text, even if multiple consecutive line breaks or white spaces are inserted where line breaks or white spaces are required or allowed by the syntax, Interpreted as if you had inserted a single newline or whitespace. The minimum number of line breaks and white spaces necessary for syntax is insufficient for human understanding and editing. shaping is done.

The programming language syntax has a recursive structure that has another sentence as an element that constitutes another sentence. A common practice in formatting source code is to insert a line break at the end of each sentence. In addition, when another sentence is described as a component of a certain sentence, more white spaces than the certain sentence are inserted at the beginning of the line of the other sentence. Indenting with white space in this way is called "indenting". Also, the number of consecutive white spaces at the beginning of a line is called "indentation width".

For example, in the example shown in FIG. 5, outer_block includes inner_block_1 and inner_block_2 as components. By indenting each component with an indentation width of 2, each component is shaped so that it is easy to visually determine that it is a component of outer_block.

The source code structure analysis unit 11 analyzes how the source code is indented (the manner of indentation of each line in the source code), thereby analyzing the hierarchy of sentences without depending on the syntax defined for each programming language. Analyze structure. The source code structure analysis unit 11 outputs the following program structure information for each file (file in which source code is recorded) as an analysis result. The definitions below are based on the BNF (Backus-Naur form) notation.
program structure information ::== root node root node ::== ordered node *
ordered node::==index node node::==line number ordered node*
According to the above, a "root node" represents a set of zero or more ordered nodes. An index, which is an element of an ordered node, is a value that uniquely identifies each node in a group of nodes having the same parent node, and is a natural number that indicates the order of appearance in the source code. Also, the ordered nodes of the elements of the node are the child nodes of the node. A tree structure (recursive structure) is represented by a node including ordered nodes, which are child nodes, as elements.

A processing procedure executed by the source code structure analysis unit 11 will be described.

FIG. 6 is a flowchart for explaining an example of a processing procedure executed by the source code structure analysis unit 11. FIG. The source code structure analysis unit 11 executes loop processing L1 for each file included in a list of source code files of a Web application. One file to be processed in the loop processing L1 is hereinafter referred to as a "target file".

In step S101, the source code structure analysis unit 11 generates a root node without ordered nodes. Subsequently, the source code structure analysis unit 11 creates an empty stack (S102). This stack can store pairs of indent widths and references to nodes as elements.

Next, the source code structure analysis unit 11 opens the target file (S103). Subsequently, the source code structure analysis unit 11 executes loop processing L2 including steps S104 to S112 for each line of the target file. Loop processing L2 is executed for all lines of the target file.

In step S104, the source code structure analysis unit 11 reads the first line (hereinafter referred to as "target line") among the unprocessed lines in the target file. Subsequently, the source code structure analysis unit 11 determines whether the target line is a blank line (S105). If the target line is a blank line (Yes in S105), the source code structure analysis unit 11 does not execute step S106 and subsequent steps for the target line.

If the target line is not blank (No in S105), the source code structure analysis unit 11 acquires the indentation width of the target line (S106). Next, the source code structure analysis unit 11 compares the indentation width of the target line with the indentation width of the element at the top of the stack, and if the two match or if the indentation width of the target line is smaller, The top element on the stack is removed from the stack and discarded (S107). The source code structure analysis unit 11 continues this operation until the stack becomes empty or the indentation width of the element at the top of the stack becomes smaller than the indentation width of the target line.

Note that step S107 is a process for searching for candidates for the parent of the target row. That is, the source code structure analysis unit 11 extracts elements stacked on the stack until an element with an indentation width smaller than that of the target line is found. identify as the parent of A parent is a parent node in the tree structure (hierarchical structure) of the source code.

Subsequently, the source code structure analysis unit 11 generates a node (hereinafter referred to as "target node") that includes the line number of the target line as an element (S108). Subsequently, the source code structure analysis unit 11 identifies the parent node of the target node (S109). Specifically, when the stack is empty after step S107 (that is, when the parent of the target line is not found), the source code structure analysis unit 11 identifies the root node as the parent node. On the other hand, if the stack is not empty (that is, if the parent of the target line is found), the source code structure analysis unit 11 selects the node that the top element of the stack (that is, the element related to the parent of the target line) has a reference. Identifies it as a parent node.

Subsequently, the source code structure analysis unit 11 generates ordered nodes (having the target node as an element) including the target node (S110). At this time, the source code structure analysis unit 11 identifies the index, which is the element of the ordered node, based on the parent node of the target node. Specifically, if the parent node does not have an ordered node, the source code structure analysis unit 11 sets the index to 0; A value obtained by adding 1 is used as the index.

Subsequently, the source code structure analysis unit 11 adds the generated ordered node as one of the ordered nodes of the parent node (S111).

Subsequently, the source code structure analysis unit 11 adds an element including the indent width of the target line and the reference to the target node to the top of the stack (S112).

When the processing procedure in FIG. 6 ends, program structure information is generated (derived) for each file. The program structure information is information representing a tree structure (hierarchical structure) in which lines with relatively small indentation are parent nodes and lines with relatively large indentation are child nodes. The source code structure analysis unit 11 associates each piece of program structure information with the file name of the source code file that generated the program structure information.

FIG. 7 is a diagram showing an example of program structure information. In FIG. 7, (1) is an example of source code, and (2) is program structure information generated for the source code of (1). In (2), italic numbers indicate indexes, and non-italic numbers indicate line numbers. Thus, the program structure information holds the parent-child relationship and adjacency relationship (back-and-forth relationship) of each line of the source code.

[Web API definition information generation unit 12]
The WebAPI definition information generation unit 12 uses the input WebAPI definition information elements and the program structure information obtained from the source code structure analysis unit 11 to output a list of WebAPI definition information.

Each of the WebAPI definition information element and the WebAPI definition information is defined as follows.
WebAPI definition information element::==Token Element type identifier File name Line number WebAPI definition information ::==HTTP method path The token in the WebAPI definition information element is a character indicating the WebAPI definition information element (HTTP method or path component) column, and the element type identifier is an identifier for distinguishing whether the relevant WebAPI definition information element is an HTTP method or a component of a path. The file name and line number represent the file name of the file containing the WebAPI definition information element among the files of the Web application, and the line number of the line containing the WebAPI definition information element in the file.

The HTTP method and path in the WebAPI definition information are character strings indicating the HTTP method or path related to the WebAPI, respectively.

The relationship between each WebAPI definition information element includes "hierarchical relationship between paths" and "relationship between paths and HTTP methods".

<Hierarchical relationship between paths>
Since the path has a hierarchical structure separated by slashes ("/"), it may be defined hierarchically even in the source code, for example, as shown in FIG. In the example of FIG. 8, each of "/user" and "/{id}" is a WebAPI definition information element that constitutes a path. /user/{id}" is the Web API path.

<Relationship between paths and HTTP methods>
The Web API definition information elements of the path and HTTP method may be defined in the same line or adjacent lines of the source code, or the line where one is defined may be a component of the line where the other is defined. many. (1) in FIG. 9 shows an example defined in the same line. (2) in FIG. 9 shows an example defined by adjacent lines. (3) in FIG. 9 shows an example in which one defined line is a component of the other defined line.

For any of the examples in FIG. 9, the HTTP method WebAPI definition element "Get" and the WebAPI definition information elements "/user" and "/{id}" as path components are combined. The WebAPI definition information is configured in this way.

FIG. 10 is a flowchart for explaining an overview of the processing procedure executed by the WebAPI definition information generation unit 12. FIG.

The WebAPI definition information generation unit 12 first adds (corresponds to) the information of the WebAPI definition information element corresponding to the node of the program structure information (S200).

Next, the WebAPI definition information generation unit 12 uses the structure indicated by the program structure information to combine (combine) the WebAPI definition information elements that make up the paths, thereby generating a path list (S300).

Subsequently, the WebAPI definition information generation unit 12 searches for the WebAPI definition information element of the HTTP method corresponding to each path forming the list, and generates a list of WebAPI definition information by associating the searched WebAPI definition information elements. (S400).

The details of step S200 will be described. FIG. 11 is a flowchart for explaining a processing procedure for adding a WebAPI definition information element to a node of program structure information. The WebAPI definition information generation unit 12 executes loop processing L3 for each WebAPI definition information element searched by the WebAPI definition information element search device 20 from the source code of the Web application. A WebAPI definition information element to be processed in loop processing L3 is hereinafter referred to as a "target definition information element".

In step S201, the WebAPI definition information generation unit 12 selects the program structure information corresponding to the file name included in the target definition information element (generated for the file associated with the file name) as a processing target. Hereinafter, program structure information selected as a processing target is referred to as "target structure information".

Next, the WebAPI definition information generation unit 12 searches for a node (hereinafter referred to as "target node") that includes a line number that matches the line number of the target definition information element from the target structure information (S202). Specifically, the WebAPI definition information generation unit 12 recursively selects ordered nodes of child elements from the root node in the target structure information, and compares the line number of each node with the line number of the target definition information element. . The WebAPI definition information generation unit 12 identifies a node whose line number matches the object definition information element as an object node.

Subsequently, the WebAPI definition information generating unit 12 updates the target node by adding the information of the target definition information element to the target node (S203). Therefore, the updated node (node with WebAPI definition information element) has the following format.
Node with WebAPI definition information element ::== line number Ordered node* WebAPI definition information element*
Next, details of step 300 in FIG. 10 will be described.

FIG. 12 is a diagram for explaining an example of the processing procedure of the path list generation processing. The processing procedure shown in FIG. 12 shows processing for generating a list of paths by performing a depth-first search (in order of precedence) on the tree structure indicated by the program structure information.

The WebAPI definition information generation unit 12 executes loop processing L4 for all program structure information (program structure information to which WebAPI definition information elements have been added). The program structure information to be processed in the loop processing L4 is hereinafter referred to as "target structure information".

In step S301, the WebAPI definition information generation unit 12 generates an empty stack. Subsequently, the WebAPI definition information generation unit 12 selects the root node of the target structure information as a processing target (S302). Hereinafter, a node to be processed will be referred to as a "target node". For the sake of convenience, the root node here is a virtual node whose child nodes are the root node defined above (a set of 0 or more ordered nodes).

Next, the WebAPI definition information generation unit 12 determines whether the target node has the WebAPI definition information element of the path (S303). That is, the WebAPI definition information generation unit 12 determines whether or not the target node has a WebAPI definition information element and the element type identifier of the WebAPI definition information element is a value indicating a path.

If the target node does not have the WebAPI definition information element of the path (No in S303), proceed to step S305. This is because all nodes are processed in a depth-first manner even if a node in the middle of searching does not have a WebAPI definition information element.

On the other hand, if the target node has the WebAPI definition information element of the path (Yes in S303), the WebAPI definition information generation unit 12 combines the token of the WebAPI definition information element after the currently constructed path (S304). If the beginning of the token is not "/" (a symbol that separates paths), the WebAPI definition information generation unit 12 combines "/" after the currently constructed path, and then combines the token. If there is no path currently being constructed, the path being constructed is treated as an empty character string. Subsequently, the process proceeds to step S305.

In step S305, the WebAPI definition information generation unit 12 generates a list of the currently configured path, the node that last updated the currently configured path, and unprocessed nodes among the child nodes (ordered nodes) of the target node. and are added to the top of the stack as a set of three. Note that the ``node that last updated the path currently being constructed'' is the target node if the target node has the WebAPI definition information element of the path, and if not, it is the target node that has the WebAPI definition information element at the end. It is the determined node.

Subsequently, the WebAPI definition information generating unit 12 determines whether or not the list of unprocessed nodes includes the element (S306). That is, it is determined whether or not there is one or more unprocessed child nodes. If the list of unprocessed child nodes includes an element (Yes in S306), the WebAPI definition information generation unit 12 selects the node with the smallest index value in the list of unprocessed child nodes as a processing target. (S307), and repeats steps S304 and subsequent steps Note that selecting the node with the smallest index value in the list of unprocessed child nodes for processing is a method of processing all nodes without omission. This is an example, and as long as it is possible to distinguish whether each node is processed or not, an unprocessed child node may be randomly selected as a processing target.

On the other hand, if the list of unprocessed child nodes does not contain any elements (No in S306), the path that is currently being constructed and the node that last updated the path that is currently being constructed, which is included in the element at the top of the stack. Add the pair to the path list (S308). At this time, if there is a path that is completely included in the currently configured path in the path list, the WebAPI definition information generation unit 12 removes the element including the included path from the path list. For example, if the path list contains a path "/user" and the path currently being constructed is "/user/{id}", the WebAPI definition information generation unit 12 generates "/ remove the element containing the path "user" from the path list.

Next, the WebAPI definition information generation unit 12 deletes the element at the top of the stack (S309). In the process of sequentially processing the child nodes of the node related to the element, after processing one child node, it is necessary to hold the element on the stack in order to restore the state before processing the next child node. This is because there is no longer any unprocessed child node, so there is no longer a need to hold the element in the stack.

Next, the WebAPI definition information generation unit 12 determines whether the stack is empty (S310). If the stack is not empty (No in S310), the WebAPI definition information generator 12 reads the list of the node that last updated the path currently being constructed and the unprocessed child nodes from the top element of the stack (S311). . Subsequently, the WebAPI definition information generation unit 12 selects the most indexed child node that remains in the list of unprocessed child nodes even though the process has been completed. The small node is treated as a processed node (the node is deleted from the unprocessed child node list), and the remaining unprocessed child node list is processed, and steps S306 and subsequent steps are repeated.

On the other hand, if the stack is empty (Yes in S310), the WebAPI definition information generation unit 12 outputs a path list based on the target structure information (S312). That is, a path list is generated for each program structure information.

When the above processing procedure is executed for all program structure information, the processing in FIG. 12 ends.

Next, the details of step S400 in FIG. 10 will be described. FIG. 13 is a flowchart for explaining an example of a processing procedure for generating a list of WebAPI definition information.

The WebAPI definition information generation unit 12 executes loop processing L5 including loop processing L6 and step S406 for each path list generated for each program structure information. A path list to be processed in the loop processing L5 is hereinafter referred to as a "target path list".

A loop process L6 is a loop process for each element (path) of the target path list, and includes steps S401 to S405. An element to be processed in loop processing L6 is hereinafter referred to as a "target element".

In step S401, the WebAPI definition information generation unit 12 acquires the path and the node (hereinafter referred to as the "target node") that last updated the path (hereinafter referred to as the "target path") from the target element. Note that the node that last updated the path is the node that has the token linked to the lowest layer of the path.

Next, the WebAPI definition information generation unit 12 determines that the program structure information to which the target node belongs (that is, the program structure information corresponding to the target path list) is adjacent to the target node (has a relationship of immediately before and after in the source code). ) nodes (ordered nodes whose indices are different by 1 among sibling nodes having a common parent node) and the target node are searched for a node having the WebAPI definition information element of the HTTP method (S402).

Subsequently, if there is one or more applicable nodes, the WebAPI definition information generating unit 12 generates WebAPI definition information by combining the HTTP method and target path of each applicable node, and The definition information is added to the list of WebAPI definition information (S403).

Note that steps S402 and S403 are processes corresponding to examples defined in the same line and examples defined in adjacent lines in the "relationship between paths and HTTP methods" described above.

Next, the WebAPI definition information generation unit 12 searches for a child node having the WebAPI definition information element of the HTTP method among the child nodes of the target node (S404).

When one or more applicable child nodes are found, the WebAPI definition information generation unit 12 generates WebAPI definition information by combining the HTTP method and target path of each applicable child node. The WebAPI definition information is added to the list of WebAPI definition information (S405).

When the loop processing L6 is executed for all the elements of the target path list, the WebAPI definition information generation unit 12 outputs the list of WebAPI definition information generated for the target path list (S406).

When loop processing L5 is executed for all path lists, the processing in FIG. 13 ends.

As described above, according to the present embodiment, it is possible to automatically generate WebAPI definition information without depending on Web application documents. That is, since the WebAPI definition information is automatically generated based on the elements of the WebAPI definition information searched from the source code, it is possible to solve the problem of the discrepancy between the implementation of the Web application and the automatically generated WebAPI definition information. . In addition, by estimating the relationship between elements from the result of structural analysis using indentation, it is possible to automatically generate WebAPI definition information from a wide range of Web applications without depending on the grammar of a specific programming language.

Using the obtained WebAPI definition information, for example, developers can create tests without omission by utilizing techniques such as manual or automatic test data generation.

In addition, in the present embodiment, the source code structure analysis unit 11 is an example of an analysis unit. The WebAPI definition information generator 12 is an example of a generator.

Although the embodiments of the present invention have been described in detail above, the present invention is not limited to such specific embodiments, and various modifications can be made within the scope of the gist of the present invention described in the claims.・Changes are possible.

10 WebAPI definition information generation device 11 Source code structure analysis unit 12 WebAPI definition information generation unit 20 WebAPI definition information element search device 100 Drive device 101 Recording medium 102 Auxiliary storage device 103 Memory device 104 CPU
105 interface device 106 display device 107 input device B bus

Claims (7)

1. an analysis unit that generates information holding the parent-child relationship and the adjacency relationship of each line in the source code based on the indentation width of each line in the source code of the Web application;
   a generation unit that generates definition information of the WebAPI by combining the components of the WebAPI included in the source code based on the parent-child relationship and the adjacency relationship;
   A WebAPI definition information generation device characterized by comprising:
2. The analysis unit generates information that holds the parent-child relationship in which a line with a relatively large indentation width is a child and a line with a relatively small indentation width is a parent,
   The Web API definition information generation device according to claim 1, characterized by:
3. The generation unit generates definition information of the WebAPI by combining the components of the WebAPI based on the parent-child relationship and the adjacency relationship regarding a row containing the components of the WebAPI.
   3. The Web API definition information generation device according to claim 1, wherein:
4. an analysis procedure for generating information holding a parent-child relationship and an adjacency relationship of each line in the source code based on the indentation width of each line in the source code of the web application;
   a generation procedure for generating definition information of the WebAPI by combining WebAPI components included in the source code based on the parent-child relationship and the adjacency relationship;
   A web API definition information generating method, characterized in that a computer executes:
5. The analysis procedure generates information that holds the parent-child relationship in which a line with a relatively large indent width is a child and a line with a relatively small indent width is a parent.
   5. The WebAPI definition information generation method according to claim 4, wherein:
6. The generation procedure generates definition information of the WebAPI by combining the components of the WebAPI based on the parent-child relationship and the adjacency relationship regarding the row containing the component of the WebAPI.
   6. The WebAPI definition information generating method according to claim 4 or 5, characterized in that:
7. A program characterized by causing a computer to execute the WebAPI definition information generating method according to any one of claims 4 to 6.

Images