Low-code development method and device, readable storage medium, and electronic device

Abstract

The present disclosure belongs to the technical field of Internet software development, and relates to a low-code development method and device, a readable storage medium and an electronic device. The method comprises the following steps: determining a target metadata language template, identifying a target metadata language corresponding to the target metadata language template; analyzing the target metadata language to obtain action information, identifying the action information to obtain a type identification result; and distributing the action information to a front-end page or a back-end system according to the type identification result, so as to execute an action corresponding to the action information in the front-end page or the back-end system. In the present disclosure, the target metadata language is obtained, the target metadata language is analyzed to obtain the action information, and the action information is distributed according to the type identification result obtained by identifying the action information. Compared with the prior art, the target metadata language can be developed by mixing the front end and the back end, the situation that the front end and the back end are developed separately is avoided, the development cycle is shortened, and the development efficiency is improved.

Description

Technical Field

[0001] This disclosure relates to the field of Internet software technology, and in particular to a low-code development method and apparatus, a computer-readable storage medium, and an electronic device. Background Technology

[0002] Low-code development technology reduces the workload and difficulty of code development for developers with varying levels of experience, making it easier and more efficient to create applications.

[0003] In existing technologies, front-end and back-end are generally developed separately. Due to the high development threshold, business personnel cannot participate in the development. Moreover, front-end developers do not have the ability to develop back-end developers, and vice versa. Therefore, the development cycle is increased, the development efficiency is reduced, and it is impossible to adapt to the changing speed of actual development needs.

[0004] Therefore, there is an urgent need in this field to develop a new low-code development method and apparatus.

[0005] It should be noted that the information disclosed in the background section above is only used to enhance the understanding of the background of this disclosure, and therefore may include information that does not constitute prior art known to those skilled in the art. Summary of the Invention

[0006] The purpose of this disclosure is to provide a low-code development method, a low-code development apparatus, a computer-readable storage medium, and an electronic device, thereby overcoming, at least to some extent, the problems of long development cycles and low development efficiency caused by related technologies.

[0007] Other features and advantages of this disclosure will become apparent from the following detailed description, or may be learned in part from practice of this disclosure.

[0008] According to a first aspect of the present invention, a low-code development method is provided, the method comprising: determining a target metadata language template; identifying a target metadata language corresponding to the target metadata language template; the target metadata language being a low-code metadata language written based on the target metadata language template; the target metadata language being a low-code metadata language; parsing the target metadata language to obtain action information; identifying the action information to obtain a type identification result; and distributing the action information to a front-end page or a back-end system according to the type identification result, so as to execute an action corresponding to the action information on the front-end page or the back-end system.

[0009] In an exemplary embodiment of the present invention, determining the target metadata language template includes: if a selection instruction is obtained, determining the target metadata language template corresponding to the selection instruction from a plurality of preset metadata language templates.

[0010] In an exemplary embodiment of the present invention, the target metadata language includes metadata language blocks; the metadata language blocks include block types and action events; parsing the target metadata language to obtain action information includes: parsing the metadata language blocks to obtain the block types and the action events; and parsing the event content corresponding to the action events to obtain action information.

[0011] In an exemplary embodiment of the present invention, the action information includes an action identifier and an action type corresponding to the action identifier; the step of parsing the event content corresponding to the action event to obtain the action information includes: parsing the event content corresponding to the action event to obtain the action identifier included in the action content and the action type corresponding to the action identifier.

[0012] In an exemplary embodiment of the present invention, the step of identifying the action information to obtain a type identification result includes: identifying the action type in the action information to obtain a type identification result.

[0013] In an exemplary embodiment of the present invention, the step of distributing the action information to a front-end page or a back-end system according to the type identification result includes: if the type identification result is a first type result corresponding to the front-end page, then the action information is distributed to the front-end page; if the type identification result is a second type result corresponding to the back-end system, then the action information is distributed to the back-end system.

[0014] In an exemplary embodiment of the present invention, the step of performing an action corresponding to the action information on the front-end page or the back-end system includes: combining the action identifier, the action type corresponding to the action identifier, and the block type to perform a corresponding action on the front-end page or the back-end system; the block type is used to identify the component type, and the component is used to be responsible for the display of the action and user interaction.

[0015] According to a second aspect of the present invention, a low-code development apparatus is provided, the apparatus comprising: an identification module configured to determine a target metadata language template and identify a target metadata language corresponding to the target metadata language template; the target metadata language being a low-code metadata language written based on the target metadata language template; a parsing module configured to parse the target metadata language to obtain action information and to identify the action information to obtain a type identification result; and a distribution module configured to distribute the action information to a front-end page or a back-end system according to the type identification result, so as to execute an action corresponding to the action information on the front-end page or the back-end system.

[0016] According to a third aspect of the present invention, an electronic device is provided, comprising: a processor and a memory; wherein the memory stores computer-readable instructions, which, when executed by the processor, implement the low-code development method of any of the above exemplary embodiments.

[0017] According to a fourth aspect of the present invention, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the low-code development method in any of the above exemplary embodiments.

[0018] As can be seen from the above technical solutions, the low-code development method, low-code development apparatus, computer storage medium, and electronic device in the exemplary embodiments of the present invention have at least the following advantages and positive effects:

[0019] In the methods and apparatus provided by the exemplary embodiments of this disclosure, on the one hand, the target metadata language is a low-code metadata language, which allows business personnel to write the target metadata language according to their needs, avoiding the situation in the prior art where business personnel cannot participate in development; on the other hand, the target metadata language is obtained, the target metadata language is parsed to obtain action information, and the action information is distributed according to the type identification result obtained by identifying the action information. Compared with the prior art, the target metadata language can be developed in a hybrid front-end and back-end manner, avoiding the situation where the front-end and back-end are developed separately, shortening the development cycle, improving development efficiency, and thus increasing the degree of adaptability to actual development needs.

[0020] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0021] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure. It is obvious that the drawings described below are merely some embodiments of this disclosure, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort.

[0022] Figure 1 The schematic diagram illustrates a flowchart of the low-code development method in an embodiment of this disclosure;

[0023] Figure 2 This illustration schematically shows a preset metadata language template X-1 in an embodiment of the present disclosure;

[0024] Figure 3 This illustration shows a flowchart of parsing a target metadata language to obtain action information in a low-code development method according to an embodiment of the present disclosure.

[0025] Figure 4 This illustration shows a flowchart of the low-code development method according to an embodiment of the present disclosure, in which action information is distributed to a front-end page or a back-end system.

[0026] Figure 5 This illustration schematically shows the prompt information displayed on the front-end page in the low-code development method of this disclosure embodiment;

[0027] Figure 6 This diagram illustrates the application management interface in the low-code development method of this disclosure embodiment.

[0028] Figure 7 A flowchart illustrating a low-code development method in an application scenario is provided.

[0029] Figure 8 This schematic diagram illustrates the structure of a low-code development apparatus according to an embodiment of the present disclosure;

[0030] Figure 9 An electronic device for a low-code development method is illustrated schematically in an embodiment of this disclosure;

[0031] Figure 10 The illustration schematically depicts a computer-readable storage medium for a low-code development method according to an embodiment of the present disclosure. Detailed Implementation

[0032] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided to make this disclosure more comprehensive and complete, and to fully convey the concept of the example embodiments to those skilled in the art. The described features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a full understanding of embodiments of this disclosure. However, those skilled in the art will recognize that the technical solutions of this disclosure can be practiced with one or more of the specific details omitted, or other methods, components, apparatus, steps, etc., can be employed. In other instances, well-known technical solutions are not shown or described in detail to avoid obscuring various aspects of this disclosure.

[0033] The terms “a,” “an,” “the,” and “the” are used in this specification to indicate the presence of one or more elements / components / etc.; the terms “including” and “having” are used to indicate an open-ended inclusion and to mean that there may be other elements / components / etc. in addition to the listed elements / components / etc.; the terms “first” and “second” are used only as markings and are not a limitation on the number of objects.

[0034] Furthermore, the accompanying drawings are merely illustrative of this disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and therefore repeated descriptions of them will be omitted. Some block diagrams shown in the drawings are functional entities and do not necessarily correspond to physically or logically independent entities.

[0035] In response to the problems existing in related technologies, this disclosure proposes a low-code development method. Figure 1 A flowchart illustrating the low-code development methodology is shown, such as... Figure 1 As shown, the low-code development method includes at least the following steps:

[0036] Step S110. Determine the target metadata language template and identify the target metadata language corresponding to the target metadata language template; the target metadata language is a low-code metadata language written based on the target metadata language template.

[0037] Step S120. Parse the target metadata language to obtain action information, and identify the action information to obtain type identification results.

[0038] Step S130. Based on the type recognition result, distribute the action information to the front-end page or back-end system to execute the action corresponding to the action information on the front-end page or back-end system.

[0039] In the methods and apparatus provided by the exemplary embodiments of this disclosure, on the one hand, the target metadata language is a low-code metadata language, which allows business personnel to write the target metadata language according to their needs, avoiding the situation in the prior art where business personnel cannot participate in development; on the other hand, the target metadata language is obtained, the target metadata language is parsed to obtain action information, and the action information is distributed according to the type identification result obtained by identifying the action information. Compared with the prior art, the target metadata language can be developed in a hybrid front-end and back-end manner, avoiding the situation where the front-end and back-end are developed separately, shortening the development cycle, improving development efficiency, and thus increasing the degree of adaptability to actual development needs.

[0040] The following section provides a detailed explanation of each step in the low-code development method.

[0041] In step S110, the target metadata language template is determined, and the target metadata language corresponding to the target metadata language template is identified; the target metadata language is a low-code metadata language written based on the target metadata language template.

[0042] In an exemplary embodiment of this disclosure, the target metadata language template refers to a pre-set template provided to developers or business personnel for reference when writing low-code metadata language (i.e., writing target metadata language).

[0043] The target metadata language refers to a low-code metadata language written by developers or business personnel. Specifically, the target metadata language can be a YAML (YAML Are Not a Markup Language) format metadata language, an XML (eXtensible Markup Language) format metadata language, a JSON (JavaScript Object Notation) format metadata language, a C (The C Programming Language) format metadata language, or any other metadata language. This exemplary embodiment does not impose any special limitations on it.

[0044] Once the target metadata language template is determined, developers or business personnel can refer to the target metadata language template to write low-code metadata language. At this time, the low-code metadata language written by the developers or business personnel will be automatically recognized to form the target metadata language.

[0045] For example, the target metadata language template is determined, and the low-code target metadata language written by the developers is identified. It is worth noting that the target metadata language is written by the developers after referring to the target metadata language template, and the target metadata language can be in YAML format.

[0046] In an optional embodiment, determining the target metadata language includes: if a selection instruction is obtained, determining the target metadata language template corresponding to the selection instruction from a plurality of preset metadata language templates.

[0047] Since there are multiple metadata languages, there may be multiple preset metadata language templates. For example, there may be a preset metadata language template corresponding to the YAML metadata language, a preset metadata language template corresponding to the JSON metadata language, and a preset metadata language template corresponding to the XML metadata language. This exemplary embodiment does not impose any special limitations on this.

[0048] A selection instruction refers to an instruction issued by a developer or business user after triggering one of a plurality of preset metadata language templates. A selection instruction can also be an instruction issued by a developer or business user after triggering a template control. This exemplary embodiment does not impose any special limitations on this. Here, the trigger template control refers to the control corresponding to the preset metadata language template.

[0049] Once the selection instruction is received, the developer or business personnel can determine the template (i.e., the target metadata language template) needed from multiple preset metadata language templates.

[0050] For example, if a selection instruction A is obtained, the preset metadata language template X-1 corresponding to selection instruction A can be determined from multiple preset metadata language templates. Figure 2 The schematic illustration shows the preset metadata language template X-1, such as Figure 2 As shown, Block refers to a metadata language block, id refers to the block identifier (defined as a hexadecimal character) corresponding to the metadata language block, type refers to the block type of the metadata language block, and events refers to action events. In events, id refers to the action identifier (defined as a hexadecimal character), and type refers to the action type corresponding to the action identifier. Specifically, the action type can be the action type corresponding to the action of sending a message, the action type corresponding to the action of changing the page style, the action type corresponding to the action of reading and writing the database, or the action type corresponding to the action of calling the application interface. This exemplary embodiment does not impose any special limitations on this.

[0051] At this point, the developers write a low-code target metadata language based on the preset metadata language template. Specifically, the low-code target metadata language written by the developers can be as follows:

[0052] Block:

[0053] ID: "0000111111"

[0054] type: "graph"

[0055] events: {

[0056] id: "Verification"

[0057] type: "Validate"

[0058] ID: "New Application"

[0059] type: "Request"

[0060] }

[0061] In this exemplary embodiment, the target metadata language template can be determined from multiple preset metadata language templates according to the acquisition instruction, thus meeting the needs of business personnel or developers.

[0062] In step S120, the target metadata language is parsed to obtain action information, and the action information is identified to obtain type identification results.

[0063] In the exemplary embodiments of this disclosure, action information refers to information related to actions performed by a front-end page or a back-end system. Identifying the action information yields a type identification result, which determines whether the action was performed by the front-end page or the back-end system.

[0064] For example, parsing the target metadata language yields action information, specifically including the action type "message" and the corresponding action identifier "user reminder". Based on this, identifying the action information yields a type identification result; specifically, the type identification result indicates that the action type contained in the action information suggests that the action needs to be executed by the front-end page.

[0065] In an optional embodiment, Figure 3 This diagram illustrates the process of parsing a target metadata language to obtain action information in a low-code development methodology. The target metadata language includes metadata language blocks; each metadata language block includes a block type and an action event, such as... Figure 3 As shown, the method includes at least the following steps: In step S310, the metadata language block is parsed to obtain the block type and action event.

[0066] The target metadata language includes metadata language blocks, and within each metadata language block are block types and action events. Block types correspond to metadata language blocks and represent the type of component. Specifically, a block type can be a text box type, a button type, a dialog box type, or a chart type. The block type determines how data is displayed or how the user interacts with it. Action events describe events corresponding to actions performed by the front-end page or back-end system, and can include information related to the actions performed by the front-end page or back-end system.

[0067] For example, the target metadata language includes metadata language blocks. Parsing these metadata language blocks yields a block type of "graph". Parsing the metadata language blocks also yields action events, which record information related to actions performed by the front-end page or back-end system.

[0068] In step S320, the event content corresponding to the action event is parsed to obtain action information.

[0069] After receiving an action event, the corresponding action content can be determined. Further parsing of the action content yields action information, which refers to information related to the actions performed by the front-end page or back-end system.

[0070] For example, parsing the metadata language block yields action events. The event content corresponding to each action event includes: id: "User Reminder"; type: "Message". Based on this, further parsing the action content corresponding to the action event yields action information, which specifically includes an action identifier (i.e., id, with the value of id being "User Reminder") and an action type (i.e., type, with the value of type being "Message").

[0071] In this exemplary embodiment, the metadata language block is parsed to obtain the block type and action event, and then the action content corresponding to the action event is parsed to obtain the action information, which lays the foundation for obtaining the type recognition result in the future.

[0072] In an optional embodiment, the action information includes an action identifier and an action type corresponding to the action identifier; parsing the event content corresponding to the action event to obtain the action information includes: parsing the event content corresponding to the action event to obtain the action identifier included in the action content and the action type corresponding to the action identifier.

[0073] The action information includes an action identifier and the corresponding action type. The action type indicates whether the action is executed by the front-end page or the back-end system. The action identifier corresponds to the action type, and its specific execution content is revealed.

[0074] For example, the event content corresponding to an action event includes: id: "User Reminder"; type: "Message". Based on this, further parsing of the action event can yield action information, which specifically includes the action identifier (i.e., id, and the value of id is "User Reminder") and the action type (i.e., type, and the value of type is "Message").

[0075] In this exemplary embodiment, parsing the action content can yield the action identifier and the action type corresponding to the action identifier. This lays the foundation for subsequent identification of the action information to obtain the type identification result. Compared with the prior art, the target metadata language can be developed in a hybrid front-end and back-end manner, avoiding the situation of separate front-end and back-end development, shortening the development cycle, improving development efficiency, and thus increasing the degree of adaptability to actual development needs.

[0076] In an optional embodiment, identifying the action information to obtain a type identification result includes: identifying the action type in the action information to obtain a type identification result.

[0077] The action information includes the action type, and identifying the action type yields a type identification result. This type identification result determines whether the action information is distributed to the front-end page or the back-end system.

[0078] For example, by identifying the action type "Message" in the action information, a type identification result can be obtained. Specifically, the obtained type identification result is the first type result. Through the first type identification result, it can be known that the action information is the action information that needs to be distributed to the front-end page.

[0079] In this exemplary embodiment, the type identification result obtained by identifying the action information lays the foundation for the subsequent distribution of the action information. Compared with the prior art, the target metadata language can be developed in a hybrid front-end and back-end manner, avoiding the situation of separate front-end and back-end development, shortening the development cycle and improving development efficiency.

[0080] In step S130, based on the type recognition result, the action information is distributed to the front-end page or the back-end system so that the action corresponding to the action information can be executed on the front-end page or the back-end system.

[0081] In the exemplary embodiments of this disclosure, the type recognition result refers to the result obtained after recognizing the action type in the action information. Furthermore, there are two types of type recognition results: one type recognition result corresponds to the front-end page, and the other type recognition result corresponds to the back-end system.

[0082] Based on this, according to the type recognition results, action information can be sent to the front-end page or back-end system. Then, after the front-end page or back-end system obtains the action information, it executes the corresponding action.

[0083] For example, if the type identification result is the first type, and the first type corresponds to the front-end page, then the action information (id: "User Reminder"; type: "Message") is distributed to the front-end page. Based on this, the front-end page renders and generates a prompt message to remind the user.

[0084] In an optional embodiment, Figure 4 This illustrates a flowchart of the process of distributing action information to the front-end page or back-end system in a low-code development methodology, such as... Figure 4 As shown, the method includes at least the following steps: In step S410, if the type identification result is the first type result corresponding to the front-end page, the action information is distributed to the front-end page.

[0085] The action information includes the action type, which can be either the action type corresponding to the front-end page or the action type corresponding to the back-end system.

[0086] The first type of result indicates that the action type in the action information corresponds to the front-end page. Based on this, when the type recognition result is the first result, the action information needs to be sent to the front-end page so that the front-end page can execute the corresponding action in combination with the action information.

[0087] For example, if the type recognition result is the first type result Z-1 corresponding to the front-end page, then the action information (action identifier "user reminder" and the action type "Message" corresponding to the action identifier) ​​is sent to the front-end page to display a prompt message to the user in the form of a text box on the front-end page, so as to remind the user.

[0088] Figure 5 The illustration shows the prompt information displayed on the front-end page, such as... Figure 5 As shown, interface 510 is the terminal interface, and text box 520 is displayed in interface 510, which displays prompt information to remind the user.

[0089] In step S420, if the type identification result is the second type result corresponding to the backend system, the action information is sent to the backend system.

[0090] The second type of result indicates that the action type in the action information corresponds to the backend system. Based on this, when the type identification result is the second type, the action information needs to be sent to the backend system so that the backend system can execute the corresponding action in combination with the action information.

[0091] For example, if the type identification result is the second type result Z-2 corresponding to the backend system, the action information (action identifier "add application" and the action type "Request" corresponding to the action identifier) ​​is sent to the backend to write the action information into the database, and a new application is created at this time.

[0092] Figure 6 The diagram illustrates the application management interface, such as... Figure 6 As shown, interface 610 is the application management interface, and data 611 is the newly created application. Specifically, data 611 includes the name 621 of the newly created application, the creator of the application 622, the time of creation of the application 623, and the time of update of the application 624.

[0093] In this exemplary embodiment, action information is distributed to the front-end page or the back-end system based on the type recognition result. Compared with the prior art, the target metadata language can be developed in a hybrid manner between the front-end and back-end, avoiding the situation of separate development between the front-end and back-end, shortening the development cycle and improving development efficiency.

[0094] In an optional embodiment, the action corresponding to the action information is executed on the front-end page or the back-end system, including: combining the action identifier, the action type corresponding to the action identifier, and the block type to execute the corresponding action on the front-end page or the back-end system; the block type is used to identify the component type, and the component is used to be responsible for the display of the action and user interaction.

[0095] Among them, the block type corresponds to the metadata language block, and the block type represents the type of the component. Specifically, the block type can be the type of text box, the type of button, the type of dialog box, or the type of chart. The block type can determine how the data is displayed or how the user interacts with it.

[0096] For example, by combining the action identifier "user reminder", the corresponding action type "Message", and the block type "text box", we can know that a prompt message will be displayed to the user in the form of a text box on the front-end page to remind the user.

[0097] In this exemplary embodiment, by combining the action identifier, action type, and action block type, the corresponding action is executed on the front-end page or back-end system, thereby optimizing the execution effect when the corresponding action is executed.

[0098] In the methods and apparatus provided by the exemplary embodiments of this disclosure, on the one hand, the target metadata language is a low-code metadata language, which allows business personnel to write the target metadata language according to their needs, avoiding the situation in the prior art where business personnel cannot participate in development; on the other hand, the target metadata language is obtained, the target metadata language is parsed to obtain action information, and the action information is distributed according to the type identification result obtained by identifying the action information. Compared with the prior art, the target metadata language can be developed in a hybrid front-end and back-end manner, avoiding the situation where the front-end and back-end are developed separately, shortening the development cycle, improving development efficiency, and thus increasing the degree of adaptability to actual development needs.

[0099] The low-code development method in this embodiment will be described in detail below with reference to an application scenario.

[0100] Figure 7 This diagram illustrates a flowchart of a low-code development method in an application scenario, such as... Figure 7 As shown, module 710 is the action group parsing module, personnel 711 is the business personnel or developers, terminal 712 is the front-end page, and terminal 713 is the back-end system.

[0101] Step S721 involves sending a preset metadata language template to personnel 711, and step S731 involves obtaining the target metadata language. After obtaining the target metadata language in module 710, the target metadata language is parsed to obtain action information, and the action information is identified to obtain a type identification result. Step S741 involves distributing the action information to the front-end page 712 if the type identification result is a first type result; step S751 involves distributing the action information to the back-end system 713 if the type identification result is a second type result.

[0102] In this application scenario, on the one hand, the target metadata language is a low-code metadata language, which allows business personnel to write target metadata languages ​​according to their needs, avoiding the situation in existing technologies where business personnel cannot participate in development; on the other hand, by acquiring the target metadata language, parsing it to obtain action information, and distributing action information based on the type identification results obtained from identifying the action information, compared with existing technologies, the target metadata language can be developed in a hybrid front-end and back-end manner, avoiding the situation of separate front-end and back-end development, shortening the development cycle, improving development efficiency, and thus increasing the degree of adaptability to actual development needs.

[0103] Furthermore, in an exemplary embodiment of this disclosure, a low-code development apparatus is also provided. Figure 8 A schematic diagram of the low-code development device is shown, such as... Figure 8 As shown, the low-code development device 800 may include: an identification module 810, a parsing module 820, and a distribution module 830. Wherein:

[0104] The identification module 810 is configured to determine the target metadata language template and identify the target metadata language corresponding to the target metadata language template; the target metadata language is a low-code metadata language written based on the target metadata language template; the parsing module 820 is configured to parse the target metadata language to obtain action information and identify the action information to obtain a type identification result; the distribution module 830 is configured to distribute the action information to the front-end page or the back-end system according to the type identification result, so as to execute the action corresponding to the action information on the front-end page or the back-end system.

[0105] The specific details of the aforementioned low-code development device 800 have been described in detail in the corresponding low-code development method, so they will not be repeated here.

[0106] It should be noted that although several modules or units of the low-code development device 800 are mentioned in the detailed description above, this division is not mandatory. In fact, according to embodiments of this disclosure, the features and functions of two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.

[0107] Furthermore, in an exemplary embodiment of this disclosure, an electronic device capable of implementing the above-described method is also provided.

[0108] The following reference Figure 9 To describe an electronic device 900 according to such an embodiment of the present invention. Figure 9 The electronic device 900 shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of the present invention.

[0109] like Figure 9 As shown, the electronic device 900 is presented in the form of a general-purpose computing device. The components of the electronic device 900 may include, but are not limited to: at least one processing unit 910, at least one storage unit 920, a bus 930 connecting different system components (including storage unit 920 and processing unit 910), and a display unit 940.

[0110] The storage unit stores program code that can be executed by the processing unit 910, causing the processing unit 910 to perform the steps described in the "Exemplary Methods" section above, according to various exemplary embodiments of the present invention.

[0111] Storage unit 920 may include readable media in the form of volatile storage units, such as random access memory (RAM) 921 and / or cache memory 922, and may further include read-only memory (ROM) 923.

[0112] Storage unit 920 may also include a program / utility 924 having a set (at least one) of program modules 925, such program modules 925 including but not limited to: operating system, one or more application programs, other program modules and program data, each or some combination of these examples may contain the reality of the network environment.

[0113] Bus 930 can represent one or more of several types of bus structures, including a memory cell bus or memory cell controller, a peripheral bus, a graphics acceleration port, a processing unit, or a local bus using any of the various bus structures.

[0114] Electronic device 900 can also communicate with one or more external devices 970 (e.g., keyboard, pointing device, Bluetooth device, etc.), and with one or more devices that enable a user to interact with electronic device 900, and / or with any device that enables electronic device 900 to communicate with one or more other computing devices (e.g., router, modem, etc.). This communication can be performed via input / output (I / O) interface 950. Furthermore, electronic device 900 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public networks, such as the Internet) via network adapter 960. As shown, network adapter 960 communicates with other modules of electronic device 900 via bus 930. It should be understood that, although not shown in the figures, other hardware and / or software modules can be used in conjunction with electronic device 900, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0115] From the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solutions according to the embodiments of this disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, external hard drive, etc.) or on a network, including several instructions to cause a computing device (such as a personal computer, server, terminal device, or network device, etc.) to execute the methods according to the embodiments of this disclosure.

[0116] In exemplary embodiments of this disclosure, a computer-readable storage medium is also provided, on which a program product capable of implementing the methods described above is stored. In some possible embodiments, various aspects of the invention may also be implemented as a program product comprising program code that, when the program product is run on a terminal device, causes the terminal device to perform the steps of the various exemplary embodiments of the invention described in the "Exemplary Methods" section above.

[0117] refer to Figure 10 As shown, a program product 1000 for implementing the above-described method according to an embodiment of the present invention is described. It may employ a portable compact disc read-only memory (CD-ROM) and include program code, and may run on a terminal device, such as a personal computer. However, the program product of the present invention is not limited thereto. In this document, the readable storage medium may be any tangible medium containing or storing a program that may be used by or in conjunction with an instruction execution system, apparatus, or device.

[0118] The program product may employ any combination of one or more readable media. A readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires, a portable disk, a hard disk, 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 devices, magnetic storage devices, or any suitable combination thereof.

[0119] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, carrying readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A readable signal medium may also be any readable medium other than a readable storage medium, capable of sending, propagating, or transmitting programs for use by or in conjunction with an instruction execution system, apparatus, or device.

[0120] The program code contained on the readable medium may be transmitted using any suitable medium, including but not limited to wireless, wired, optical fiber, RF, etc., or any suitable combination thereof.

[0121] Program code for performing the operations of this invention can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java and C++, and conventional procedural programming languages ​​such as C or similar languages. The program code can execute entirely on the user's computing device, partially on the user's computing device, as a standalone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0122] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and embodiments are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the claims.

Claims

1. A low-code development method, characterized in that, The method includes: Determine the target metadata language template and identify the target metadata language corresponding to the target metadata language template; the target metadata language is a low-code metadata language written based on the target metadata language template. The target metadata language is parsed to obtain action information, and the action information is identified to obtain a type identification result; Based on the type identification result, the action information is distributed to the front-end page or the back-end system to execute the action corresponding to the action information on the front-end page or the back-end system. The target metadata language includes metadata language blocks; each metadata language block includes block types and action events; the block types are used to determine how data is displayed or how users interact with it; the action events describe events corresponding to actions performed by the front-end page or back-end system. The step of parsing the target metadata language to obtain action information includes: The metadata language block is parsed to obtain the block type and the action event; The action information is obtained by parsing the event content corresponding to the action event; The action information includes an action identifier and the action type corresponding to the action identifier; The step of parsing the event content corresponding to the action event to obtain action information includes: The event content corresponding to the action event is parsed to obtain the action identifier included in the action content and the action type corresponding to the action identifier.

2. The low-code development method according to claim 1, characterized in that, The determination of the target metadata language template includes: If a selection instruction is obtained, the target metadata language template corresponding to the selection instruction is determined from multiple preset metadata language templates.

3. The low-code development method according to claim 1, characterized in that, The process of identifying the action information to obtain a type identification result includes: The action type in the action information is identified to obtain the type identification result.

4. The low-code development method according to claim 3, characterized in that, The step of distributing the action information to the front-end page or back-end system based on the type identification result includes: If the type identification result is the first type result corresponding to the front-end page, then the action information is distributed to the front-end page; If the type identification result is the second type result corresponding to the backend system, then the action information is distributed to the backend system.

5. The low-code development method according to claim 1, characterized in that, The step of performing the action corresponding to the action information on the front-end page or the back-end system includes: By combining the action identifier, the action type corresponding to the action identifier, and the block type, a corresponding action is executed on the front-end page or the back-end system; the block type is used to identify the component type, and the component is used to be responsible for the display of the action and user interaction.

6. A low-code development device, characterized in that, The device includes: The identification module is configured to determine a target metadata language template and identify the target metadata language corresponding to the target metadata language template; the target metadata language is a low-code metadata language written based on the target metadata language template. The parsing module is configured to parse the target metadata language to obtain action information, and to identify the action information to obtain a type identification result; The distribution module is configured to distribute the action information to a front-end page or a back-end system based on the type identification result, so as to execute the action corresponding to the action information on the front-end page or the back-end system. The target metadata language includes metadata language blocks; each metadata language block includes block types and action events; the block types are used to determine how data is displayed or how users interact with it; the action events describe events corresponding to actions performed by the front-end page or back-end system. The action information obtained by parsing the target metadata language is configured as follows: The metadata language block is parsed to obtain the block type and the action event; The action information is obtained by parsing the event content corresponding to the action event; The action information includes an action identifier and the action type corresponding to the action identifier; The action information obtained by parsing the event content corresponding to the action event is configured as follows: The event content corresponding to the action event is parsed to obtain the action identifier included in the action content and the action type corresponding to the action identifier.

7. An electronic device, characterized in that, include: processor; Memory for storing the executable instructions of the processor; The processor is configured to execute the low-code development method of any one of claims 1-5 by executing the executable instructions.

8. A computer-readable storage medium storing a computer program thereon, characterized in that, When the computer program is executed by a processor, it implements the low-code development method according to any one of claims 1-5.

Images