CN112181370B - Data interaction relation generation method, computer equipment and storage medium - Google Patents

Data interaction relation generation method, computer equipment and storage medium Download PDF

Info

Publication number
CN112181370B
CN112181370B CN202010979865.2A CN202010979865A CN112181370B CN 112181370 B CN112181370 B CN 112181370B CN 202010979865 A CN202010979865 A CN 202010979865A CN 112181370 B CN112181370 B CN 112181370B
Authority
CN
China
Prior art keywords
information
code
interface
analysis
parsing
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.)
Active
Application number
CN202010979865.2A
Other languages
Chinese (zh)
Other versions
CN112181370A (en
Inventor
庄锐
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Wuhan United Imaging Healthcare Co Ltd
Original Assignee
Wuhan United Imaging Healthcare Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Wuhan United Imaging Healthcare Co Ltd filed Critical Wuhan United Imaging Healthcare Co Ltd
Priority to CN202010979865.2A priority Critical patent/CN112181370B/en
Publication of CN112181370A publication Critical patent/CN112181370A/en
Application granted granted Critical
Publication of CN112181370B publication Critical patent/CN112181370B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/20—Software design
    • G06F8/22—Procedural
    • 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
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/40—Transformation of program code
    • G06F8/41—Compilation
    • G06F8/42—Syntactic analysis
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/40—Transformation of program code
    • G06F8/41—Compilation
    • G06F8/42—Syntactic analysis
    • G06F8/425—Lexical analysis
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/40—Transformation of program code
    • G06F8/41—Compilation
    • G06F8/42—Syntactic analysis
    • G06F8/427—Parsing
    • 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/448—Execution paradigms, e.g. implementations of programming paradigms
    • G06F9/4482—Procedural

Abstract

The application relates to a data interaction relationship generation method, computer equipment and a storage medium. The method comprises the steps of obtaining front-end codes and rear-end codes of target applications, analyzing the front-end codes to obtain front-end information comprising correlation information among interface calling information of the front end, analyzing the rear-end codes to obtain rear-end information comprising correlation information among interface realizing information of the rear end, and then generating a data interaction relation between the front end and the rear end according to the front-end information and the rear-end information. According to the method, the information and the front-end interface calling information are realized by scanning the front-end code and the back-end code of the target application and associating the back-end interface, the data interaction relation between the front end and the back end is automatically generated, the time and the effort of an application developer for manually combing the data interaction relation between the front end and the back end are saved, and the application development efficiency of the application developer is further improved.

Description

Data interaction relation generation method, computer equipment and storage medium
Technical Field
The present application relates to the field of computer application technologies, and in particular, to a method for generating a data interaction relationship, a computer device, and a storage medium.
Background
With the popularization and application of the Web technology, a user can access application programs bearing various business processes only through a browser. Generally, a Web application is divided into a front-end application and a back-end service, the back-end service provides a service and opens an interface, and the front-end application calls the back-end service interface to realize various functions.
In order to maintain the Web application, a developer usually provides an interface document for the back-end service while developing the Web application, the interface document records a plurality of information related to an interface, and the developer can know information such as the type, interface parameters, input and output methods and the like of the back-end service providing interface by checking the interface document, so that the developer can acquire interface calling of the front-end application and interface implementation conditions of the back-end service at any time, and thus, auxiliary development is performed.
However, the above interface document only describes the relevant information of the interface on the back-end service, and in practical application, a complex data interaction process exists between the front-end application and the back-end service of the Web application, and if a developer wants to know the data interaction process between the front-end application and the back-end service, the developer must know the complex data interaction process between the front-end application and the back-end service by operations such as manually reading codes, memorizing interaction details, analyzing data, and the like, so that the method occupies a large amount of human resources and has extremely low efficiency.
Disclosure of Invention
In view of the foregoing, it is necessary to provide a method for generating a data interaction relationship, a computer device, and a storage medium, which can effectively develop the efficiency of an application and reduce the labor cost for developing the application.
In a first aspect, a method for generating a data interaction relationship includes:
acquiring a front-end code and a back-end code of a target application;
analyzing the front-end code to obtain front-end information; the front-end information comprises the correlation information among the interface calling information of the front end;
analyzing the back-end code to obtain back-end information; the back end information comprises the correlation information among the interface realization information of the back end;
and generating a data interaction relation between the front end and the back end according to the front end information and the back end information.
In one embodiment, parsing the front-end code to obtain front-end information includes:
performing lexical analysis on the front-end codes to obtain first front-end analysis codes; the first front-end analysis code comprises a first identifier used for replacing a keyword in the front-end code;
and carrying out syntax analysis on the first front-end analysis code to obtain front-end information.
In one embodiment, the lexical analysis of the front-end code to obtain a first front-end analysis code includes:
performing lexical analysis on the front-end code, and identifying a keyword in the front-end code to obtain a corresponding first identifier;
and replacing the key words in the front-end code by using the first identifier correspondingly to obtain a first front-end analysis code.
In one embodiment, parsing the first front-end parsing code to obtain front-end information includes:
matching a first preset grammar rule, and carrying out grammar analysis on the first front-end analysis code to obtain a second front-end analysis code;
analyzing the second front-end analysis code, and extracting interface calling information of the front end from the second front-end analysis code; the second front-end analysis code comprises the calling information of each interface of the front end;
and substituting the calling information of each interface into a preset first driving function for calculation to obtain front-end information.
In one embodiment, the code parsing of the backend code to obtain the backend information includes:
performing lexical analysis on the rear-end codes to obtain first rear-end analysis codes; the first front-end analysis code comprises a second identifier used for replacing the key words in the front-end code;
and carrying out syntax analysis on the first back-end analysis code to obtain back-end information.
In one embodiment, the lexical parsing the backend code to obtain a first backend parsed code includes:
performing lexical analysis on the rear-end code, and identifying a keyword in the rear-end code to obtain a corresponding second identifier;
and using the key words in the substitute back-end codes corresponding to the second identifiers to obtain the first back-end analysis codes.
In one embodiment, parsing the first backend parsing code to obtain backend information includes:
matching a second preset grammar rule, and carrying out grammar analysis on the first back-end analysis code to obtain a second back-end analysis code;
analyzing the second back-end analysis code, and extracting back-end interface implementation information from the second back-end analysis code; the second back-end analysis code comprises back-end interface realization information;
and substituting the realization information of each interface into a preset second driving function for calculation to obtain the back-end information.
In one embodiment, the interface calling information of the front end includes successful interface calling return information, and the front end information includes a cascade calling relationship between the interfaces when the interfaces are called, and the method further includes:
performing lexical analysis on the front-end code, and identifying newly added keywords in the front-end code to obtain a corresponding third identifier; newly-added keywords represent that the front-end calls the interface successfully;
replacing the newly added keywords in the front-end code by using the third identifier to obtain a third front-end analysis code;
matching a preset newly added grammar rule, and carrying out grammar analysis on the third front-end analysis code to obtain a fourth front-end analysis code; presetting new grammar rules including describing the success of the front end calling interface and continuing to call the grammar rule of the next interface; the fourth front-end analysis code comprises return information of successful calling of each interface;
analyzing the fourth front-end analysis code, and extracting return information of each interface calling success from the fourth front-end analysis code;
and substituting the successful calling return information of each interface into a preset third driving function for calculation to obtain front-end information.
In one embodiment, generating the data interaction relationship between the front end and the back end according to the front end information and the back end information includes:
extracting overlapped information between the front-end information and the back-end information;
determining interface calling information associated with the overlapped information in the front-end information;
determining interface implementation information which is backward associated with the overlapped information in the back-end information;
and logically connecting the overlapping information, the forward associated interface calling information and the backward associated interface implementation information to generate a data interaction relation between the front end and the back end.
In a second aspect, an apparatus for generating a data interaction relationship, the apparatus includes:
the acquisition module is used for acquiring a front-end code and a back-end code of the target application;
the first analysis module is used for analyzing the front-end code to obtain front-end information; the front-end information comprises correlation information among interface calling information of the front end;
the second analysis module is used for analyzing the back-end code to obtain back-end information; the back-end information comprises the correlation information among the interface realization information of the back end;
and the generating module is used for generating a data interaction relation between the front end and the back end according to the front end information and the back end information.
In a third aspect, a computer device comprises a memory and a processor, the memory stores a computer program, and the processor implements the method of the first aspect when executing the computer program.
In a fourth aspect, a computer-readable storage medium has stored thereon a computer program which, when executed by a processor, implements the method of the first aspect described above.
According to the method and the device for generating the data interaction relationship, the computer equipment and the storage medium, the front end code and the rear end code of the target application are obtained and analyzed to obtain the front end information comprising the association information among the interface calling information of the front end, the rear end code is analyzed to obtain the rear end information comprising the association information among the interface realizing information of the rear end, and then the data interaction relationship between the front end and the rear end is generated according to the front end information and the rear end information. Compared with the traditional method for manually generating the data interaction relationship between the front end and the rear end, the method saves time and energy of an application developer for manually combing the data interaction relationship between the front end and the rear end, further improves the application development efficiency of the application developer, and greatly reduces the labor cost.
Drawings
FIG. 1 is a diagram illustrating an internal structure of a computer device according to an embodiment;
FIG. 2 is a flowchart illustrating a method for generating a data interaction relationship according to an embodiment;
FIG. 3 is a flowchart illustrating an implementation manner of S102 in the embodiment of FIG. 2;
FIG. 4 is a flowchart illustrating an implementation manner of S201 in the embodiment of FIG. 3;
FIG. 5 is a flowchart illustrating an implementation manner of S202 in the embodiment of FIG. 3;
FIG. 6 is a flowchart illustrating an implementation manner of S103 in the embodiment of FIG. 2;
FIG. 7 is a flowchart illustrating an implementation manner of S501 in the embodiment of FIG. 6;
FIG. 8 is a flowchart illustrating an implementation manner of S502 in the embodiment of FIG. 6;
FIG. 9 is a flowchart illustrating a method for generating data interactions according to an embodiment;
FIG. 10 is a relational diagram of data interactions in one embodiment;
FIG. 11 is a flowchart illustrating an implementation of S104 in the embodiment of FIG. 2;
FIG. 12 is a flowchart illustrating a method for generating data interactions according to an embodiment;
fig. 13 is a schematic structural diagram of a data interaction relationship generation apparatus in one embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of and not restrictive on the broad application.
The method for generating the data interaction relationship provided by the present application may be applied to a computer device shown in fig. 1, where the computer device may be a server, the computer device may also be a terminal, and an internal structure diagram of the computer device may be as shown in fig. 1. The computer device includes a processor, a memory, a network interface, a display screen, and an input device connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a method of generating a data interaction relationship. The display screen of the computer equipment can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, a key, a track ball or a touch pad arranged on a shell of the computer equipment, an external keyboard, a touch pad or a mouse and the like.
Those skilled in the art will appreciate that the architecture shown in fig. 1 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, as shown in fig. 2, a method for generating a data interaction relationship is provided, which is described by taking the method as an example applied to the computer device in fig. 1, and includes the following steps:
s101, front-end codes and back-end codes of target applications are obtained.
The front end is an interface calling party and is used for calling the back end interface. The front-end calls the back-end interface in a more common mode of ajax, and the calling can be completed by formulating an interface address and parameters. The front-end code includes front-end interface call rules that implement the target application. The back end is an interface provider and is used for providing the interface provider for the front end to call so as to realize data interaction between the front end and the back end. The backend code includes backend interface implementation rules that implement the target application. The interface implementation generally adopts an @ RequestMapping annotation mode. The target application may be a Web application or may be another type of application.
Specifically, when analyzing the data interaction relationship between the front end and the back end in the service flow corresponding to the target application, the computer device may first scan the front end code and the back end code sentence by sentence, respectively, to read each line of codes of the front end code and each line of codes of the back end code.
S102, analyzing the front-end code to obtain front-end information; the front-end information comprises the correlation information among the interface calling information of the front end.
The interface calling information comprises any one of a front-end method name, ajax called by the front-end method name, a rear-end interface name accessed by the ajax, and a parameter list contained in the ajax. The front-end information comprises different interface calling information of the front end.
Specifically, when the computer device reads the front-end code, it may further perform lexical and syntactic analysis on each line of the read front-end code, and analyze the front-end code into a front-end code file formulated according to a certain rule, so that the computer device may quickly obtain, from the front-end code file, each interface calling information included in the front-end information, and obtain, by analyzing an association relationship between each interface calling information, association information between each interface calling information of the front end. In the above-described lexical and grammatical analysis, any conventional lexical and grammatical analysis tool may be used, and the present invention is not limited thereto. For example, common analytical tools are Flex and Bison.
S103, analyzing the back-end code to obtain back-end information; the back-end information includes the association information between the interface realization information of the back-end.
The interface implementation information comprises any one of a backend interface name, a class name associated with the backend interface name, a method name contained in the class name and a parameter list contained in the method name. The back-end information includes different interface implementation information of the back end.
Specifically, when the computer device reads the back-end codes, lexical and grammatical analysis can be further performed on each line of read back-end codes, the back-end codes are analyzed into a back-end code file formulated according to a certain rule, so that the computer device can quickly acquire interface implementation information contained in the back-end information from the back-end code file, and association information among the interface implementation information of the back-end is obtained by analyzing association relations among the interface implementation information. In the above-described lexical and syntactic analysis, the same lexical and syntactic analysis tools as in the front-end analysis may be used.
And S104, generating a data interaction relation between the front end and the back end according to the front end information and the back end information.
Specifically, when the computer device obtains the front-end information and the back-end information based on the foregoing steps, the association information between the interface calling information included in the front-end information and the association information between the interface implementation information included in the back-end information may be further analyzed to obtain an association relationship between the front-end calling interface and the back-end called interface, and further generate a data interaction relationship between the front-end and the back-end. For example, if the association information between the interface call information included in the front-end information is "a front-end method calls a back-end interface a with ajax and transfers a plurality of parameters", and the association information between the interface realization information included in the back-end information is "a back-end interface will be processed by a method a of a class a and the method includes a plurality of parameters", by analyzing the two pieces of association information, the data interaction relationship between the front end and the back end can be obtained as "a method a front-end method calls a back-end interface a".
In the method for generating the data interaction relationship, the front-end code and the back-end code of the target application are obtained and analyzed to obtain the front-end information comprising the association information between the interface calling information of the front end, the back-end code is analyzed to obtain the back-end information comprising the association information between the interface realizing information of the back end, and then the data interaction relationship between the front end and the back end is generated according to the front-end information and the back-end information. Compared with the traditional method for manually generating the data interaction relationship between the front end and the rear end, the method saves time and energy of an application developer for manually combing the data interaction relationship between the front end and the rear end, further improves the application development efficiency of the application developer, and simultaneously greatly reduces the labor cost.
In an embodiment, a specific implementation manner of the foregoing S102 is provided, and as shown in fig. 3, the foregoing S102 "parsing the front-end code to obtain the front-end information" includes:
s201, performing lexical analysis on the front-end codes to obtain first front-end analysis codes, wherein the first front-end analysis codes comprise first identifiers used for replacing keywords in the front-end codes.
The first identifier may be represented by a single form such as a letter, a symbol, a number, or a combination of a letter, a symbol, a number, and the like, which is not limited herein. Specifically, the computer device may perform lexical analysis on the keyword, each type of symbol, the custom sentence part, and the unnecessary analysis sentence part in each line of the sentence in the front-end code by using an existing lexical analysis tool (e.g., flex tool), and generate an analyzed first front-end analysis code, so that the first front-end analysis code includes a first identifier for replacing each keyword in the front-end code, a first identifier for replacing each type of symbol, a first identifier for replacing the custom sentence, and a first identifier for replacing the unnecessary analysis sentence, so that the computer device may identify the semantics of each sentence in the first front-end analysis code according to each type of first identifier.
S202, syntax analysis is carried out on the first front-end analysis code to obtain front-end information.
Specifically, the computer device may perform syntax parsing on each line of statements in the first front-end parsing code by using an existing syntax parsing tool (for example, a Bison tool), extract interface calling information of the front end from the syntax parsing tool, further obtain association information between the interface calling information of the front end by analyzing an association relationship between the interface calling information of the front end, that is, front-end information, and store the front-end information in a memory, so that the front-end information is used in subsequent query.
In an embodiment, the present application further provides a specific implementation manner of the foregoing S201, and as shown in fig. 4, the foregoing S201 "performs lexical analysis on the front-end code to obtain a first front-end analysis code", including:
s301, performing lexical analysis on the front-end code, and identifying a keyword in the front-end code to obtain a corresponding first identifier.
Specifically, in the process of lexical analysis of the front-end code, the computer device identifies keywords in the front-end code to obtain a first identifier corresponding to each keyword. For example, the front-end code uses the ajax common calling mode, and the code for calling the interface is as follows:
Figure BDA0002687157490000081
correspondingly, in the process of lexical analysis of the front-end code, the computer device identifies keywords (also called Token) therein, and obtains a first identifier corresponding to each keyword:
FUNC function
AJAX $.ajax
TYPE type
URL url
DATA data
BASE(base)
wherein, function, AJAX, TYPE, URL, DATA and BASE are each keyword in the front-end code, and FUNC, AJAX, TYPE, URL, DATA and BASE are first identifiers corresponding to the keywords.
S302, the first front-end analysis code is obtained by using the key words in the substitute front-end code corresponding to the first identifier.
When the computer device obtains the first identifier, the computer device further uses the keywords in the substitute front-end code corresponding to the first identifier. Meanwhile, when the computer device identifies the keywords in the front-end code, other types of information in the front-end code, such as various symbols, a custom sentence part, and an unnecessary analysis part, need to be identified. For example, each kind of symbol includes "+", ": and"; ", brackets" () "," { } ", double quotation marks and the like. The custom statement part comprises a custom part such as an interface name and a method name in the calling interface code, and a part which does not need to be analyzed, and the custom statement part can be classified into a character STRING, namely, represented by a first identifier "STRING". After the computer device identifies the keywords in the front-end code and other types of information, the calling interface code can be abstracted into the following code:
Figure BDA0002687157490000091
the abstracted code is a first front-end analysis code obtained after the computer device uses key words, related various symbols, a user-defined statement part and a statement part in the substitute front-end code corresponding to the first identifier. The code presentation section is only an example, and does not limit the analysis method of the present embodiment.
In an embodiment, the present application further provides a specific implementation manner of the foregoing S202, and as shown in fig. 5, the foregoing S202 "performs syntax parsing on the first front-end parsing code to obtain front-end information", including:
s401, matching the first preset grammar rule, and performing grammar parsing on the first front-end parsing code to obtain a second front-end parsing code, wherein the second front-end parsing code comprises interface calling information of the front end.
The first preset grammar rule is a grammar rule for describing each statement in the front-end code, and the first preset grammar rule is predetermined by computer equipment. Specifically, in the process of parsing the front-end code, the computer device parses the statement syntax of each line in the first front-end parsing code according to a first preset syntax rule, and generates a second front-end parsing code including interface calling information of the front end. For example, by performing syntax parsing on the first front-end parsing code used in the above step S302, the following second front-end parsing codes can be obtained:
PARAM"STRING":"STRING"
PARAM_LIST PARAM_LIST,PARAM|PARAM
FUNC_BODY FUNC STRING(){AJAX_BODY}
AJAX_BODY AJAX({URL_DEF,DATA_DEF})
URL_DEF URL:"STRING"
DATA_DEF DATA:PARAM_LIST
FUNC _ BODY in the second front-end analysis code represents a method defined by the front end; AJAX _ BODY represents AJAX calling performed in a method defined by a front end; the interface address of the ajax request is recorded in URL _ DEF.
S402, analyzing the second front-end analysis code, and extracting the interface calling information of the front end from the second front-end analysis code.
When the computer equipment obtains the second front-end analysis code, the obtained second front-end analysis code can be analyzed, and the interface calling information of the front end is extracted from the second front-end analysis code. For example, based on the second front-end analysis code exemplified in S401, each interface call information that can be extracted from the second front-end analysis code is: the method name, the ajax called by the method name, the interface name accessed by the ajax, and the parameter list accessed by the ajax.
And S403, substituting the calling information of each interface into a preset first driving function to calculate to obtain front-end information.
The first driving function is used for outputting the associated information among the interface calling information according to the interface calling information of the front end. For example, the computer device obtains the call information of each interface as follows: when the method name, the ajax called by the method name, the interface name accessed by the ajax and the parameter list accessed by the ajax are listed, the interface calling information is taken as parameters to be transmitted to a first driving function, and the first driving function can output the following associated information among the interface calling information:
method name Call- > ajax
ajax Access- > interface name
ajax contains- > parameter List
Obviously, the associated information can be obtained as follows: "some front-end method calls some back-end interface with ajax, passing some parameters".
In the above embodiment, the second front-end analysis code described by using the first preset syntax rule is obtained by performing lexical and syntactic analysis on the front-end code, and then each interface call information of the front end can be obtained by analyzing the second front-end analysis code, and then the association information between each interface call information of the front end can be obtained by calling the first drive function. According to the method, the correlation information among the calling information of each interface of the front end can be automatically acquired by scanning the front end code for analysis, and front end information support and basis are provided for later analysis of the data interaction relationship between the front end and the back end.
In an embodiment, a specific implementation manner of the foregoing S103 is provided, and as shown in fig. 6, the foregoing S103 "parsing the backend code to obtain the backend information" includes:
s501, performing lexical analysis on the rear-end codes to obtain first rear-end analysis codes; the first front-end parsing code includes a second identifier for replacing a keyword in the front-end code.
The second identifier may be represented by using a single form of letter, symbol, number, or the like, or may be represented by using a combination of letters, symbols, numbers, or the like, which is not limited herein. Specifically, the computer device may perform lexical analysis on the keyword, each type of symbol, the custom sentence part, and the unnecessary analysis sentence part in each line of the sentence in the backend code by using an existing lexical analysis tool (e.g., flex tool), to generate an analyzed first backend analysis code, so that the first backend analysis code includes a second identifier for replacing each keyword in the backend code, a second identifier for replacing each type of symbol, a second identifier for replacing the custom sentence, and a second identifier for replacing an unnecessary analysis sentence, so that the computer device may identify the semantics of each sentence in the first backend analysis code according to each type of second identifier.
S502, syntax analysis is carried out on the first back-end analysis code, and back-end information is obtained.
Specifically, the computer device may perform syntax parsing on each line of statements in the first back-end parsing code by using an existing lexical parsing tool (e.g., a Bison tool), extract back-end interface implementation information from the syntax parsing tool, further obtain association information between the back-end interface implementation information by analyzing an association relationship between the back-end interface implementation information, that is, back-end information, and store the back-end information in a memory, so that the back-end information is used in a later query.
In an embodiment, the present application further provides a specific implementation manner of the foregoing S501, and as shown in fig. 7, the foregoing S501 "performs lexical analysis on the backend code to obtain a first backend analysis code", including:
s601, performing lexical analysis on the rear-end code, and identifying a keyword in the rear-end code to obtain a corresponding second identifier.
Specifically, in the process of lexical analysis of the back-end code, the computer device identifies the keywords in the back-end code to obtain the second identifiers corresponding to the keywords. For example, the code implemented by the interface in the backend code is as follows:
Figure BDA0002687157490000121
correspondingly, in the process of lexical analysis of the back-end code, the computer device identifies keywords (also called Token) therein, and obtains a second identifier corresponding to each keyword:
RQUEST @RequestMapping
PUBLIC public
private
protect
CLASS class
VALUE value
METHOD method
wherein @ RequestMapping, PUBLIC, private, protect, CLASS, VALUE, and METHOD are keywords in the back-end code, and RQUEST, PUBLIC, CLASS, VALUE, and METHOD are second identifiers corresponding to the keywords.
S602, the keyword in the substitute back-end code corresponding to the second identifier is used to obtain a first back-end analysis code.
When the computer device obtains the second identifier, the keywords in the substitute backend code corresponding to the second identifier are further used. Meanwhile, when the computer device identifies the keywords in the back-end code, other types of information in the back-end code, such as various symbols, custom statement parts, unnecessary analysis statement parts, are also required to be identified. Taking the interface implementation codes listed in S601 as an example for explanation, for example, each type of symbol includes "+", ": and"; ", brackets" () "," { } ", double quotation marks and the like. The custom sentence part comprises the interface name, the method name, the class name, the return type and other custom parts in the interface implementation code, and parts which do not need to be analyzed, and the custom sentence parts can be classified into character STRINGs, namely represented by a second identifier "STRING". After the computer device identifies the keywords in the back-end code and other types of information, the interface implementation code may be abstracted as the following code:
Figure BDA0002687157490000131
the abstracted codes are first back-end analysis codes obtained after the computer equipment uses various symbols related to key words in the substitute back-end codes corresponding to the second identifiers, the self-defined statement part and the statement part do not need to be analyzed. The code presenting part is only an example, and does not limit the analysis method of the embodiment.
In an embodiment, the present application further provides a specific implementation manner of the foregoing S502, and as shown in fig. 8, the foregoing S502 "performing syntax parsing on the first backend parsing code to obtain a second backend parsing code" includes:
and S701, matching a second preset grammar rule, and performing grammar parsing on the first back-end parsing code to obtain a second back-end parsing code, wherein the second back-end parsing code comprises each interface implementation information of the back end.
And the second preset grammar rule is a grammar rule for describing each statement in the back-end code, and the second preset grammar rule is predetermined by the computer equipment. Specifically, in the process of parsing the back-end code, the computer device parses the statement syntax of each line in the first back-end parsing code according to a second preset syntax rule, and generates a second back-end parsing code including the interface implementation information of the back end. For example, by performing syntax parsing on the first backend parsing code used in the above step S602, the following second backend parsing codes can be obtained:
Figure BDA0002687157490000141
the PARAM and PARAM _ LIST in the second back-end analysis code represent parameters and parameter LISTs, where recursive description and or operation are used; MAP _ CLASS and MAP _ METHOD respectively represent annotation CLASS and annotation METHOD; CLASS _ BODY and METHOD _ BODY respectively represent a CLASS BODY and a function BODY; CLASS _ BODY includes multiple METHOD _ BODY, which includes the service implementation and result.
S702, analyzing the second back-end analysis code, and extracting back-end interface implementation information from the second back-end analysis code; the second back-end analysis code comprises back-end interface implementation information.
When the computer equipment obtains the second back-end analysis code, the second back-end analysis code can be analyzed, and the back-end realization information of each interface is extracted from the second back-end analysis code. For example, based on the second backend parsing code exemplified in S701, the interface implementation information may be extracted as follows: the interface name, the class name associated with the interface name, the method name associated with the class name, and the parameter list associated with the method name.
And S703, substituting the implementation information of each interface into a preset second driving function for calculation to obtain back-end information.
And the second driving function is used for outputting the associated information among the interface realization information according to the interface realization information at the rear end. For example, the computer device obtains the implementation information of each interface as follows: when the interface name, the class name associated with the interface name, the method name associated with the class name, and the parameter list associated with the method name are used, the interface implementation information is transmitted to the second driving function as a parameter, and the second driving function can output the following association information among the interface implementation information:
interface name association- > class name
Interface name association- > method name
Class name contains- > method name
Method name contains- > parameter list
Obviously, the associated information can be obtained as follows: "a certain interface will be handled by a certain method of a certain class, the method containing several parameters".
In the above embodiment, the second backend analysis code described by using the second preset syntax rule is obtained by performing lexical and syntactic analysis on the backend code, and then by analyzing the second backend analysis code, the interface implementation information of the backend can be obtained therefrom, and then the association information between the interface implementation information of the backend can be obtained by calling the second drive function. According to the method, the correlation information among the realization information of each interface at the back end can be automatically acquired by scanning the back end code for analysis, and back end information support and basis are provided for the later analysis of the data interaction relationship between the front end and the back end.
In an embodiment, when the front-end information and the back-end information are obtained by the method described in the embodiments of fig. 3 to 8, a data interaction relationship between the front end and the back end may be obtained, for example, by applying the example in the embodiment, it is assumed that the front-end information obtained by analyzing the front-end code is: "a certain front-end method calls a certain back-end interface by ajax and transfers a plurality of parameters", and the back-end information obtained by analyzing the back-end code is as follows: "a certain interface will be processed by a certain method of a certain class, the method includes several parameters", then by analyzing these two pieces of information, information representing the data interaction relationship between the front end and the back end can be obtained: "A certain front-end method invokes a certain back-end method".
In practical application, there is also a data interaction relationship, that is, the front end ajax is invoked further after being successfully invoked, so that the data interaction relationship is also presented to construct a data interaction relationship between the front end and the back end, and based on the above analysis, when the calling information of each interface at the front end includes the calling return information of each interface successfully, the front end information includes the cascade calling relationship between each interface when each interface is invoked. In this application scenario, the present application further provides a method for generating a data interaction relationship, as shown in fig. 9, on the basis of the foregoing embodiment, the method for generating a data interaction relationship further includes the following steps:
s801, performing lexical analysis on the front-end code, and identifying a newly added keyword in the front-end code to obtain a corresponding third identifier; the newly added keywords indicate that the front end calls the interface successfully.
The newly added keywords are newly added keywords which need to be identified. For example, the newly added keyword may be: success, the corresponding third identifier is: SUCCESS.
Specifically, the present embodiment relates to a lexical analysis process for front-end codes, and a specific analysis method is consistent with the method described in step S301, and for details, reference is made to the foregoing description, which is not repeated herein.
S802, replacing the newly added keywords in the front-end code by using the third identifier to obtain a third front-end analysis code.
The present embodiment relates to a lexical analysis process for a front-end code, a specific analysis method is consistent with the method described in the foregoing step S302, and for details, reference is made to the foregoing description, which is not repeated herein.
S803, matching a preset newly-added grammar rule, and performing grammar parsing on the third front-end parsing code to obtain a fourth front-end parsing code; presetting new grammar rules including describing grammar rules that the front end calls the interface successfully and continues to call the next interface; the fourth front-end analysis code comprises return information of successful calling of each interface.
The new grammar rule is preset to describe the grammar rule of the statement of the next interface, wherein the grammar rule represents that the front end calls the interface successfully in the front end code. For example, the fourth front-end parsing code is:
RET_AJAX SUCCESS FUNCTION(STRING){AJAX_BODY}
the fourth front-end analysis code is obtained by analyzing the third front-end analysis code according to a preset new grammar rule, wherein RET _ AJAX indicates that another AJAX request is continuously called after the AJAX request is called and returns to be successful.
And S804, analyzing the fourth front-end analysis code, and extracting the return information of successful calling of each interface from the fourth front-end analysis code.
When the computer equipment obtains the fourth front-end analysis code, the fourth front-end analysis code can be analyzed, and the interface calling information of the front end is extracted from the fourth front-end analysis code. For example, based on the fourth front-end analysis code exemplified in S803, the successful return information of each interface call that can be extracted from the fourth front-end analysis code is: the ajax request is successfully called, and the ajax request continues to call another ajax after being successfully called.
And S805, substituting the returned information of each interface calling success into a preset third driving function for calculation to obtain front-end information.
The present embodiment relates to a process of successfully returning information output front-end information according to each interface call by using a third driver function, and the method used is substantially the same as the foregoing S403, and please refer to the foregoing description for details, which is not described redundantly here. For example, based on the successful return information of each interface call obtained in S804, after the third driver function is calculated, the following information may be obtained: "after a certain ajax call returns successfully, the next interface is called continuously".
In the above embodiment, by adding the newly added keyword to the front-end code and the corresponding preset newly added grammar rule, the successful call return information of each interface can be obtained from the fourth analyzed code after analysis, and then the cascade call relationship between the interfaces can be obtained by calling the third drive function when the call of each interface included in the front-end information is obtained, so that complete interactive data is provided for analyzing the data interaction relationship between the front end and the back end.
In one embodiment, in order to facilitate a user to view a data interaction relationship between a front end and a back end of a target application, which is automatically generated by a computer device according to the method described in the above embodiment, the method for generating a data interaction relationship provided by the present application further includes a method for graphically displaying the data interaction relationship, where the method includes: and drawing the data interaction relationship between the front end and the back end on the front end page by using a preset drawing tool to obtain a relationship diagram representing the data interaction relationship between the front end and the back end, wherein the relationship diagram can be a timing diagram or other types of diagrams, and the relationship diagram is not limited herein. For example, the computer device may obtain the timing chart shown in fig. 10 after drawing the data interaction relationship. The application developer can clearly know the data interaction relationship between the front end and the back end through the relationship diagram displayed on the front end page, so that the application developer can conveniently test, and the development efficiency of the application developer in developing the application program is improved.
In one embodiment, an implementation manner of the above S104 is provided, and as shown in fig. 11, the method includes:
s1001 extracts overlapping information between the front-end information and the back-end information.
Specifically, when the computer device obtains the front-end information and the back-end information, the overlapping information between the front-end information and the back-end information can be further determined by analyzing various interface calling information included in the front-end information and various interface implementation information included in the back-end information. For example, the association information between the interface call information included in the front-end information is "a front-end method calls a back-end interface a with ajax, and passes a plurality of parameters", and the association information between the interface implementation information included in the back-end information is "a back-end interface a will be processed by a method a of class a, and the method includes a plurality of parameters", and then the overlapping information between the front-end information and the back-end information in this example is "a back-end interface a". Optionally, when the overlap information between the front-end information and the back-end information is specifically determined, the overlap information may be determined by calculating the degree of overlap between the front-end information and the back-end information, for example, calculating the degree of overlap between each of the front-end information and the back-end information, and then determining that the information whose degree of overlap is greater than a preset threshold value of degree of overlap is the overlap information. Optionally, the computer device may also identify overlapping information between the front-end information and the back-end information by using a machine learning algorithm, which is not limited herein.
S1002, interface calling information associated with the overlapped information in the front-end information is determined.
For example, the related information among the interface calling information included in the front-end information is that "a front-end method calls a back-end interface a with ajax, and transfers a plurality of parameters", if the overlapped information in the front-end information is the back-end interface a, the key information in the calling relationship with the back-end interface a is the front-end method a, and the front-end method a is the interface calling information in forward association with the back-end interface a.
Specifically, after the computer device determines the overlapping information, the interface calling information associated with the overlapping information in the forward direction can be determined by analyzing the association relationship between the interface calling information included in the front-end information.
And S1003, determining interface implementation information which is backward associated with the overlapped information in the back-end information.
For example, the association information among the interface implementation information included in the backend information is that "a backend interface will be processed by a method a of class a, the method includes a plurality of parameters", if the overlapping information in the backend information is the a backend interface, the key information in the implementation relationship with the a backend interface is the method a, and the method a is the interface implementation information in backward association with the a backend interface.
Specifically, after the computer device determines the overlapping information, the interface implementation information backward associated with the overlapping information may be determined by analyzing the association relationship between the interface implementation information included in the back-end information.
S1004, the overlapping information, the interface calling information associated with the overlapping information in the forward direction and the interface implementation information associated with the overlapping information in the backward direction are logically connected to generate a data interaction relationship between the front end and the back end.
Specifically, after the computer device determines the overlay information, the interface call information associated with the overlay information in the forward direction, and the interface implementation information associated with the overlay information in the backward direction, the information may be logically connected according to the association relationship between the information, so as to generate the data interaction relationship between the front end and the back end.
The method realizes the process of generating the data interaction relationship between the front end and the back end according to the front end information and the back end information, and the process can generate the data interaction relationship between the front end and the back end only by analyzing the incidence relationship between the overlapping information and other information according to the overlapping information between the front end information and the back end information.
With all the above embodiments in general, the following describes, by way of example, a method for generating a data interaction relationship according to the present application, as shown in fig. 12, the method includes:
s901, a front end code of the target application is obtained.
S902, performing lexical analysis on the front-end code, and identifying keywords and newly added keywords in the front-end code to obtain a corresponding first identifier and a corresponding third identifier.
And S903, obtaining a first front-end analysis code by using the key words in the substitute front-end code corresponding to the first identifier and the newly added key words in the substitute front-end code corresponding to the third identifier.
And S904, matching the first preset grammar rule with the preset newly added grammar rule, and carrying out grammar analysis on the first front-end analysis code to obtain a second front-end analysis code which comprises calling information of each interface of the front end and successfully returned information of each interface.
S905, the second front-end analysis code is analyzed, and the interface calling information of the front end and the returning information of the interface calling success are extracted from the second front-end analysis code.
And S906, substituting the calling information of each interface into a preset first driving function, and substituting the successfully called return information of each interface into a preset third driving function to calculate so as to obtain front-end information.
S907, acquiring the back-end code of the target application.
And S908, performing lexical analysis on the back-end code, and identifying keywords in the back-end code to obtain a corresponding second identifier.
S909, the first backend analysis code is obtained by using the keyword in the substitute backend code corresponding to the second identifier.
S910, matching a second preset grammar rule, and performing grammar parsing on the first back-end parsing code to obtain a second back-end parsing code.
S911, analyzing the second back-end analysis code, and extracting back-end interface implementation information from the second back-end analysis code; the second back-end analysis code comprises back-end interface implementation information.
And S912, substituting the implementation information of each interface into a preset second driving function for calculation to obtain back-end information.
And S913, generating a data interaction relationship between the front end and the back end according to the front end information and the back end information.
And S914, drawing the data interaction relationship between the front end and the back end on the front end page by using a drawing tool.
For the description of the method in each step in this embodiment, please refer to the foregoing content, which is not repeated herein.
It should be understood that although the various steps in the flow charts of fig. 2-12 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least some of the steps in fig. 2-12 may include multiple steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, which are not necessarily performed in sequence, but may be performed in turn or alternately with other steps or at least some of the other steps.
In one embodiment, as shown in fig. 13, there is provided a data interaction relationship generation apparatus, including: an obtaining module 11, a first analyzing module 12, a second analyzing module 13, and a generating module 14, wherein:
an obtaining module 11, configured to obtain a front-end code and a back-end code of a target application;
the first analysis module 12 is configured to analyze the front-end code to obtain front-end information; the front-end information comprises correlation information among interface calling information of the front end;
a second parsing module 13, configured to parse the backend code to obtain backend information; the back-end information comprises the correlation information among the interface realization information of the back end;
and a generating module 14, configured to generate a data interaction relationship between the front end and the back end according to the front end information and the back end information.
For specific limitations of the data interaction relationship generation device, reference may be made to the above limitations on the data interaction relationship generation method, which is not described herein again. The modules in the data interaction relationship generation device can be wholly or partially realized by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent of a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, a computer device is provided, comprising a memory and a processor, the memory having a computer program stored therein, the processor implementing the following steps when executing the computer program:
acquiring a front-end code and a back-end code of a target application;
analyzing the front-end code to obtain front-end information; the front-end information comprises correlation information among interface calling information of the front end;
analyzing the back-end code to obtain back-end information; the back-end information comprises the correlation information among the interface realization information of the back end;
and generating a data interaction relation between the front end and the back end according to the front end information and the back end information.
The implementation principle and technical effect of the computer device provided by the above embodiment are similar to those of the above method embodiment, and are not described herein again.
In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored which, when executed by a processor, performs the steps of:
acquiring a front-end code and a back-end code of a target application;
analyzing the front-end code to obtain front-end information; the front-end information comprises correlation information among all interface calling information of the front end;
analyzing the back-end code to obtain back-end information; the back-end information comprises the correlation information among the interface realization information of the back end;
and generating a data interaction relation between the front end and the back end according to the front end information and the back end information.
The implementation principle and technical effect of the computer-readable storage medium provided by the above embodiments are similar to those of the above method embodiments, and are not described herein again.
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, database or other medium used in the embodiments provided herein can include at least one of non-volatile and volatile memory. Non-volatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical Memory, or the like. Volatile Memory can include Random Access Memory (RAM) or external cache Memory. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM), among others.
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, and these are all within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.

Claims (10)

1. A method for generating a data interaction relationship is characterized by comprising the following steps:
acquiring a front-end code and a back-end code of a target application; the target application is a Web application; the Web application is divided into a front-end application and a back-end service, the back-end service provides service and opens an interface, and the front-end application calls the back-end service interface to realize various functions;
performing lexical analysis on the front-end codes to obtain first front-end analysis codes; the first front-end analysis code comprises a first identifier used for replacing a keyword in the front-end code;
matching a first preset grammar rule, and performing grammar parsing on the first front-end parsing code to obtain a second front-end parsing code; the second front-end analysis code comprises calling information of each interface of the front end;
analyzing the second front-end analysis code, and extracting each interface calling information of the front end from the second front-end analysis code;
substituting the calling information of each interface into a preset first driving function for calculation to obtain front-end information; the front-end information comprises correlation information among interface calling information of the front end;
analyzing the back-end code to obtain back-end information; the back-end information comprises the correlation information among the interface realization information of the back end;
extracting overlapped information between the front-end information and the back-end information;
determining interface calling information forward associated with the overlapped information in the front-end information, and determining interface implementation information backward associated with the overlapped information in the back-end information;
and logically connecting the overlapping information, interface calling information forward associated with the overlapping information and interface implementation information backward associated with the overlapping information to generate a data interaction relationship between the front end and the back end.
2. The method of claim 1, wherein the lexical parsing the front-end code to obtain a first front-end parsed code comprises:
performing lexical analysis on the front-end code, and identifying a keyword in the front-end code to obtain a corresponding first identifier;
and replacing the key words in the front-end code by using the first identifier correspondingly to obtain the first front-end analysis code.
3. The method of claim 1, wherein the parsing the backend code to obtain backend information comprises:
performing lexical analysis on the rear-end codes to obtain first rear-end analysis codes; the first back-end analysis code comprises a second identifier used for replacing a keyword in the back-end code;
and carrying out syntax analysis on the first back-end analysis code to obtain the back-end information.
4. The method of claim 3, wherein the lexical parsing the backend code to obtain a first backend parsed code comprises:
performing lexical analysis on the rear-end code, and identifying a keyword in the rear-end code to obtain a corresponding second identifier;
and replacing the key words in the back-end code by using the second identifier correspondingly to obtain the first back-end analysis code.
5. The method of claim 3, wherein parsing the first backend parsing code to obtain the backend information comprises:
matching a second preset grammar rule, and carrying out grammar analysis on the first back-end analysis code to obtain a second back-end analysis code; the second back-end analysis code comprises the realization information of each interface of the back end;
analyzing the second back-end analysis code, and extracting each interface implementation information of the back end from the second back-end analysis code;
and substituting the realization information of each interface into a preset second driving function for calculation to obtain the back-end information.
6. The method according to claim 1, wherein each interface call information of the front end includes successful return information of each interface call, and the front end information includes a cascade call relationship between interfaces when each interface is called, the method further comprising:
performing lexical analysis on the front-end code, and identifying a newly added keyword in the front-end code to obtain a corresponding third identifier; the newly added keywords represent that the front-end calling interface is successful;
replacing the newly added keywords in the front-end code with the third identifier correspondingly to obtain a third front-end analysis code;
matching a preset newly added grammar rule, and carrying out grammar analysis on the third front-end analysis code to obtain a fourth front-end analysis code; the preset newly-added grammar rule comprises a grammar rule which describes that the front end calls the interface successfully and continues to call the next interface; the fourth front-end analysis code comprises return information of calling success of each interface;
analyzing the fourth front-end analysis code, and extracting return information of each interface calling success from the fourth front-end analysis code;
and substituting the successfully called return information of each interface into a preset third driving function for calculation to obtain the front-end information.
7. An apparatus for generating data interaction relationship, the apparatus comprising:
the acquisition module is used for acquiring a front-end code and a back-end code of the target application; the target application is a Web application; the Web application is divided into a front-end application and a back-end service, the back-end service provides service and opens an interface, and the front-end application calls the back-end service interface to realize various functions;
the first analysis module is used for performing lexical analysis on the front-end codes to obtain first front-end analysis codes; the first front-end analysis code comprises a first identifier used for replacing a keyword in the front-end code; matching a first preset grammar rule, and performing grammar parsing on the first front-end parsing code to obtain a second front-end parsing code; the second front-end analysis code comprises calling information of each interface of the front end; analyzing the second front-end analysis code, and extracting each interface calling information of the front end from the second front-end analysis code; substituting the calling information of each interface into a preset first driving function for calculation to obtain front-end information; the front-end information comprises correlation information among interface calling information of the front end;
the second analysis module is used for analyzing the back-end code to obtain back-end information; the back-end information comprises the correlation information among the interface realization information of the back end;
the generating module is used for extracting the overlapping information between the front-end information and the back-end information; determining interface calling information associated with the overlapped information in the front-end information in a forward direction, and determining interface implementation information associated with the overlapped information in a backward direction in the back-end information; and logically connecting the overlapping information, interface calling information forward associated with the overlapping information and interface implementation information backward associated with the overlapping information to generate a data interaction relationship between the front end and the back end.
8. The apparatus of claim 7, wherein the first parsing module is specifically configured to:
performing lexical analysis on the front-end code, and identifying a keyword in the front-end code to obtain a corresponding first identifier;
and replacing the key words in the front-end code by using the first identifier correspondingly to obtain the first front-end analysis code.
9. A computer device comprising a memory and a processor, the memory storing a computer program, wherein the processor implements the steps of the method of any one of claims 1 to 6 when executing the computer program.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 6.
CN202010979865.2A 2020-09-17 2020-09-17 Data interaction relation generation method, computer equipment and storage medium Active CN112181370B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010979865.2A CN112181370B (en) 2020-09-17 2020-09-17 Data interaction relation generation method, computer equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010979865.2A CN112181370B (en) 2020-09-17 2020-09-17 Data interaction relation generation method, computer equipment and storage medium

Publications (2)

Publication Number Publication Date
CN112181370A CN112181370A (en) 2021-01-05
CN112181370B true CN112181370B (en) 2023-02-28

Family

ID=73921523

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010979865.2A Active CN112181370B (en) 2020-09-17 2020-09-17 Data interaction relation generation method, computer equipment and storage medium

Country Status (1)

Country Link
CN (1) CN112181370B (en)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106547520A (en) * 2015-09-16 2017-03-29 腾讯科技（深圳）有限公司 A kind of code path analysis method and device
CN109375922A (en) * 2018-09-26 2019-02-22 深圳壹账通智能科技有限公司 A kind of automatic generation method and terminal device of interface document
CN110286966A (en) * 2019-05-21 2019-09-27 上海烜翊科技有限公司 The interconnection method and device of multiple subsystems in embedded system
CN110333898A (en) * 2019-05-27 2019-10-15 北京达佳互联信息技术有限公司 A kind of code relation generation method, device, electronic equipment and storage medium
CN110515608A (en) * 2019-08-30 2019-11-29 网易（杭州）网络有限公司 A kind of generation method and device, electronic equipment, storage medium of interface code
CN111240653A (en) * 2019-12-31 2020-06-05 瑞庭网络技术（上海）有限公司 Interface document generation method and device and readable storage medium

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107291743B (en) * 2016-03-31 2020-10-16 北京星选科技有限公司 Data calling method and device
JP6926841B2 (en) * 2017-08-31 2021-08-25 富士電機株式会社 Control system, development support device, and control method
CN108462750A (en) * 2018-03-22 2018-08-28 平安好房（上海）电子商务有限公司 Distribution calls method for tracing, operation system, monitoring system and storage medium
US11151018B2 (en) * 2018-04-13 2021-10-19 Baidu Usa Llc Method and apparatus for testing a code file
CN110908710B (en) * 2019-11-19 2023-08-29 天津大学 Web front-end code dependency visualization method
CN111488573A (en) * 2020-03-25 2020-08-04 腾讯科技（深圳）有限公司 Link library detection method and device, electronic equipment and computer readable storage medium

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106547520A (en) * 2015-09-16 2017-03-29 腾讯科技（深圳）有限公司 A kind of code path analysis method and device
CN109375922A (en) * 2018-09-26 2019-02-22 深圳壹账通智能科技有限公司 A kind of automatic generation method and terminal device of interface document
CN110286966A (en) * 2019-05-21 2019-09-27 上海烜翊科技有限公司 The interconnection method and device of multiple subsystems in embedded system
CN110333898A (en) * 2019-05-27 2019-10-15 北京达佳互联信息技术有限公司 A kind of code relation generation method, device, electronic equipment and storage medium
CN110515608A (en) * 2019-08-30 2019-11-29 网易（杭州）网络有限公司 A kind of generation method and device, electronic equipment, storage medium of interface code
CN111240653A (en) * 2019-12-31 2020-06-05 瑞庭网络技术（上海）有限公司 Interface document generation method and device and readable storage medium

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
基于Http Token认证前后端交互流程;TheoXiong;《https://blog.csdn.net/m0_37859660/article/details/82716162》;20180915;1 *

Also Published As

Publication number Publication date
CN112181370A (en) 2021-01-05

Similar Documents

Publication Publication Date Title
US11669579B2 (en) Method and apparatus for providing search results
CN111176996A (en) Test case generation method and device, computer equipment and storage medium
US9984050B2 (en) Ground truth collection via browser for passage-question pairings
CN107391561B (en) Advertisement processing method in content source page, server and computer readable medium
CN111459977B (en) Conversion of natural language queries
CN112651236B (en) Method and device for extracting text information, computer equipment and storage medium
CN113051514A (en) Element positioning method and device, electronic equipment and storage medium
CN115599386A (en) Code generation method, device, equipment and storage medium
CN104699836A (en) Multi-keyword search prompting method and multi-keyword search prompting device
CN102193789B (en) Method and equipment for realizing configurable skip link
CN113760894A (en) Data calling method and device, electronic equipment and storage medium
CN104778232A (en) Searching result optimizing method and device based on long query
CN112181370B (en) Data interaction relation generation method, computer equipment and storage medium
CN116521621A (en) Data processing method and device, electronic equipment and storage medium
CN116225956A (en) Automated testing method, apparatus, computer device and storage medium
US11250084B2 (en) Method and system for generating content from search results rendered by a search engine
CN114579461A (en) Browser compatibility detection method and related equipment
CN111400623B (en) Method and device for searching information
CN109243249B (en) Method and device for generating evaluation program
CN111753548A (en) Information acquisition method and device, computer storage medium and electronic equipment
US20240104297A1 (en) Analysis of spreadsheet table in response to user input
CN112732254B (en) Webpage development method, webpage development device, computer equipment and storage medium
CN110347818B (en) Word segmentation statistical method and device, electronic equipment and computer readable storage medium
CN108932326B (en) Instance extension method, device, equipment and medium
CN116185420A (en) Source code language conversion method and device

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
GR01 Patent grant
GR01 Patent grant