CN114816373A - Instant error prompt method and system for low-code development platform - Google Patents
Instant error prompt method and system for low-code development platform Download PDFInfo
- Publication number
- CN114816373A CN114816373A CN202210755238.XA CN202210755238A CN114816373A CN 114816373 A CN114816373 A CN 114816373A CN 202210755238 A CN202210755238 A CN 202210755238A CN 114816373 A CN114816373 A CN 114816373A
- Authority
- CN
- China
- Prior art keywords
- component
- error
- event
- error prompt
- prompt
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/33—Intelligent editors
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F18/00—Pattern recognition
- G06F18/20—Analysing
- G06F18/24—Classification techniques
- G06F18/241—Classification techniques relating to the classification model, e.g. parametric or non-parametric approaches
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/38—Creation or generation of source code for implementing user interfaces
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/451—Execution arrangements for user interfaces
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Human Computer Interaction (AREA)
- Bioinformatics & Cheminformatics (AREA)
- Evolutionary Computation (AREA)
- Evolutionary Biology (AREA)
- Computer Vision & Pattern Recognition (AREA)
- Bioinformatics & Computational Biology (AREA)
- Artificial Intelligence (AREA)
- Life Sciences & Earth Sciences (AREA)
- Debugging And Monitoring (AREA)
- Stored Programmes (AREA)
Abstract
The invention provides an instant error prompt method and system for a low-code development platform, which belong to the technical field of low-code development and comprise the following steps: classifying different operation objects based on code development, wherein the operation objects comprise development of components, resources, editors and event operation objects; receiving a current development action signal, judging the type of an operation object, respectively carrying out verification processing based on the type of the operation object, and carrying out error prompt on a console interface based on a verification result; meanwhile, the error prompt is respectively stored in different variable objects based on the operation object type and is bound with the corresponding component; after the current page is developed, error collection is carried out based on variable objects bound with the components, and complete error prompt is carried out in a console, wherein the error prompt comprises component names, component IDs, event names, action names and error information, and the corresponding components can be quickly selected by clicking the component IDs.
Description
Technical Field
The invention belongs to the technical field of low-code development, and particularly relates to an instant error prompt method and system for a low-code development platform.
Background
The statements in this section merely provide background information related to the present disclosure and may not necessarily constitute prior art.
Currently, low-code development platforms have become hot spots in the industry, and various low-code development platforms are continuously emerged in the market. In the face of increasingly complex market demands, the requirements for low-code platforms are increasingly high, simple scene quick construction needs to be met, and complex scene construction needs to be supported. The complex scene certainly has less various configurations, the configurations are more, a user may forget some configuration items, the missing of the configuration items may cause the published page program to be unavailable, and the user can only return to the designer to reconfigure the missing items again, so that it is very necessary to have a timely error prompt in a low-code development environment, but the inventor finds that the low-code platform in the market still has the following defects:
(1) a timely error prompt mechanism is not provided, and the error prompt needs to be triggered when the page is stored, so that a coder needs to reposition and search for an error position.
(2) The error prompt adopts pop-up window prompt, the display time is short, the memory is difficult, the existing error prompt logic is disordered, and a user is difficult to position an error position according to the error prompt, so that the modification efficiency is low.
Disclosure of Invention
The invention provides an instant error prompt method and system for a low-code development platform, aiming at solving the problems, the scheme is based on a classification check mode, the instant check is respectively carried out on different types of operations of different operation objects, the error condition of the check result is fed back to a user in an instant mode through a control console, the user is guided to correct the problems in time, the condition of prompt lag is effectively avoided, the user experience is improved, and the condition that a page program cannot be used after being issued can be effectively reduced.
According to a first aspect of the embodiments of the present invention, there is provided an immediate error prompt method for a low-code development platform, including:
classifying different operation objects based on code development, wherein the operation objects comprise development of components, resources, editors and event operation objects;
receiving a current development action signal, judging the type of an operation object, respectively carrying out verification processing based on the type of the operation object, and carrying out error prompt on a console interface based on a verification result; meanwhile, the error prompt is respectively stored in different variable objects based on the operation object type and is bound with the corresponding component;
after the current page is developed, error collection is carried out based on variable objects bound with the components, and complete error prompt is carried out in a console, wherein the error prompt comprises component names, component IDs, event names, action names and error information, and the corresponding components can be quickly selected by clicking the component IDs.
Further, by clicking the component ID in the error prompt, the component corresponding to the error prompt can be located.
Further, the error prompt is displayed in a hierarchical manner, and the hierarchical manner classifies the error prompt into a warning class and an error class based on whether page publishing, compiling or running is affected.
Further, for the component operation object type, based on preset check rules and component operation types, correspondingly performing rollback check on addition, deletion, copy or cancellation of the component; for the resource operation object type, correspondingly deleting or issuing the resource based on a preset check rule and a resource operation type; for the type of an operation object of the editor, based on the field edited by the editor currently, carrying out real-time verification on the current field according to a preset verification rule; for the event operation object type, correspondingly performing event addition, deletion, action parameter modification and dynamic event verification based on a preset verification rule and an event operation type;
further, the component operation types comprise component addition, component deletion, component copying and component rollback checking.
Further, the resource operation type includes resource deletion and resource publishing, wherein the resource includes a workflow, a data model and a page.
Further, the event operation types include event addition, event deletion, action parameter modification and dynamic events.
According to a second aspect of the embodiments of the present invention, there is provided an immediate error prompt system for a low-code development platform, including:
the classification unit is used for classifying different operation objects based on code development, wherein the operation objects comprise development of components, resources, editors and event operation objects;
the real-time checking and error prompting unit is used for receiving the current development action signal, judging the operation object type of the current development action signal, respectively checking the operation object type of the current development action signal based on the operation object type of the current development action signal, and performing error prompting on a console interface based on a checking result; meanwhile, the error prompt is respectively stored in different variable objects based on the operation object type and is bound with the corresponding component;
and the error complete display unit is used for carrying out error collection based on the variable object bound with the component and carrying out complete error prompt in the console after the current page is developed, wherein the error prompt comprises a component name, a component ID, an event name, an action name and error information, and the corresponding component can be quickly selected by clicking the component ID.
According to a third aspect of the embodiments of the present invention, there is provided an electronic device, including a memory, a processor, and a computer program stored in the memory and running on the memory, where the processor implements the method for prompt error notification for a low-code development platform when executing the program.
According to a fourth aspect of the embodiments of the present invention, there is provided a non-transitory computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the method for immediate error notification for a low code development platform.
Compared with the prior art, the invention has the beneficial effects that:
(1) the invention provides an instant error prompting method and system for a low-code development platform, wherein the scheme is based on a classification check mode, different types of operations of different operation objects are respectively checked in an instant mode, error conditions of check results are fed back to a user in an instant mode through a control console, the user is guided to correct problems in time, the condition of prompt lag is effectively avoided, user experience is improved, and the condition that a page program cannot be used after being issued can be effectively reduced.
(2) According to the scheme, the component ID in the error prompt is strongly associated with the corresponding component, when the error prompt is clicked, the component with the error can be directly positioned, and the positioning efficiency of the error position is improved.
Advantages of additional aspects of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, are included to provide a further understanding of the invention, and are incorporated in and constitute a part of this specification, illustrate exemplary embodiments of the invention and together with the description serve to explain the invention and not to limit the invention.
FIG. 1 is a flowchart of an instant error prompt method for a low code development platform according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of an error information collection process according to an embodiment of the present invention;
fig. 3 is a detailed flowchart of an instant error prompt method for a low code development platform according to an embodiment of the present invention.
Detailed Description
The invention is further described with reference to the following figures and examples.
It is to be understood that the following detailed description is exemplary and is intended to provide further explanation of the invention as claimed. Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs.
It is noted that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of exemplary embodiments according to the invention. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, and it should be understood that when the terms "comprises" and/or "comprising" are used in this specification, they specify the presence of stated features, steps, operations, devices, components, and/or combinations thereof, unless the context clearly indicates otherwise.
The embodiments and features of the embodiments of the present invention may be combined with each other without conflict.
The first embodiment is as follows:
the embodiment aims at providing an instant error prompting method for a low-code development platform.
An immediate error prompt method for a low code development platform, comprising:
classifying different operation objects based on code development, wherein the operation objects comprise development of components, resources, editors and event operation objects;
receiving a current development action signal, judging the type of an operation object, respectively carrying out verification processing based on the type of the operation object, and carrying out error prompt on a console interface based on a verification result; meanwhile, the error prompt is respectively stored in different variable objects based on the operation object type and is bound with the corresponding component;
after the current page is developed, error collection is carried out based on variable objects bound with the components, and complete error prompt is carried out in a console, wherein the error prompt comprises component names, component IDs, event names, action names and error information, and the corresponding components can be quickly selected by clicking the component IDs.
Further, by clicking the component ID in the error prompt, the component corresponding to the error prompt can be located.
Further, the error prompt is displayed in a hierarchical manner, and the hierarchical manner classifies the error prompt into a warning class and an error class based on whether page publishing, compiling or running is affected.
Further, for the component operation object type, based on preset check rules and component operation types, correspondingly performing rollback check on addition, deletion, copy or cancellation of the component; for the resource operation object type, correspondingly deleting or issuing the resource based on a preset check rule and a resource operation type; for the type of an operation object of the editor, based on the field edited by the editor currently, carrying out real-time verification on the current field according to a preset verification rule; for the event operation object type, correspondingly performing event addition, deletion, action parameter modification and dynamic event verification based on a preset verification rule and an event operation type;
further, the component operation types comprise component addition, component deletion, component copying and component rollback checking.
Further, the resource operation type includes resource deletion and resource publishing, wherein the resource includes a workflow, a data model and a page.
Further, the event operation types include event addition, event deletion, action parameter modification and dynamic events.
Specifically, for the convenience of understanding, the scheme of the present embodiment is described in detail below with reference to specific examples:
based on the problems in the prior art, the present embodiment provides an immediate error prompt method for a low-code development platform, including:
step 1: classifying different operation objects based on code development, wherein the operation objects comprise components, resources, editors and event operation objects;
step 2: receiving a current development action signal, judging the type of an operation object, respectively carrying out verification processing based on the type of the operation object, and carrying out error prompt on a console interface based on a verification result; meanwhile, the error prompt is respectively stored in different variable objects of the components based on the operation object types and is bound with the corresponding components;
the checking process is respectively performed based on the operation object types, and specifically includes:
(1) for the component operation object type, correspondingly performing backspacing verification of adding, deleting, copying or canceling components based on preset verification rules and component operation types; the method specifically comprises the following steps:
1) and verifying after the component is added. After a component is added to a canvas, the component addition event is executed, a periodic function [ onAdd ] of the current component is called in the event addition, in the method, some methods defined on the component can be cited to realize verification, for example, a form is taken as an example, the form is output after being added to the canvas to prompt a user to add a form column, only two steps are needed, a verification method is configured on the form component, and then the method is introduced into the onAdd method of the form component.
2) And checking after the component is deleted. Taking a clear value action (for example, clearing a value of an input box after clicking) as an example, in a low-code platform, a component to be executed with a clear value needs to be manually selected, once the component is deleted, an error is reported after a program is issued, so that after the component is deleted, the selected component needs to be prompted to be absent, the clear value action is positioned according to the incidence relation recorded when the component is selected, and verification is performed again.
3) The component is checked after being copied. Or taking a clearing value action as an example, in a page 1, configuring a clearing value action for a button clicking event, selecting an input box by a clearing component, copying a button and pasting the button to a page 2, wherein the input box is not arranged in the page 2, in order to not report an error, the component selected by the clearing value action of a new page button is set to be empty, and meanwhile, a console outputs prompt information to prompt a user to select the clearing component.
4) And verifying after the component withdraws rollback. If the value action selection component is cleared, the component is deleted, the console prompts that the component does not exist, at this time, the revocation operation is executed, the revocation method is verified again, and the console clears the error prompt.
(2) For the resource operation object type, correspondingly deleting or issuing the resource based on a preset check rule and a resource operation type; the method specifically comprises the following steps:
1) and checking after the resources are deleted. Common resources such as workflows, data models, pages and the like, when a list page is drawn, a form needs to be associated with the data models to obtain data, a form page needs to be opened by adding a button, and when the resources or a folder where the resources are located are manually deleted on a resource management panel, the condition that the component associated resources do not exist is prompted on a console, and the resources are selected again.
2) And checking before the resource is released. If the page is associated with the data model, but the model may be modified, in order to ensure that the program can run, the referenced resources are checked again before the page is issued, on one hand, whether the resources exist is checked, on the other hand, an error checking method defined by the resources is called, and the change or the error of the resources is found in time.
(3) For the type of an operation object of the editor, based on the field edited by the editor currently, carrying out real-time verification on the current field according to a preset verification rule; the method specifically comprises the following steps: and checking by an editor in real time. After the configuration of the editor is modified, a verification method corresponding to the field is dynamically acquired according to the field currently edited by the editor, and the modified value of the editor is transmitted to be verified.
(4) For the event operation object category, correspondingly performing event addition, deletion, action parameter modification and dynamic event verification based on a preset verification rule and an event operation type; specifically, the method comprises the following steps:
1) and checking after adding or deleting events, conditions and actions. Such verification is typically a guided verification, which informs the user of the next operation in advance. If the event is newly added, triggering an afterEventAdd method, judging whether the event has a child node or not, and if the event does not have the child node, prompting that the event lacks action or condition, if the event is newly added, triggering an afterActionAdd method, deleting the prompt that the parent-level event does not have action in the method, and simultaneously outputting the prompt that the current action parameter is not configured.
2) And the action parameter modification is verified in real time. Such checks are like editor real-time checks, each action defining its own check method. And after the parameters are modified, triggering a parameter modification event, calling a verification method corresponding to the action in the event, and outputting error information in the console.
3) And checking the dynamic event. Some events do not exist in the event panel, and only after a certain configuration is started, the corresponding event can occur in the event panel. And after the configuration is started, prompting a user to configure on an event panel, and after the event panel configures the event, closing the configuration and prompting the user that the event source cannot be found.
Further, the location of the error storage may vary based on the operating scenario. The error storage locations include component errors (instanceErrors), functional errors (properrors), data errors (datasErrors), interactive errors (interactionsErrors), event errors (errorMsgs), action parameter errors (paramErrors), and conditional errors (errorMessage). And after the error is checked, creating an error prompt object, and storing the error prompt object to different positions according to the operation scene.
Checking the resource operation class: deleting the resource, acquiring the reference information of the resource, traversing the reference information, calling a reference check method according to the reference information, identifying that the resource does not exist, storing the resource at a corresponding error position of the component, and outputting.
Checking the component operation class: the component performs deletion operation, acquires the reference information of the component, traverses the reference information, calls a reference checking method according to the reference information, identifies that the component does not exist, and stores the component in a corresponding error position, and outputs the result.
And (3) verifying the editor operation class: the method comprises the steps of editor modification configuration, trigger value changing, field checking defined in a field acquisition component corresponding to an editor, verification executing, error storing, and outputting.
Event operation class checking: parameter modification configuration, parameter change triggering, action unified checking (defined in each action), verification execution, error, event action stored in the component, and output.
And step 3: after the current page is developed, error collection is carried out based on variable objects bound with the components, and complete error prompt is carried out in a console, wherein the error prompt comprises component names, component IDs, event names, action names and error information, and the corresponding components can be quickly selected by clicking the component IDs.
Further, the error collection specifically includes:
the errors are stored on the component in a scattered manner, and if all error prompts of the current page are to be displayed in a centralized manner, error information on the component needs to be collected and stored according to the page. The method for collecting error prompts by the self-expansion of the component mainly collects error prompts stored by variable objects bound with the component. Collecting error information is also divided into scenes, error prompts (see a collection flow in figure 2) left after a page is edited last time are required to be collected after the page is opened, after a pasted component is copied, if the copied component has errors, the pasted component should have error prompts, and the same reason is also achieved after a custom component is added.
Further, the displaying in the console specifically includes:
the console can simultaneously display Error prompts of different levels, such as Warning class (Warning) and Error class (Error), the Warning class prompts generally indicate that the code has problems, but the issue, compilation and operation of the page cannot be influenced, and the Error class prompts can be ignored.
The prompt information output by the console is clear, and when any error prompt is clicked, the error component can be quickly positioned according to the component information recorded in the prompt information.
The console displays all error prompts of the current page in a list mode, and different types of error prompts can be screened through the top navigation bar. The error prompt component comprises a component name, a component ID, an event name, an action name, a specific error and the like, and a user can clearly know where the error exists by looking at the component name, the component ID, the event name, the action name, the specific error and the like. Meanwhile, the function of clicking the error positioning component is provided (namely, the component ID in the error prompt and the corresponding component are associated), when an error is clicked, the component ID of the current error record is obtained, the canvas selected value is set as the current component, so that the component is positioned on the canvas in a highlighting mode, specifically, the corresponding component is obtained when the component ID is clicked through the strong association between the component ID and the corresponding component, and the specific position of the error component in the page is obtained based on the position information stored in the component.
Further, the method provides a concept of configuration states, wherein the configuration states are divided into 3 types, configured, unconfigured and error, the configured type means that all the required items are configured completely, the unconfigured type means that all the items are not configured, and the error type means that the configuration does not meet the rules or the required items are not completed. Changes to the configuration state typically occur after a user modifies an editor value or a configuration event action parameter.
Specifically, to further explain the scheme of this embodiment, the following takes event verification as an example to explain the working process of the scheme of this embodiment in detail:
when a user creates an event, error verification is immediately triggered, the user is informed of 'action or condition required under the event', an error prompt is created and stored in the event error, then error information is collected and output and displayed on a console; when a user creates an action, error checking is immediately triggered, the user is informed in advance that the current action lacks XX parameters, error information is stored in parameter errors, and then the error information is collected and output and displayed on a console; meanwhile, deleting error prompt in the event because the event has an action; after the user configures the action parameters, error checking is carried out according to the rules, if the rules are met, the action configuration state is changed into configured, meanwhile, error prompts in the parameters are deleted, and the parameters are selected at the moment; after the user deletes the parameter-quoted component, manually triggering the action to perform error check again according to the position information quoted and recorded, finding that the parameter does not exist, creating an error prompt, storing the error prompt into the parameter error, collecting error information at the same time, and outputting the error information at the console.
Example two:
the embodiment aims to provide an instant error prompt system for a low-code development platform.
An immediate error prompt system for a low code development platform, comprising:
the classification unit is used for classifying different operation objects based on code development, wherein the operation objects comprise development of components, resources, editors and event operation objects;
the real-time checking and error prompting unit is used for receiving the current development action signal, judging the operation object type of the current development action signal, respectively checking the operation object type of the current development action signal based on the operation object type of the current development action signal, and performing error prompting on a console interface based on a checking result; meanwhile, the error prompt is respectively stored in different variable objects based on the operation object type and is bound with the corresponding component;
and the error complete display unit is used for carrying out error collection based on the variable object bound with the component and carrying out complete error prompt in the console after the current page is developed, wherein the error prompt comprises a component name, a component ID, an event name, an action name and error information, and the corresponding component can be quickly selected by clicking the component ID.
Further, the system of the present embodiment corresponds to the method of the first embodiment, and the technical details thereof have been described in detail in the first embodiment, so that the details are not repeated herein.
In further embodiments, there is also provided:
an electronic device comprising a memory and a processor, and computer instructions stored on the memory and executed on the processor, the computer instructions when executed by the processor performing the method of embodiment one. For brevity, no further description is provided herein.
It should be understood that in this embodiment, the processor may be a central processing unit CPU, and the processor may also be other general purpose processors, digital signal processors DSP, application specific integrated circuits ASIC, off-the-shelf programmable gate arrays FPGA or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and so on. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory may include both read-only memory and random access memory, and may provide instructions and data to the processor, and a portion of the memory may also include non-volatile random access memory. For example, the memory may also store device type information.
A computer readable storage medium storing computer instructions which, when executed by a processor, perform the method of embodiment one.
The method in the first embodiment may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and software modules in the processor. The software modules may be located in ram, flash, rom, prom, or eprom, registers, among other storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor. To avoid repetition, it is not described in detail here.
Those of ordinary skill in the art will appreciate that the various illustrative elements, i.e., algorithm steps, described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
The method and the system for prompting the immediate error for the low-code development platform can be realized, and have wide application prospect.
The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (10)
1. An immediate error prompt method for a low code development platform, comprising:
classifying different operation objects based on code development, wherein the operation objects comprise development of components, resources, editors and event operation objects;
receiving a current development action signal, judging the type of an operation object, respectively carrying out verification processing based on the type of the operation object, and carrying out error prompt on a console interface based on a verification result; meanwhile, the error prompt is respectively stored in different variable objects based on the operation object type and is bound with the corresponding component;
after the current page is developed, error collection is carried out based on variable objects bound with the components, and complete error prompt is carried out in a console, wherein the error prompt comprises component names, component IDs, event names, action names and error information, and the corresponding components can be quickly selected by clicking the component IDs.
2. The method of claim 1, wherein the component corresponding to the error prompt can be located by clicking on a component ID in the error prompt.
3. The method of claim 1, wherein the error hints are presented in a hierarchical manner that classifies error hints into warning and error classes based on whether page publication, compilation, or execution is affected.
4. The immediate error prompt method for the low-code development platform according to claim 1, wherein for the component operation object category, based on a preset check rule and a component operation type, a rollback check of adding, deleting, copying or revoking the component is correspondingly performed; for the resource operation object type, correspondingly deleting or issuing the resource based on a preset check rule and a resource operation type; for the type of an operation object of the editor, based on a field currently edited by the editor, carrying out real-time verification on the current field according to a preset verification rule; and for the event operation object type, correspondingly performing event addition, deletion, action parameter modification and dynamic event verification based on a preset verification rule and an event operation type.
5. The method of claim 4, wherein the component operation types comprise component addition, component deletion, component replication, and component rollback checking.
6. The method of claim 4, wherein the resource operation types comprise resource deletion and resource release, and wherein the resources comprise workflows, data models and pages.
7. The method as claimed in claim 4, wherein the event operation types include event addition, event deletion, action parameter modification and dynamic event.
8. An immediate error prompt system for a low code development platform, comprising:
the classification unit is used for classifying different operation objects based on code development, wherein the operation objects comprise development of components, resources, editors and event operation objects;
the real-time checking and error prompting unit is used for receiving the current development action signal, judging the operation object type of the current development action signal, respectively checking the operation object type of the current development action signal based on the operation object type of the current development action signal, and performing error prompting on a console interface based on a checking result; meanwhile, the error prompt is respectively stored in different variable objects based on the operation object type and is bound with the corresponding component;
and the error complete display unit is used for carrying out error collection based on the variable object bound with the component and carrying out complete error prompt in the console after the current page is developed, wherein the error prompt comprises a component name, a component ID, an event name, an action name and error information, and the corresponding component can be quickly selected by clicking the component ID.
9. An electronic device comprising a memory, a processor and a computer program stored and run on the memory, wherein the processor implements a method of immediate error notification for a low code development platform as claimed in any one of claims 1 to 7 when executing the program.
10. A non-transitory computer readable storage medium having stored thereon a computer program, wherein the program when executed by a processor implements a method for immediate error alerting for a low code development platform as claimed in any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210755238.XA CN114816373B (en) | 2022-06-30 | 2022-06-30 | Instant error prompt method and system for low-code development platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210755238.XA CN114816373B (en) | 2022-06-30 | 2022-06-30 | Instant error prompt method and system for low-code development platform |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114816373A true CN114816373A (en) | 2022-07-29 |
| CN114816373B CN114816373B (en) | 2022-09-16 |
Family
ID=82522372
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210755238.XA Active CN114816373B (en) | 2022-06-30 | 2022-06-30 | Instant error prompt method and system for low-code development platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114816373B (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100153913A1 (en) * | 2008-12-16 | 2010-06-17 | Sap Ag | Systems and Methods for Executing Object-Oriented Programming Code Invoking Pre-Existing Objects |
| CN104899027A (en) * | 2015-05-22 | 2015-09-09 | 国云科技股份有限公司 | Universal form verification method for js |
| CN106940640A (en) * | 2016-01-04 | 2017-07-11 | 阿里巴巴集团控股有限公司 | A kind of page positioning method and device for mistake input information |
| CN110489091A (en) * | 2019-08-22 | 2019-11-22 | 辽东学院 | A kind of software development process method for managing and monitoring and system |
| US20190384370A1 (en) * | 2019-08-30 | 2019-12-19 | Jason Seung-Min Kim | Software assisted power management |
| CN112685039A (en) * | 2021-01-19 | 2021-04-20 | 金现代信息产业股份有限公司 | Configuration method and device of low-code development platform |
| CN114491206A (en) * | 2022-01-04 | 2022-05-13 | 电子科技大学 | General low-code crawler method and system for news blog websites |
-
2022
- 2022-06-30 CN CN202210755238.XA patent/CN114816373B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100153913A1 (en) * | 2008-12-16 | 2010-06-17 | Sap Ag | Systems and Methods for Executing Object-Oriented Programming Code Invoking Pre-Existing Objects |
| CN104899027A (en) * | 2015-05-22 | 2015-09-09 | 国云科技股份有限公司 | Universal form verification method for js |
| CN106940640A (en) * | 2016-01-04 | 2017-07-11 | 阿里巴巴集团控股有限公司 | A kind of page positioning method and device for mistake input information |
| CN110489091A (en) * | 2019-08-22 | 2019-11-22 | 辽东学院 | A kind of software development process method for managing and monitoring and system |
| US20190384370A1 (en) * | 2019-08-30 | 2019-12-19 | Jason Seung-Min Kim | Software assisted power management |
| CN112685039A (en) * | 2021-01-19 | 2021-04-20 | 金现代信息产业股份有限公司 | Configuration method and device of low-code development platform |
| CN114491206A (en) * | 2022-01-04 | 2022-05-13 | 电子科技大学 | General low-code crawler method and system for news blog websites |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114816373B (en) | 2022-09-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN114115857B (en) | Machine learning model automatic production line construction method and system | |
| US6415396B1 (en) | Automatic generation and maintenance of regression test cases from requirements | |
| Verbeek et al. | Analyzing BPEL processes using Petri nets | |
| US8621417B2 (en) | Rule merging in system for monitoring adherence by developers to a software code development process | |
| Klein et al. | Weaving multiple aspects in sequence diagrams | |
| CN110928772A (en) | Test method and device | |
| JP2018501538A (en) | Impact analysis | |
| KR101597780B1 (en) | Method and apparatus for visually implementing software code | |
| US9052845B2 (en) | Unified interface for meta model checking, modifying, and reporting | |
| WO2022188780A1 (en) | Visual software development system, method and apparatus, and computer storage medium | |
| Gómez et al. | Cardinality-Based Feature Modeling and Model-Driven Engineering: Fitting them Together. | |
| US8949203B1 (en) | Verification of design libraries and databases | |
| da Silva et al. | Dynamic plans for integration testing of self-adaptive software systems | |
| US8527254B2 (en) | Simulator engine development system and simulator engine development method | |
| CN106600226A (en) | Method and device used for optimizing flow management system | |
| CN114816373B (en) | Instant error prompt method and system for low-code development platform | |
| US9110763B2 (en) | Highlighting changes on computer diagrams | |
| Speth | Issue management for multi-project, multi-team microservice architectures | |
| Silva Filho et al. | Supporting concern-based regression testing and prioritization in a model-driven environment | |
| US7076779B2 (en) | System for controlling and monitoring a process | |
| CN116974537A (en) | Component-based product development method, device, computer equipment and storage medium | |
| CN116415094A (en) | Page embedded point reporting method and device, electronic equipment and storage medium | |
| JPH11224186A (en) | Device and method for analyzing software | |
| CN111949267B (en) | UI front end generation method and device | |
| CA2739762C (en) | Rule merging in system for monitoring adherence by developers to a software code development process |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |