CN110347380B - Front-end and back-end development method and device - Google Patents

Abstract

The embodiment of the application provides a front-end and back-end development method and device, wherein the method is applied to a first client, and the first client runs on the device of a front-end developer and comprises the following steps: acquiring a client list stored by a server, wherein the client list comprises a client which establishes connection with the server, and the server runs on the server; determining a second client according to the client list, wherein the second client runs on equipment of a background developer; the server sends the junction pair debugging request message to the second client, so that the second client sends the junction pair debugging request message to the background interface project, and sends the obtained interface return message to the server, and the server returns the first client, so that front and rear end developers can conduct junction pair debugging at any time before code integration testing, the situation that the interface developer has divergence to interface development is reduced, interface problems can be found in time, and the front and rear development efficiency is improved.

Description

Front-end and back-end development methods and equipment

technical field

The embodiments of the present application relate to the technical field of the Internet, and in particular to a front-end and back-end development method and equipment.

Background technique

With the continuous development and progress of society, the aesthetic perception and interactive experience of Web pages have an increasingly significant impact on Internet users. The smooth rendering speed of modern browsers, the rich expressive power of Html5 and CSS3, and the flexible functions of Javascript have attracted the attention of Internet users.

At present, in order to meet users' pursuit of product experience, the complexity of front-end development has increased rapidly, and the development model of back-end development taking into account the front-end page has been eliminated, and the development model of front-end and back-end separation has evolved. The new development model enables parallel development of the front-end and the back-end, and finally combines performance and data through the restful protocol interface.

However, the parallel development of the front-end and the back-end may lead to the inconsistency of the interface development between the front-end and the back-end development engineers. This problem is not exposed until the integration test stage. It is necessary to modify the code to re-integrate the test, and the development efficiency is low.

Contents of the invention

The embodiment of the present application provides a front-end and back-end development method and equipment to overcome the problem that the existing front-end and back-end are developed in parallel, and interface problems cannot be found in time, resulting in low development efficiency.

In the first aspect, the embodiment of the present application provides a front-end and back-end development method, the method is applied to a first client, and the first client runs on a device of a front-end developer, and the method includes:

Obtain a client list stored by the server, the client list includes clients that establish connections with the server, and the server runs on the server;

Determine a second client according to the client list, and the second client runs on the device of the background developer;

Send a pairing debugging request message to the second client through the server, so that the second client sends the pairing debugging request message to the background interface project, and sends the obtained interface return message to the server, and return to the first client through the server.

In a possible design, the first client includes an interface design module, the interface design module includes interface specifications of the front end and the backend, and the server includes a packet inspection module;

The method also includes:

determining the message to be checked from the messages stored at the server;

Send the message to be checked to the message checking module, so that the message checking module judges whether the message to be checked is correct according to the interface specification, and determines that the message to be checked is wrong , determine the error location of the message to be checked according to the interface specification.

In a possible design, the interface specification includes all node names, types, length limits, required fields, enumeration values, node dependencies, and collections of the front-end and back-end interfaces described based on json syntax Node number constraints.

In a possible design, the above method also includes:

Establish a connection with the server;

sending heartbeat data to the server after a preset time interval, and judging whether the heartbeat data returned by the server is received;

If the heartbeat data returned by the server is not received, re-execute the step of establishing a connection with the server.

In the second aspect, the embodiment of the present application provides another front-end and back-end development method, the method is applied to the server, and the server runs on the server, and the method includes:

sending a client list to the first client, so that the first client determines a second client according to the client list, the client list includes clients establishing connections with the server, the second A client runs on the device of the front-end developer, and the second client runs on the device of the background developer;

receiving a pairing debugging request message sent by the first client to the second client;

sending the pairing debugging request message to the second client, so that the second client sends the pairing debugging request message to the background interface engineering, and sends the obtained interface return message to the the server side;

returning the interface return message to the first client.

In a possible design, the first client includes an interface design module, the interface design module includes interface specifications of the front end and the backend, and the server includes a packet inspection module;

The method also includes:

The message checking module receives the message to be checked sent by the first client, and the message to be checked is the message to be checked determined by the first client from the messages stored in the server;

Judging whether the message to be checked is correct according to the interface specification, and determining the error location of the message to be checked according to the interface specification when it is determined that the message to be checked is incorrect.

In a possible design, the interface specification includes all node names, types, length limits, required fields, enumeration values, node dependencies, and collections of the front-end and back-end interfaces described based on json syntax Node number constraints.

In the third aspect, the embodiment of the present application provides a front-end and back-end development device, the device is applied to the first client, and the first client runs on the device of the front-end developer, and the device includes a memory, a processor, and Computer-executable instructions stored in the memory and operable on the processor, the processor implements the following steps when executing the computer-executable instructions:

Obtain a client list stored by the server, the client list includes clients that establish connections with the server, and the server runs on the server;

Determine a second client according to the client list, and the second client runs on the device of the background developer;

Send a pairing debugging request message to the second client through the server, so that the second client sends the pairing debugging request message to the background interface project, and sends the obtained interface return message to the server, and return to the first client through the server.

In a possible design, the first client includes an interface design module, the interface design module includes interface specifications of the front end and the backend, and the server includes a packet inspection module;

When the processor executes the computer execution instructions, the following steps are also implemented:

determining the message to be checked from the messages stored at the server;

Send the message to be checked to the message checking module, so that the message checking module judges whether the message to be checked is correct according to the interface specification, and determines that the message to be checked is wrong , determine the error location of the message to be checked according to the interface specification.

In a possible design, the interface specification includes all node names, types, length limits, required fields, enumeration values, node dependencies, and collections of the front-end and back-end interfaces described based on json syntax Node number constraints.

In a possible design, when the processor executes the computer execution instructions, the following steps are also implemented:

Establish a connection with the server;

sending heartbeat data to the server after a preset time interval, and judging whether the heartbeat data returned by the server is received;

If the heartbeat data returned by the server is not received, re-execute the step of establishing a connection with the server.

In the fourth aspect, the embodiment of the present application provides another front-end and back-end development equipment. The equipment is applied to the server, and the server runs on the server. The equipment includes a memory, a processor, and a memory stored in the memory and Computer-executable instructions that can run on the processor, and the processor implements the following steps when executing the computer-executable instructions:

sending a client list to the first client, so that the first client determines a second client according to the client list, the client list includes clients establishing connections with the server, the second A client runs on the device of the front-end developer, and the second client runs on the device of the background developer;

receiving a pairing debugging request message sent by the first client to the second client;

sending the pairing debugging request message to the second client, so that the second client sends the pairing debugging request message to the background interface engineering, and sends the obtained interface return message to the the server side;

returning the interface return packet to the first client.

In a possible design, the first client includes an interface design module, the interface design module includes interface specifications of the front end and the backend, and the server includes a packet inspection module;

When the processor executes the computer execution instructions, the following steps are also implemented:

The message checking module receives the message to be checked sent by the first client, and the message to be checked is the message to be checked determined by the first client from the messages stored in the server;

Judging whether the message to be checked is correct according to the interface specification, and determining the error location of the message to be checked according to the interface specification when it is determined that the message to be checked is incorrect.

In a possible design, the interface specification includes all node names, types, length limits, required fields, enumeration values, node dependencies, and collections of the front-end and back-end interfaces described based on json syntax Node number constraints.

In the fifth aspect, the embodiment of the present application provides a computer-readable storage medium, the computer-readable storage medium stores computer-executable instructions, and when the processor executes the computer-executable instructions, the above first aspect and the first The front-end and back-end development methods described in various possible designs.

In the sixth aspect, the embodiment of the present application provides another computer-readable storage medium, the computer-readable storage medium stores computer-executable instructions, and when the processor executes the computer-executable instructions, the second aspect and the second aspect above are realized. The front-end and back-end development methods described in various possible designs in the second aspect.

The front-end and back-end development methods and devices provided by the embodiments of the present application are applied to the first client, and the first client runs on the device of the front-end developer. By obtaining the client list saved by the server, the client list Including the client that establishes a connection with the server, the server runs on the server; then determines the second client according to the above client list, and the second client runs on the device of the background developer; finally sends the second client through the server The client sends a pairing debugging request message, so that the second client sends the pairing debugging request message to the background interface project, and returns the obtained interface return message to the first client through the server, enabling front-end and back-end developers to Before the code integration test, paired joint debugging can be carried out at any time, which can reduce the disagreement between interface developers on interface development, and can detect interface problems in time to improve the efficiency of front-end and back-end development.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description These are some embodiments of the present application. Those skilled in the art can also obtain other drawings based on these drawings without any creative effort.

Fig. 1 is a schematic diagram of the front-end development system architecture provided by the embodiment of the present application;

Fig. 2 is a schematic flow diagram 1 of the front-end and back-end development methods provided by the embodiment of the present application;

FIG. 3 is a schematic flow diagram II of the front-end and back-end development methods provided by the embodiment of the present application;

FIG. 4 is a schematic structural diagram of the front-end and back-end development equipment provided by the embodiment of the present application;

FIG. 5 is a schematic structural diagram II of the front-end and back-end development equipment provided by the embodiment of the present application;

FIG. 6 is a schematic structural diagram of an electronic device provided by an embodiment of the present application.

Detailed ways

In order to make the purposes, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments It is a part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by persons of ordinary skill in the art without creative efforts fall within the protection scope of this application.

At present, in order to meet users' pursuit of product experience, the complexity of front-end development has increased rapidly, and the development model of back-end development taking into account the front-end page has been eliminated, and the development model of front-end and back-end separation has evolved. The new development model enables parallel development of the front-end and the back-end, and finally combines performance and data through the restful protocol interface. However, the parallel development of the front-end and the back-end may lead to the inconsistency of the interface development between the front-end and the back-end development engineers. This problem is not exposed until the integration test stage. It is necessary to modify the code to re-integrate the test, and the development efficiency is low.

Therefore, considering the above problems, this application provides a front-end and back-end development method, the method is applied to the first client, the first client runs on the device of the front-end developer, by obtaining the client list saved by the server, wherein , the client list includes clients that establish connections with the server, and the server runs on the server; then determine the second client according to the above client list, and the second client runs on the device of the background developer; finally, through the server Send a pairing debugging request message to the second client, so that the second client sends the pairing debugging request message to the background interface project, and returns the obtained interface return message to the first client through the server, so that the front and rear End developers can perform pairing and joint debugging at any time before code integration testing, reducing the situation where interface developers have differences in interface development, and can detect interface problems in time to improve the efficiency of front-end and back-end development.

A front-end and back-end development method provided by this application can be applied to the schematic diagram of the front-end and back-end development system shown in Figure 1. As shown in Figure 1, the first client 101 runs on the front-end developer's device, and the server 102 runs On the server, for example, the first client 101 runs on the local machine of the front-end developer, the server 102 runs on the remote server, and the server 102 establishes a data connection with the first client 101 through the internal LAN. The first client 101 is connected to the front-end project, wherein the front-end project refers to the front-end project running on the front-end local machine. The first client 101 may obtain a client list stored by the server 102 , where the client list includes clients that establish connections with the server 102 . The first client 101 may determine the second client 103 according to the above client list, where the second client 103 runs on the device of the background developer. Exemplarily, the second client 103 runs on the local machine of the background developer, and the server 102 establishes a data connection with the second client 103 through the internal LAN. The second client 103 is connected to the background interface project, wherein the background interface project refers to the restful interface project running on the background local machine. The first client 101 may also send a pairing debugging request message to the second client 103 through the server 102, so that the second client 103 sends the pairing debugging request message to the background interface engineering , and send the obtained interface return message to the server 102, and return to the first client 101 through the server 102.

Here, a client (Client) may also be referred to as a client, and refers to a program that corresponds to a server and provides local services for clients. The server serves the client, such as providing resources to the client, saving client data, and so on. Restful is a software architectural style and design style, not a standard. It just provides a set of design principles and constraints. It is mainly used for client-server interaction software. Software designed based on this style can be more concise and more There are layers, and it is easier to implement mechanisms such as caching.

The technical solution of the present application and how the technical solution of the present application solves the above technical problems will be described in detail below with specific embodiments. The following specific embodiments may be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. Embodiments of the present application will be described below in conjunction with the accompanying drawings.

FIG. 2 is a first schematic flow diagram of the front-end and back-end development method provided by the embodiment of the present application. The execution subject of the embodiment of the present application may be the first client in the embodiment shown in FIG. 1 . As shown in Figure 2, the method may include:

S201: Obtain a client list saved by the server, where the client list includes clients that establish connections with the server, and the server runs on the server.

Optionally, the above method also includes:

Establish a connection with the server;

sending heartbeat data to the server after a preset time interval, and judging whether the heartbeat data returned by the server is received;

If the heartbeat data returned by the server is not received, re-execute the step of establishing a connection with the server.

Exemplarily, the first client C1 is started on the local machine M1 of the front-end developer, and relevant personnel may be prompted to enter a start-up information during startup. For example, the client indicates that C1 establishes a connection Connect1 with the server S, and C1 passes a preset time interval , for example, exchange heartbeat data with the server S every 1 second, the heartbeat data includes the startup information entered at startup, if C1 does not receive the heartbeat data returned by the server S, C1 immediately re-establishes the connection with S, if not Establish a connection and re-establish it again. If the connection cannot be established for more than three times in a row, C1 will prompt "Unable to connect to the server".

The server S can save the IP addresses and startup information of all clients that have established Socket connections with it, for example, the IP address and startup information of C1 are saved. The client C1 queries the server S for a list of other clients through the previously established connection, and then displays it on the interface of C1.

The client C1 can query the above list from the server S after a preset time interval, such as every 5 minutes, and then save it in the memory of the client. In this embodiment, the above list includes the "/rest/query" interface.

S202: Determine a second client according to the client list, where the second client runs on a background developer's device.

The first client determines the second client according to the above client list. Exemplarily, the first client displays the above client list for relevant personnel to select, and after receiving the selection instruction, the selection instruction carries client related information , such as the client ID, determine the second client according to the selection instruction above, and initiate pairing debugging.

Here, the second client needs to establish a connection with the server. Exemplarily, the second client C2 that starts the device on the local machine M2 of the background developer must input a startup information; C2 establishes a connection with the server S Connect2 , C2 exchanges heartbeat data with server S after a preset time interval, for example, every 1 second. The heartbeat data includes the startup information entered during startup. If C2 does not receive the heartbeat data returned by server S, C2 immediately re-establishes If the connection with S cannot be established, re-establish it again. If the connection cannot be established for several consecutive times, for example, 3 consecutive times, C2 will prompt "Unable to connect to the server".

As above, the server S can also obtain the IP address and startup information of C2. The client C2 queries the server S for a list of other clients through the previously established connection, and then displays it on the interface of C2. The client C2 can also query the above list from the server S after a preset time interval, such as every 5 minutes, and then save it in the memory of the client. In this embodiment, the above list includes the "/rest/query" interface.

S203: Send a pairing debugging request message to the second client through the server, so that the second client sends the pairing debugging request message to the background interface project, and returns the obtained interface The text is sent to the server, and returned to the first client through the server.

Here, the front-end developer selects client C2 to initiate pair debugging on the interface of client C1, and the command is sent to S through connection Connect1, and then transferred to C2 through connection Connect2, and the interface of C2 prompts a pair debugging request. If C2 rejects the request, this pairing debugging ends immediately. If C2 agrees to the request, C2 can prompt to input the background interface project running on the local machine M2, such as the port number of the restful interface, and C2 will save the port number in memory. Exemplarily, the front-end developer can run the front-end project on the local machine M1, operate the function button on the page, and the button triggers a request: http://localhost:8080/rest/query, and the client C1 intercepts all the requests sent by the local machine M1 Request, the part after the intercepted port number is matched with the list stored in the memory: if the match is unsuccessful, C1 releases the request to the operating system of M1 for processing. If the match is successful, for example, the match with C2 is successful, C1 sends the request to the server S, and the server S stores the request in the database, and then transfers it to C2. C2 sends the request to the restful interface running on M2, and sends the returned message from the interface to the server S. The server S stores the returned result in the database, and then transfers it to C1. C1 sends the returned result to the page for display.

The front-end developer can call the background interface project through the first client, record all the content and time of the request message and the return message of each call on the first client, and then transmit these data to the server for storage.

Optionally, the first client includes an interface design module, the interface design module includes interface specifications of the front end and the backend, and the server includes a packet inspection module;

The method also includes:

determining the message to be checked from the messages stored at the server;

Send the message to be checked to the message checking module, so that the message checking module judges whether the message to be checked is correct according to the interface specification, and determines that the message to be checked is wrong , determine the error location of the message to be checked according to the interface specification.

Optionally, the interface specification includes all node names, types, length limits, required fields, enumeration values, node dependencies, and collection node quantity constraints of the front-end and the back-end interfaces described based on the json syntax.

Here, both the first client and the second client may include the above-mentioned interface design module, and the above-mentioned interface design module includes all node names, types, length limits, required fields, enumerated values, and node dependencies based on the json syntax description interface , the number of collection nodes, etc. It can be used as an interface specification that front-end and back-end developers must abide by, and can also be used by the message checking module to judge the correctness of messages.

Exemplarily, a sample interface design module is as follows.

Among them, the first layer of the object describing the interface has 5 key-value pairs:

(1) The value corresponding to the RestName key is the interface name;

(2) The value corresponding to the RestUrl key is the interface address suffix;

(3) The value corresponding to the RestDesc key is the functional expression of the interface;

(4) The value corresponding to the RestReqFields key is the description of all fields of the interface request message;

(5) The value corresponding to the RestRspFields key is the description of all the fields in the message returned by the interface.

The values of the RestReqFields and RestRspFields keys are both an array, which contains several sub-objects, and each sub-object has 7 key-value pairs:

(1) The value corresponding to the FieldDesc key is the description of the meaning of the field;

(2) The value corresponding to the FieldPath key is the path expression of the field. For example, $.shopInfo.shopName means that the shopName node is at the lower level of the shopInfo node, and the shopInfo node is at the lower level of the root node of the interface message;

(3) The value corresponding to the FieldRequired key is whether the field is required, true means it is required, and false means it is not required;

(4) The value corresponding to the FieldType key is the field type, such as string, integer;

(5) The value corresponding to the FieldSize key is the field length, such as 64;

(6) The value corresponding to the FieldEnum key is an array of field optional values, such as ["suning", "jd"];

(7) The value corresponding to the FieldRelations key is the field's association constraints with other fields;

The value of FieldRelations is an array, which contains several sub-objects, and each sub-object has 2 key-value pairs:

(1) The corresponding value of the RelatedField key is the path expression of the related field;

(2) The corresponding value of the RelatedType key is the associated constraint type, optional value: coexist indicates that the field pointed to by the RelatedField key value and this field must be not empty at the same time, or must be empty at the same time, sizesize indicates that the field pointed to by the RelatedField key value is Array type, the value of this field is also an array type, and the array length of the two fields is the same; countsize indicates that the field pointed to by the RelatedField key value is an integer type, the value of this field is an array type, and the value of the former is the latter Array length.

In the above process of pair debugging, if the front-end developer has any objection to the message of the interface, he can find the record of the message at that time in the call history stored on the server through the first client, and submit it to the message inspection module for checking correct or not and give an explanation.

Exemplarily, taking the request message as an example, the first client determines the message to be checked from the message stored in the server, reads the content of the message, extracts the path of all the fields in the message, and then obtains the The RestReqFields node extracts the paths of all fields, and if the latter does not completely contain the former, record the paths of the unincluded fields in the message to be checked.

Traverse all sub-objects of the RestReqFields node of the interface design module, extract the path of the interface field whose FieldRequired key value is equal to true, if the field in the message to be checked is empty or does not exist, record the path of the field in the message.

Extract each field of the message to be checked, and then find the sub-object described by the RestReqFields node in the interface design module, check the type of the field according to the FieldType key value, check the length of the field according to the FieldSize key value, and check according to the FieldEnum key value Whether the field's value is within the enumeration range. If there is an item that fails to pass the inspection, record the path of the field in the message to be inspected and the unsatisfied inspection type.

Extract each FieldRelations array node under the RestReqFields node in the interface design module, traverse all sub-objects of each FieldRelations array node, extract the RelatedField key value of the sub-object, hereinafter referred to as the A value, and extract the RelatedType key value of the sub-object, hereinafter referred to as For the C value, extract the same-level FieldName key value of the FieldRelations array where the child object is located, hereinafter referred to as the B value. Find the field value of the indicated field in the message to be inspected according to the A value, and find the field value of the indicated field in the message to be inspected according to the B value. After obtaining the two field values, check the relationship between the A and B values according to the rules according to the C value: if the C value is equal to coexist, the A value and the B value must be not empty at the same time, or both must be empty; if the C value is equal to sizesize, The A value is an array type, the B value is also an array type, and the array length is the same; if the C value is equal to countsize, the A value is an integer type, and the B value is an array type, and the value of the former is the array length of the latter. If there are items that fail the inspection, record the field path of A value, field path of B value, and C value.

Collect all failed checks recorded in the above steps and display them as output.

The above are the inspection steps of the request message. If it is the inspection of the response message, replace the RestReqFields node with RestRspFields.

In addition, during the above-mentioned pair debugging process, if the background developer has any objection to the message of the interface, the message record at that time can be found in the call history stored on the server through the second client, and submitted to the message inspection module Check it for correctness and give an explanation. For specific steps, refer to the above steps for checking the request message.

It can be seen from the above description that the embodiment of the present application uses the interface design module to describe the interface design. The front-end and back-end developers refer to the interface design module for development work, and perform remote pairing and joint debugging at any time before the code integration test, and back up the interface messages generated during the joint debugging process. In the server, if the front-end and back-end developers have disputes over the interface message, the message checking module will check the correctness of the message and point out the specific location of the error, so as to confirm which party has a wrong understanding of the interface and reduce the interface designer's Manually handle the situation where developers disagree, and improve the work efficiency of the front-end and back-end separation development model.

FIG. 3 is the second schematic flow diagram of the front-end and back-end development methods provided by the embodiment of the present application. The execution subject of the embodiment of the present application may be the server in the embodiment shown in FIG. 1 . As shown in Figure 3, the method includes:

S301: Send a client list to the first client, so that the first client determines a second client according to the client list, the client list includes clients that have established connections with the server, so The first client runs on the device of the front-end developer, and the second client runs on the device of the background developer.

S302: Receive a pairing debugging request message sent by the first client to the second client.

S303: Send the pairing debugging request message to the second client, so that the second client sends the pairing debugging request message to the background interface project, and sends the obtained interface return message to the server.

S304: Return the interface return packet to the first client.

Optionally, the first client includes an interface design module, the interface design module includes interface specifications of the front end and the backend, and the server includes a packet inspection module;

The method also includes:

The message checking module receives the message to be checked sent by the first client, and the message to be checked is the message to be checked determined by the first client from the messages stored in the server;

Judging whether the message to be checked is correct according to the interface specification, and determining the error location of the message to be checked according to the interface specification when it is determined that the message to be checked is incorrect.

Here, the message checking module may also receive a message to be checked sent by the second client, and the message to be checked is a message to be checked determined by the second client from messages stored in the server. Judging whether the above-mentioned message to be checked is correct according to the above-mentioned interface specification, and when determining that the above-mentioned message to be checked is incorrect, determining the error location of the above-mentioned message to be checked according to the above-mentioned interface specification.

Optionally, the interface specification includes all node names, types, length limits, required fields, enumeration values, node dependencies, and collection node quantity constraints of the front-end and the back-end interfaces described based on the json syntax.

The front-end and back-end development methods provided by the embodiments of the present application are applied to the server. The server runs on the server and sends the client list to the first client so that the first client can determine the second client according to the client list. terminal, wherein the client list includes clients that establish connections with the server, the first client runs on the device of the front-end developer, and the second client runs on the device of the background developer; The pairing debugging request message sent by the second client; send the pairing debugging request message to the second client, so that the second client sends the pairing debugging request message to the background interface project, and returns the obtained interface message Send it to the server; return the interface return message to the first client, enabling the front-end and back-end developers to perform pairing and joint debugging at any time before the code integration test, reducing the situation where interface developers have differences in interface development, and discovering the interface in time problems and improve the efficiency of front-end and back-end development.

Corresponding to the front-end and back-end development methods in the above embodiments, FIG. 4 is a schematic structural diagram of the front-end and back-end development equipment provided in the embodiment of the present application. For ease of description, only the parts related to the embodiment of the present application are shown. FIG. 4 is a first structural schematic diagram of the front-end and back-end development equipment provided by the embodiment of the present application. As shown in Figure 4, the front-end and back-end development equipment 40 is applied to the first client, and the first client runs on the equipment of the front-end developer, and the equipment includes: a list acquisition module 401, a client determination module 402 and Pair debugging module 403 .

Wherein, the list acquiring module 401 is configured to acquire a client list saved by the server, the client list includes clients establishing connections with the server, and the server runs on the server.

The client determining module 402 is configured to determine a second client according to the client list, and the second client runs on the device of the background developer.

A pairing debugging module 403, configured to send a pairing debugging request message to the second client through the server, so that the second client sends the pairing debugging request message to the background interface project, and The obtained interface return message is sent to the server, and returned to the first client through the server.

Optionally, the first client includes an interface design module 404, and the interface design module 404 includes interface specifications of the front end and the backend, and the server includes a packet inspection module.

The device further includes a packet determination module 405 and a packet inspection module 406 .

Wherein, the message determining module 405 is configured to determine the message to be checked from the messages stored by the server.

A message checking module 406, configured to send the message to be checked to the message checking module, so that the message checking module judges whether the message to be checked is correct according to the interface specification, and determines whether the message to be checked is correct. When the message to be checked has an error, determine the error location of the message to be checked according to the interface specification.

Optionally, the interface specification includes all node names, types, length limits, required fields, enumeration values, node dependencies, and collection node quantity constraints of the front-end and the back-end interfaces described based on the json syntax.

Optionally, the device further includes a connection establishing module 407 and a data sending module 408 .

Wherein, the connection establishment module 407 is configured to establish a connection with the server.

A data sending module 408, configured to send heartbeat data to the server after a preset time interval, and determine whether the heartbeat data returned by the server is received;

The connection establishing module 407 is further configured to re-execute the step of establishing a connection with the server if the heartbeat data returned by the server is not received.

The device provided by the embodiment of the present application can be used to execute the technical solution of the above method embodiment in FIG. 2 , and its implementation principle and technical effect are similar, so the embodiments of the present application will not repeat them here.

FIG. 5 is a second structural schematic diagram of the front-end and back-end development equipment provided by the embodiment of the present application. As shown in Figure 5, the front-end and back-end development equipment 50 is applied to the server, and the server runs on the server, and the device includes: a list sending module 501, a message receiving module 502, a message sending module 503 and a message Return to module 504 .

Wherein, the list sending module 501 is configured to send the client list to the first client, so that the first client determines the second client according to the client list, and the client list includes the The first client runs on the device of the front-end developer, and the second client runs on the device of the background developer.

A message receiving module 502, configured to receive a pairing debugging request message sent by the first client to the second client.

A message sending module 503, configured to send the pairing debugging request message to the second client, so that the second client sends the pairing debugging request message to the background interface project, and obtains The interface return message is sent to the server.

A message returning module 504, configured to return the interface return message to the first client.

Optionally, the first client includes an interface design module, and the interface design module includes interface specifications of the front end and the backend, and the server includes a packet inspection module 505 .

The message checking module 505 receives the message to be checked sent by the first client, the message to be checked is the message to be checked determined by the first client from the messages stored in the server ;

Judging whether the message to be checked is correct according to the interface specification, and determining the error location of the message to be checked according to the interface specification when it is determined that the message to be checked is incorrect.

Optionally, the interface specification includes all node names, types, length limits, required fields, enumeration values, node dependencies, and collection node quantity constraints of the front-end and the back-end interfaces described based on the json syntax.

The equipment provided in the embodiment of the present application can be used to implement the technical solution of the above method embodiment in FIG. 3 , and its implementation principle and technical effect are similar, so the embodiments of the present application will not repeat them here.

Referring to FIG. 6 , it shows a schematic structural diagram of an electronic device 600 suitable for implementing the embodiment of the present application. The electronic device 600 may be a terminal device or a server. Wherein, the terminal equipment may include but not limited to mobile phones, notebook computers, digital broadcast receivers, personal digital assistants (Personal Digital Assistant, PDA for short), tablet computers (Portable Android Device, PAD for short), portable multimedia players (Portable MediaPlayer (PMP for short), mobile terminals such as vehicle-mounted terminals (such as vehicle-mounted navigation terminals), and fixed terminals such as digital TVs and desktop computers. The electronic device shown in FIG. 6 is only an example, and should not limit the functions and scope of use of this embodiment of the present application.

As shown in FIG. 6, an electronic device 600 may include a processing device (such as a central processing unit, a graphics processing unit, etc.) 601, which may be stored in a program in a read-only memory (Read Only Memory, ROM for short) 602 or from a storage device. 608 programs loaded into the Random Access Memory (RAM for short) 603 to execute various appropriate actions and processes. In the RAM 603, various programs and data necessary for the operation of the electronic device 600 are also stored. The processing device 601 , ROM 602 and RAM 603 are connected to each other through a bus 604 . An input/output (I/O) interface 605 is also connected to the bus 604 .

Generally, the following devices can be connected to the I/O interface 605: an input device 606 including, for example, a touch screen, a touchpad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; including, for example, a Liquid Crystal Display (LCD for short) , an output device 607 such as a speaker, a vibrator, etc.; a storage device 608 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 609. The communication means 609 may allow the electronic device 600 to communicate with other devices wirelessly or by wire to exchange data. While FIG. 6 shows electronic device 600 having various means, it should be understood that implementing or having all of the means shown is not a requirement. More or fewer means may alternatively be implemented or provided.

In particular, according to the embodiments of the present application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, the embodiments of the present application include a computer program product, which includes a computer program carried on a computer-readable medium, where the computer program includes program codes for executing the methods shown in the flowcharts. In such an embodiment, the computer program may be downloaded and installed from a network via communication means 609 , or from storage means 608 , or from ROM 602 . When the computer program is executed by the processing device 601, the above-mentioned functions defined in the method of the embodiment of the present application are executed.

It should be noted that the computer-readable medium mentioned above in this application may be a computer-readable signal medium or a computer-readable storage medium, or any combination of the above two. A computer readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to, electrical connections with one or more wires, portable computer diskettes, hard disks, random access memory (RAM), read-only memory (ROM), erasable Programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination of the above. In this application, a computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this application, however, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code therein. Such propagated data signals may take many forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, which can transmit, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device . Program code embodied on a computer readable medium may be transmitted by any appropriate medium, including but not limited to wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.

The above-mentioned computer-readable medium may be included in the above-mentioned electronic device, or may exist independently without being incorporated into the electronic device.

The above-mentioned computer-readable medium carries one or more programs, and when the above-mentioned one or more programs are executed by the electronic device, the electronic device is made to execute the methods shown in the above-mentioned embodiments.

Computer program code for performing the operations of the present application may be written in one or more programming languages or combinations thereof, including object-oriented programming languages—such as Java, Smalltalk, C++, and conventional Procedural Programming Language - such as "C" or a similar programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In cases involving a remote computer, the remote computer can be connected to the user's computer through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or it can be connected to an external computer (e.g. using an Internet Service Provider to connect via the Internet).

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in a flowchart or block diagram may represent a module, program segment, or portion of code that contains one or more logical functions for implementing specified executable instructions. It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or they may sometimes be executed in the reverse order, depending upon the functionality involved. It should also be noted that each block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by a dedicated hardware-based system that performs the specified functions or operations , or may be implemented by a combination of dedicated hardware and computer instructions.

The units involved in the embodiments described in the present application may be implemented by means of software or by means of hardware.

Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, rather than limiting them; although the application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: It is still possible to modify the technical solutions described in the foregoing embodiments, or perform equivalent replacements for some or all of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the technical solutions of the various embodiments of the present application. scope.

Claims (9)

1. A front-end and back-end development method, the method being applied to a first client running on a front-end developer's device, the method comprising:

acquiring a client list stored by a server, wherein the client list comprises a client which establishes connection with the server, and the server runs on a server;

determining a second client according to the client list, wherein the second client runs on equipment of a background developer;

sending a junction to a second client through the server so that the second client sends the junction to a background interface project, and sends an obtained interface return message to the server, and the first client is returned through the server;

The first client comprises an interface design module, the interface design module comprises interface specifications of the front end and the background, and the server comprises a message checking module;

the method further comprises the steps of:

determining a message to be checked from the messages stored in the server;

and sending the message to be checked to the message checking module, so that the message checking module judges whether the message to be checked is correct according to the interface specification, and determines the error position of the message to be checked according to the interface specification when judging that the message to be checked is error.

2. The method of claim 1, wherein the interface specification includes all node names, types, length restrictions, whether to fill, enumerated values, node dependencies, and aggregate node number constraints for the front end and the background interface described based on json syntax.

3. The method as recited in claim 1, further comprising:

establishing connection with the server;

sending heartbeat data to the server at preset time intervals, and judging whether the heartbeat data returned by the server are received or not;

and if the heartbeat data returned by the server side is not received, the step of establishing connection with the server side is re-executed.

4. A front-end and back-end development method, wherein the method is applied to a server, the server running on a server, the method comprising:

transmitting a client list to a first client so that the first client determines a second client according to the client list, wherein the client list comprises clients connected with the server, the first client operates on equipment of a front-end developer, and the second client operates on equipment of a background developer;

receiving a knot debug request message sent by the first client to the second client;

sending the junction to the second client to enable the second client to send the junction to a background interface project and send the obtained interface return message to the server;

returning the interface return message to the first client;

the first client comprises an interface design module, the interface design module comprises interface specifications of the front end and the background, and the server comprises a message checking module;

the method further comprises the steps of:

the message checking module receives a message to be checked sent by the first client, wherein the message to be checked is determined from the messages stored by the server by the first client;

Judging whether the message to be checked is correct or not according to the interface specification, and determining the error position of the message to be checked according to the interface specification when judging that the message to be checked is error.

5. The method of claim 4, wherein the interface specification includes all node names, types, length restrictions, whether to fill, enumerated values, node dependencies, and aggregate node number constraints for the front end and the background interfaces described based on json syntax.

6. A front-end development device, the device being for use with a first client running on a front-end developer's device, the device comprising a memory, a processor, and computer-executable instructions stored in the memory and executable on the processor, when executing the computer-executable instructions, performing the steps of:

acquiring a client list stored by a server, wherein the client list comprises a client which establishes connection with the server, and the server runs on a server;

determining a second client according to the client list, wherein the second client runs on equipment of a background developer;

Sending a junction to a second client through the server so that the second client sends the junction to a background interface project, and sends an obtained interface return message to the server, and the first client is returned through the server;

the first client comprises an interface design module, the interface design module comprises interface specifications of the front end and the background, and the server comprises a message checking module;

the processor when executing the computer execution instructions also realizes the following steps:

determining a message to be checked from the messages stored in the server;

and sending the message to be checked to the message checking module, so that the message checking module judges whether the message to be checked is correct according to the interface specification, and determines the error position of the message to be checked according to the interface specification when judging that the message to be checked is error.

7. A front-end and back-end development device, wherein the device is applied to a server, the server runs on a server, the device comprises a memory, a processor and computer-executable instructions stored in the memory and running on the processor, and the processor implements the following steps when executing the computer-executable instructions:

Transmitting a client list to a first client so that the first client determines a second client according to the client list, wherein the client list comprises clients connected with the server, the first client operates on equipment of a front-end developer, and the second client operates on equipment of a background developer;

receiving a knot debug request message sent by the first client to the second client;

sending the junction to the second client to enable the second client to send the junction to a background interface project and send the obtained interface return message to the server;

returning the interface return message to the first client;

the first client comprises an interface design module, the interface design module comprises interface specifications of the front end and the background, and the server comprises a message checking module;

the processor when executing the computer execution instructions also realizes the following steps:

the message checking module receives a message to be checked sent by the first client, wherein the message to be checked is determined from the messages stored by the server by the first client;

Judging whether the message to be checked is correct or not according to the interface specification, and determining the error position of the message to be checked according to the interface specification when judging that the message to be checked is error.

8. A computer-readable storage medium having stored therein computer-executable instructions that, when executed by a processor, implement the front-end development method of any one of claims 1 to 3.

9. A computer-readable storage medium having stored therein computer-executable instructions that, when executed by a processor, implement the front-end development method of any one of claims 4 to 5.