A real-time debugging system for low-code designers based on web browsers

Abstract

The present invention discloses a low-code designer real-time debugging system based on a Web browser, comprising an acquisition and storage module, an identifier creation module, a debugging preparation module, a debugging optimization module, a real-time debugging module, a code synchronization module and a feedback module; the present invention reduces the switching between tools through an integrated debugging system and a low-code designer, which not only reduces development costs but also improves work efficiency; further, debugging is performed through a Web browser without the need to install additional devices, which not only realizes remote collaboration and mobile office scenarios but also improves debugging flexibility; and automatic breakpoint selection is achieved by calculating the breakpoint execution index of the web debugging context, thereby avoiding the tedious steps of searching for error clues from massive logs and improving work efficiency.

Description

Technical Field

[0001] The present invention relates to the technical field of low-code designer real-time debugging, and specifically to a low-code designer real-time debugging system based on a Web browser. Background Art

[0002] Typically, code debugging requires installing additional devices and configuring a complete environment for them. This process has a high barrier to entry and a steep learning curve. When analyzing program execution logs, the correctness of code execution is determined by the information in the logs. However, the biggest problem with this method is its low efficiency and difficulty observing the execution status of each step during the execution process.

[0003] The low-code designer real-time debugging system is an upper-level device based on the low-code designer. The low-code designer is implemented based on a web browser. It can perform low-code business logic development by dragging links to the editor; however, traditional debugging can only be executed step by step or by setting breakpoints for debugging, which greatly reduces work efficiency. Summary of the Invention

[0004] The purpose of the present invention is to provide a low-code designer real-time debugging system based on a Web browser to solve the problems raised in the above background technology.

[0005] In order to solve the above technical problems, the present invention provides the following technical solutions:

[0006] A low-code designer real-time debugging system based on a web browser, the system includes an acquisition and storage module, an identifier creation module, a debugging preparation module, a debugging optimization module, a real-time debugging module, a code synchronization module, and a feedback module;

[0007] The acquisition and storage module includes an acquisition unit and a storage unit, the acquisition unit is used to acquire breakpoint debugging data and debugging context, one breakpoint debugging data corresponds to one debugging context; the storage unit is used to record the breakpoint debugging data and debugging context in a debugging database; and construct a debugging context set;

[0008] The identifier creation module builds a persistent connection between the Web client and the server by creating a session identifier. Each persistent connection has only one session identifier.

[0009] The debugging preparation module includes a breakpoint unit and a debugging unit. In the breakpoint unit, the web client creates a web debugging context, calculates the similarity between the web debugging context and the debugging context, generates a debugging context sequence, extracts the breakpoint debugging data corresponding to the first debugging context in the debugging context sequence, calculates the breakpoint execution index of the web debugging context, and sets a breakpoint on the web debugging context when the breakpoint execution index of the web debugging context is less than the execution threshold. In the debugging unit, after receiving the debugging request from the web client, the server loads the debugging interceptor, receives the web debugging context, and binds the web debugging context to the session identifier; at the same time, a new thread is created to execute the code arranged by the web client in the low-code designer, and the debugging interceptor takes effect.

[0010] The debugging optimization module includes an optimization unit and a calculation unit, which are used to optimize the similarity between the web debugging context and the debugging context, and obtain the actual similarity value between the web debugging context and the debugging context by calculating the impact factor of the similarity;

[0011] In the real-time debugging module, when the code arranged by the Web client in the low-code designer is executed, each execution step will pass through the debugging interceptor. When the execution step reaches the breakpoint position of the web debugging context, the blocking controller is called to block the thread and the debugging information is sent to the Web client. When the continue execution instruction sent by the Web client is received, the blocking controller is called to release the thread until the debugging of the code arranged by the Web client in the low-code designer is completed, and the execution result is sent to the Web client.

[0012] The code synchronization module, after receiving the real-time debugging information, the web client renders the current execution step and global variable data, wherein the server obtains the message channel of the web debugging context through the session identifier;

[0013] The feedback module records the real-time debugging information and the corresponding breakpoint debugging data in the database after the Web client receives the execution result.

[0014] Furthermore, the acquisition and storage module includes an acquisition unit and a storage unit;

[0015] The collecting unit collects breakpoint debugging data and debugging context, where one breakpoint debugging data corresponds to one debugging context, the breakpoint debugging data includes the number of breakpoint executions and the number of breakpoint errors, and the debugging context includes the code context, the document context, and the expression calculation context;

[0016] The storage unit constructs a debugging database and records the breakpoint debugging data and debugging context in the debugging database; constructs a debugging context set DB={db i|i∈[1,I]}, where db i represents the i-th debug context in the debug database, and I represents the total number of debug contexts in the debug database.

[0017] Furthermore, the identifier creation module creates a session identifier and builds a persistent connection between the Web client and the server when the Web client sends a user session request to the server through a Web browser. Each persistent connection has one and only one session identifier, wherein one user session request corresponds to one session identifier, and the session identifier is a unique identifier of the user session request.

[0018] Furthermore, the debugging preparation module includes a breakpoint unit and a debugging unit;

[0019] The breakpoint unit, the Web client creates a web debugging context, extracts keywords of the web debugging context according to a preset keyword information library, and constructs a web debugging context keyword set S={s g |g∈[1,G]}, where s g represents the gth keyword in the web debugging context, and G represents the total number of keywords in the web debugging context;

[0020] Based on the debugging database, the debugging context db is extracted through the preset keyword information library i Keywords to build debug context db i Keyword collection Among them, s f Indicates the debug context db i The fth keyword in the debug context db i The total number of keywords in the;

[0021] Compute web debug context and debug context db i Similarity: in, Represents the web debugging context keyword set and debugging context db i the number of elements in the intersection of the keyword sets, Represents the web debugging context keyword set and debugging context db i The number of elements in the union of the keyword sets;

[0022] Calculate the similarity between the web debugging context and all debugging contexts in the debugging context set DB, and generate a debugging context sequence in descending order of similarity;

[0023] Extract the breakpoint debugging data corresponding to the first debugging context in the debugging context sequence and calculate the breakpoint execution index of the web debugging context: MN = e-NL / ML , where NL represents the number of breakpoint errors and ML represents the number of breakpoint executions;

[0024] When the breakpoint execution index of the web debugging context is less than the execution threshold, setting breakpoint data at the breakpoint position of the web debugging context, wherein the breakpoint data includes the breakpoint position, the breakpoint condition, the breakpoint type, and the breakpoint record;

[0025] It should be explained that the breakpoint location is the specific location where the program execution is paused, usually a source code line number or a specific memory address; the breakpoint condition specifies the conditions for triggering the breakpoint. Only when the conditions are met will the thread pause at the breakpoint; breakpoint types include ordinary breakpoints, data breakpoints, hardware breakpoints, etc. Different types of breakpoints have different functions and uses; breakpoint records include breakpoint-related variables and status. When a thread pauses at a breakpoint, the variables and status information related to the breakpoint are also recorded. This information helps the Web client understand the status of the code at the breakpoint and locate the problem.

[0026] The debugging unit, after the server receives the Web client debugging request, loads the debugging interceptor, receives the web debugging context, and binds the web debugging context to the session identifier; at the same time, a new thread is created to execute the code arranged by the Web client in the low-code designer, and the debugging interceptor takes effect.

[0027] Furthermore, the debugging and optimization module includes an optimization unit and a calculation unit;

[0028] The optimization unit merges two adjacent keywords in the web debugging context keyword set into one keyword to generate a new web debugging context keyword set S 2*1 ={s g |g∈[1,G-1]}, the debugging context db i Merge two adjacent keywords in the keyword set into one keyword to generate the debugging context db i New set of keywords Calculate the impact factor of the similarity of the first merge in, Represents a new collection of web debug context keywords and debug context db i The number of elements in the intersection of the new set of keywords, Represents a new collection of web debug context keywords and debug context db i The number of elements in the union of the new set of keywords;

[0029] The calculation unit continuously repeats the optimization unit until g∈[1] or f∈[1] stops the optimization, and calculates the web debugging context and the debugging context db i The actual value of similarity: Among them, r represents the web debugging context and the debugging context db i The similarity is optimized for the rth time, where R represents the web debugging context and the debugging context db i The total number of similarities optimized for the rth time.

[0030] It should be explained that by calculating the unit and repeatedly optimizing the unit, the more times the optimization unit is repeated, the more accurate the actual value of similarity obtained. By debugging the optimization module, the accuracy of automatic breakpoint selection is improved.

[0031] Furthermore, in the real-time debugging module, when the code orchestrated by the Web client in the low-code designer is executed, each execution step will pass through the debugging interceptor. When the execution step reaches the breakpoint position of the web debugging context, the blocking controller is called to block the thread and the debugging information is sent to the Web client; when the continue execution instruction sent by the Web client is received, the blocking controller is called to release the thread until the debugging of the code orchestrated by the Web client in the low-code designer is completed, and the execution result is sent to the Web client.

[0032] Furthermore, in the code synchronization module, after the Web client receives the real-time debugging information, it renders the current execution step and global variable data, wherein the server obtains the message channel of the web debugging context through the session identifier.

[0033] Furthermore, the feedback module records the web debugging context and breakpoint debugging data in a debugging database after the Web client receives the execution result.

[0034] Compared with the prior art, the beneficial effects achieved by the present invention are as follows: the present invention provides a low-code designer real-time debugging system based on a Web browser, including an acquisition and storage module, an identifier creation module, a debugging preparation module, a debugging optimization module, a real-time debugging module, a code synchronization module and a feedback module; the present invention reduces the switching between tools through an integrated debugging system and a low-code designer, which not only reduces development costs but also improves work efficiency; further, debugging is performed through a Web browser without the need to install additional devices, which not only realizes remote collaboration and mobile office scenarios, but also improves the flexibility of debugging; and by calculating the breakpoint execution index of the web debugging context, automatic selection of breakpoints is achieved, thereby avoiding the tedious steps of searching for error clues from massive logs and improving work efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] The accompanying drawings are used to provide further understanding of the present invention and constitute a part of the specification. They are used to explain the present invention together with the embodiments of the present invention and do not constitute a limitation of the present invention.

[0036] Figure 1 It is a structural diagram of a low-code designer real-time debugging system based on a Web browser of the present invention;

[0037] Figure 2 This is a schematic diagram of the automatic breakpoint selection steps of a low-code designer real-time debugging system based on a Web browser of the present invention. DETAILED DESCRIPTION

[0038] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of the present invention.

[0039] See also Figure 1 , in this embodiment 1: a low-code designer real-time debugging system based on a web browser, the system includes a collection and storage module, an identifier creation module, a debugging preparation module, a debugging optimization module, a real-time debugging module, a code synchronization module and a feedback module;

[0040] The acquisition and storage module includes an acquisition unit and a storage unit. The acquisition unit is used to acquire breakpoint debugging data and debugging context, and one breakpoint debugging data corresponds to one debugging context; the storage unit is used to record the breakpoint debugging data and debugging context in the debugging database; and build a debugging context set;

[0041] The identifier creation module builds a persistent connection between the Web client and the server by creating a session identifier. Each persistent connection has only one session identifier.

[0042] The debugging preparation module includes a breakpoint unit and a debugging unit. In the breakpoint unit, the web client creates a web debugging context, calculates the similarity between the web debugging context and the debugging context, generates a debugging context sequence, extracts the breakpoint debugging data corresponding to the first debugging context in the debugging context sequence, calculates the breakpoint execution index of the web debugging context, and sets a breakpoint on the web debugging context when the breakpoint execution index of the web debugging context is less than the execution threshold. In the debugging unit, after receiving the debugging request from the web client, the server loads the debugging interceptor, receives the web debugging context, and binds the web debugging context to the session identifier. At the same time, a new thread is created to execute the code arranged by the web client in the low-code designer, and the debugging interceptor takes effect.

[0043] The debugging optimization module includes an optimization unit and a calculation unit, which are used to optimize the similarity between the web debugging context and the debugging context, and obtain the actual similarity value between the web debugging context and the debugging context by calculating the impact factor of the similarity;

[0044] Real-time debugging module: When the code arranged by the Web client in the low-code designer is executed, each execution step will pass through the debugging interceptor. When the execution step reaches the breakpoint position of the web debugging context, the blocking controller is called to block the thread and the debugging information is sent to the Web client. When the continue execution instruction sent by the Web client is received, the blocking controller is called to release the thread until the debugging of the code arranged by the Web client in the low-code designer is completed, and the execution result is sent to the Web client.

[0045] In the code synchronization module, after the web client receives the real-time debugging information, it renders the current execution step and global variable data. The server obtains the message channel of the web debugging context through the session identifier.

[0046] Feedback module, when the Web client receives the execution result, it records the real-time debugging information and the corresponding breakpoint debugging data in the database.

[0047] Preferably, the acquisition and storage module includes an acquisition unit and a storage unit;

[0048] The collection unit collects breakpoint debugging data and debugging context. One breakpoint debugging data corresponds to one debugging context. The breakpoint debugging data includes the number of breakpoint executions and the number of breakpoint errors. The debugging context includes the code context, document context, and expression evaluation context.

[0049] Storage unit, build debug database, and record breakpoint debug data and debug context in the debug database; build debug context set DB = {db i |i∈[1,I]}, where db i represents the i-th debug context in the debug database, and I represents the total number of debug contexts in the debug database.

[0050] Preferably, the identifier creation module creates a session identifier and builds a persistent connection between the Web client and the server when the Web client sends a user session request to the server through a Web browser. Each persistent connection has one and only one session identifier, wherein one user session request corresponds to one session identifier, and the session identifier is a unique identifier of the user session request.

[0051] Preferably, the debugging preparation module includes a breakpoint unit and a debugging unit;

[0052] Breakpoint unit, Web client creates web debugging context, extracts web debugging context keywords according to preset keyword information library, and constructs web debugging context keyword set S={s g |g∈[1,G]}, where s g represents the gth keyword in the web debugging context, and G represents the total number of keywords in the web debugging context;

[0053] Based on the debugging database, the debugging context db is extracted through the preset keyword information library i Keywords to build debug context db i Keyword collection Among them, s f Indicates the debug context db i The fth keyword in the debug context db i The total number of keywords in the;

[0054] Compute web debug context and debug context db i Similarity: in, Represents the web debugging context keyword set and debugging context db i the number of elements in the intersection of the keyword sets, Represents the web debugging context keyword set and debugging context db i The number of elements in the union of the keyword sets;

[0055] Calculate the similarity between the web debugging context and all debugging contexts in the debugging context set DB, and generate a debugging context sequence in descending order of similarity;

[0056] Extract the breakpoint debugging data corresponding to the first debugging context in the debugging context sequence and calculate the breakpoint execution index of the web debugging context: MN = e -NL / ML , where NL represents the number of breakpoint errors and ML represents the number of breakpoint executions;

[0057] When the breakpoint execution index of the web debugging context is less than the execution threshold, setting breakpoint data at the breakpoint position of the web debugging context, wherein the breakpoint data includes the breakpoint position, the breakpoint condition, the breakpoint type, and the breakpoint record;

[0058] Debugging unit: After the server receives the debugging request from the Web client, it loads the debugging interceptor, receives the web debugging context, and binds the web debugging context to the session identifier; at the same time, it creates a new thread to execute the code orchestrated by the Web client in the low-code designer, and the debugging interceptor takes effect.

[0059] Preferably, the debugging and optimization module includes an optimization unit and a calculation unit;

[0060] The optimization unit merges two adjacent keywords in the web debugging context keyword set into one keyword to generate a new web debugging context keyword set S 2*1 ={s g |g∈[1,G-1]}, the debugging context db i Merge two adjacent keywords in the keyword set into one keyword to generate the debugging context db i New set of keywords Calculate the impact factor of the similarity of the first merge in, Represents a new collection of web debug context keywords and debug context db i The number of elements in the intersection of the new set of keywords, Represents a new collection of web debug context keywords and debug context db i The number of elements in the union of the new set of keywords;

[0061] Calculate the unit, repeat the optimization unit until g∈[1] or f∈[1] stops the optimization, calculate the web debugging context and debugging context db i The actual value of similarity: Among them, r represents the web debugging context and the debugging context db i The similarity is optimized for the rth time, where R represents the web debugging context and the debugging context db i The total number of similarities optimized for the rth time.

[0062] Preferably, in the real-time debugging module, when the code arranged by the Web client in the low-code designer is executed, each execution step will pass through the debugging interceptor. When the execution step reaches the breakpoint position of the web debugging context, the blocking controller is called to block the thread, and the debugging information is sent to the Web client; when the continue execution instruction sent by the Web client is received, the blocking controller is called to release the thread until the debugging of the code arranged by the Web client in the low-code designer is completed, and the execution result is sent to the Web client.

[0063] Preferably, in the code synchronization module, after the Web client receives the real-time debugging information, it renders the current execution step and global variable data, wherein the server obtains the message channel of the web debugging context through the session identifier.

[0064] Preferably, the feedback module records the web debugging context and breakpoint debugging data in a debugging database after the Web client receives the execution result.

[0065] See also Figure 2 In the second embodiment of the present invention, the following steps are performed to automatically select breakpoints in a low-code designer real-time debugging system based on a web browser:

[0066] Step 1: Connect to the server through a web browser on the web client and create a Session Id (session identifier), which is a unique identifier for this connection.

[0067] Step 2: Send a debugging request through a web browser. After receiving the debugging request, the server loads the debugging interceptor, creates a web debugging context, and binds it to the Session ID.

[0068] Step 3: extracting keywords of the web debugging context according to a preset keyword information library and constructing a web debugging context keyword set;

[0069] Step 4: Based on the debugging database, extract the debugging context db through the preset keyword information library i Keywords to build debug context db i Keyword collection;

[0070] Step 5: Calculate the web debug context and debug context db i similarity;

[0071] Step 6: Calculate the web debug context and debug context db through the debug optimization module i The actual value of similarity;

[0072] Step 7: Calculate the similarity between the web debugging context and all debugging contexts in the debugging context set DB, and generate a debugging context sequence in descending order of similarity;

[0073] Step 8: Extract the breakpoint debugging data corresponding to the first debugging context in the debugging context sequence and calculate the breakpoint execution index of the web debugging context;

[0074] Step 9: When the breakpoint execution index of the web debugging context is less than the execution threshold, the breakpoint data is set at the breakpoint position of the web debugging context.

[0075] It should be noted that, in this document, relational terms such as first and second, etc., are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the terms "comprises," "comprising," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or apparatus.

[0076] Finally, it should be noted that the above description is merely a preferred embodiment of the present invention and is not intended to limit the present invention. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art will be able to modify the technical solutions described in the aforementioned embodiments or substitute equivalents for some of the technical features. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of the present invention shall be included within the scope of protection of the present invention.

Claims

1. A low-code designer real-time debugging system based on a web browser, characterized in that: The system includes an acquisition and storage module, an identifier creation module, a debugging preparation module, a debugging optimization module, a real-time debugging module, a code synchronization module, and a feedback module; The acquisition and storage module includes an acquisition unit and a storage unit, the acquisition unit is used to acquire breakpoint debugging data and debugging context, and one breakpoint debugging data corresponds to one debugging context; A storage unit, used for recording breakpoint debugging data and debugging context in a debugging database; Build a debug context collection; The identifier creation module builds a persistent connection between the Web client and the server by creating a session identifier. Each persistent connection has only one session identifier. The debugging preparation module includes a breakpoint unit and a debugging unit. The breakpoint unit and the Web client create a web debugging context, calculate the similarity between the web debugging context and the debugging context, and generate a debugging context sequence; Extracting breakpoint debugging data corresponding to the first debugging context in the debugging context sequence, calculating the breakpoint execution index of the web debugging context, and setting a breakpoint on the web debugging context when the breakpoint execution index of the web debugging context is less than an execution threshold; The debugging unit, after receiving the debugging request from the Web client, loads the debugging interceptor, receives the web debugging context, and binds the web debugging context to the session identifier; At the same time, a new thread is created to execute the code arranged by the Web client in the low-code designer, and the debugging interceptor takes effect; The debugging optimization module includes an optimization unit and a calculation unit, which are used to optimize the similarity between the web debugging context and the debugging context, and obtain the actual similarity value between the web debugging context and the debugging context by calculating the impact factor of the similarity; In the real-time debugging module, when the code arranged by the Web client in the low-code designer is executed, each execution step will pass through the debugging interceptor. When the execution step reaches the breakpoint position of the web debugging context, the blocking controller is called to block the thread and the debugging information is sent to the Web client. When the continue execution instruction sent by the Web client is received, the blocking controller is called to release the thread until the debugging of the code arranged by the Web client in the low-code designer is completed, and the execution result is sent to the Web client. The code synchronization module, after receiving the real-time debugging information, the web client renders the current execution step and global variable data, wherein the server obtains the message channel of the web debugging context through the session identifier; The feedback module records the web debugging context and the corresponding breakpoint debugging data in a database after the Web client receives the execution result.

2. A low-code designer real-time debugging system based on a Web browser according to claim 1, characterized in that: The acquisition and storage module includes an acquisition unit and a storage unit; The collecting unit collects breakpoint debugging data and debugging context, where one breakpoint debugging data corresponds to one debugging context, the breakpoint debugging data includes the number of breakpoint executions and the number of breakpoint errors, and the debugging context includes the code context, the document context, and the expression calculation context; The storage unit builds a debugging database and records the breakpoint debugging data and debugging context in the debugging database; Construct debug context set DB = {db i |i∈[1,I]}, where db i represents the i-th debug context in the debug database, and I represents the total number of debug contexts in the debug database.

3. A low-code designer real-time debugging system based on a Web browser according to claim 2, characterized in that: The identifier creation module creates a session identifier when a web client sends a user session request to the server through a web browser, and establishes a persistent connection between the web client and the server. Each persistent connection has one and only one session identifier, wherein one user session request corresponds to one session identifier, and the session identifier is a unique identifier of the user session request.

4. A low-code designer real-time debugging system based on a Web browser according to claim 3, characterized in that: The debugging preparation module includes a breakpoint unit and a debugging unit; The breakpoint unit, the Web client creates a web debugging context, extracts keywords of the web debugging context according to a preset keyword information library, and constructs a web debugging context keyword set S={s g |g∈[1,G]}, where s g represents the gth keyword in the web debugging context, and G represents the total number of keywords in the web debugging context; Based on the debugging database, the debugging context db is extracted through the preset keyword information library i Keywords to build debug context db i Keyword collection Among them, s f Indicates the debug context db i The fth keyword in the debug context db i The total number of keywords in the; Compute web debug context and debug context db i Similarity: in, Represents the web debugging context keyword set and debugging context db i the number of elements in the intersection of the keyword sets, Represents the web debugging context keyword set and debugging context db i The number of elements in the union of keyword sets; Calculate the similarity between the web debugging context and all debugging contexts in the debugging context set DB, and generate a debugging context sequence in descending order of similarity; Extract the breakpoint debugging data corresponding to the first debugging context in the debugging context sequence and calculate the breakpoint execution index of the web debugging context: MN = e -NL / ML , where NL represents the number of breakpoint errors and ML represents the number of breakpoint executions; When the breakpoint execution index of the web debugging context is less than the execution threshold, setting breakpoint data at the breakpoint position of the web debugging context, wherein the breakpoint data includes the breakpoint position, the breakpoint condition, the breakpoint type, and the breakpoint record; The debugging unit, after the server receives the Web client debugging request, loads the debugging interceptor, receives the web debugging context, and binds the web debugging context to the session identifier; at the same time, a new thread is created to execute the code arranged by the Web client in the low-code designer, and the debugging interceptor takes effect.

5. A low-code designer real-time debugging system based on a Web browser according to claim 4, characterized in that: The debugging and optimization module includes an optimization unit and a calculation unit; The optimization unit merges two adjacent keywords in the web debugging context keyword set into one keyword to generate a new web debugging context keyword set S 2*1 ={s g |g∈[1,G-1]}, the debugging context db i Merge two adjacent keywords in the keyword set into one keyword to generate the debugging context db i New set of keywords Calculate the impact factor of the similarity of the first merge in, Represents a new collection of web debug context keywords and debug context db i The number of elements in the intersection of the new set of keywords, Represents a new collection of web debug context keywords and debug context db i The number of elements in the union of the new set of keywords; The calculation unit repeats the optimization unit until g∈[1] or f∈[1] stops the optimization, and calculates the web debugging context and the debugging context db i The actual value of similarity: Among them, r represents the web debugging context and the debugging context db i The similarity is optimized for the rth time, where R represents the web debugging context and the debugging context db i The total number of similarities optimized for the rth time.

6. A low-code designer real-time debugging system based on a Web browser according to claim 5, characterized in that: In the real-time debugging module, when the code orchestrated by the Web client in the low-code designer is executed, each execution step will pass through the debugging interceptor. When the execution step reaches the breakpoint position of the web debugging context, the blocking controller is called to block the thread and the debugging information is sent to the Web client; when the continue execution instruction sent by the Web client is received, the blocking controller is called to release the thread until the debugging of the code orchestrated by the Web client in the low-code designer is completed, and the execution result is sent to the Web client.

7. A low-code designer real-time debugging system based on a Web browser according to claim 6, characterized in that: The code synchronization module renders the current execution step and global variable data after the Web client receives the real-time debugging information, wherein the server obtains the message channel of the web debugging context through the session identifier.

8. A low-code designer real-time debugging system based on a Web browser according to claim 7, characterized in that: The feedback module records the web debugging context and breakpoint debugging data in the debugging database after the Web client receives the execution result.

Images