CN117667089A - Front-end form generation method and device, storage medium and electronic equipment - Google Patents

Abstract

The invention discloses a front-end form generation method, device, storage medium and electronic equipment. Among them, the method includes: parsing the target file of the predetermined class in the back-end server to obtain the data information of the predetermined class and the back-end verification annotation; based on the data information, determining the form item used to obtain the input form data on the front-end page, Among them, the front-end page and the back-end server have a separated architecture. The separated architecture means that the functional deployment of the front-end page and the functional deployment of the back-end server are decoupled from each other; the back-end verification annotations are converted and used to verify the form data on the front-end page. Form validation rules; based on the form validation rules and form items, a front-end form is generated on the front-end page. There is a mapping relationship between the front-end form and the target file, and the target file is used to process the front-end form submitted to the back-end server. The invention solves the technical problem of unsatisfactory front-end and back-end data conversion efficiency in related technologies.

Description

Front-end form generation method, device, storage medium and electronic equipment

Technical field

The present invention relates to the field of front-end and back-end development, the field of data transmission, and the field of verification technology. Specifically, it relates to a front-end form generation method, device, storage medium, and electronic equipment.

Background technique

Currently, in the development of Web (webpage) applications, the front-end and back-end separation architecture is widely used. Frequent data interaction is required between the front-end and the back-end. In order to achieve the efficiency and consistency of data transmission, data transfer objects are often used to Data is transferred between different layers. Data transfer objects usually contain multiple fields and validation annotations to describe the structure and validation rules of the data. However, due to the differences in code languages and validation rules between the front-end and back-end, it is usually necessary to manually create front-end form items and validation rules, which results in repetitive work and potential errors. There is no widely used automated solution in related technologies. Data conversion and validation methods may be less efficient and error-prone for complex data transfer object structures and validation rules.

In response to the above problems, no effective solution has yet been proposed.

Contents of the invention

Embodiments of the present invention provide a front-end form generation method, device, storage medium and electronic equipment to at least solve the technical problem of unsatisfactory front-end and back-end data conversion efficiency in related technologies.

According to one aspect of an embodiment of the present invention, a front-end form generation method is provided, including: parsing a target file of a predetermined class in a back-end server to obtain data information of the predetermined class and back-end verification annotations; based on the Data information, determine the form items used to obtain the input form data on the front-end page, wherein the front-end page and the back-end server have a separated architecture, and the separated architecture is the functional deployment of the front-end page and the back-end server. The functional deployment of the end server is decoupled from each other; the back-end verification annotations are converted to determine the form verification rules used to verify the form data on the front-end page; based on the form verification rules and the form items , generate a front-end form on the front-end page, where there is a mapping relationship between the front-end form and the target file, and the target file is used to process the front-end form submitted to the back-end server.

Optionally, converting the back-end verification annotations and determining the form verification rules on the front-end page includes: obtaining the front-end call mapping configuration; and converting the back-end verification annotations based on the front-end call mapping configuration instructions. Perform conversion to determine the front-end calling method corresponding to the back-end verification annotation; and generate the form verification rules based on the front-end calling method.

Optionally, based on the data information, determining the form items used to obtain the input form data on the front-end page includes: determining the data type of the data information; determining the input box corresponding to the data type, and obtaining the Describe form items.

Optionally, generating a front-end form on the front-end page based on the form validation rules and the form items includes: obtaining a front-end template style and a front-end interface; based on the form validation rules and the form items, using The front-end template style generates the front-end form, wherein the front-end form is submitted to the back-end server through the front-end interface.

Optionally, parsing the target file of the predetermined class in the back-end server to obtain the data information and back-end verification annotations of the predetermined class includes: parsing the source code of the target file in the back-end server Perform analysis to obtain the variable names, keywords, and operators of the predetermined class in the target file; use the variable names, keywords, and operators as nodes to generate an abstract syntax tree; The abstract syntax tree is traversed to obtain the data information and the back-end verification annotations.

Optionally, after the front-end page generates a front-end form based on the form validation rule and the form item, the front-end page performs the following processing: obtain the form input in the form item Data; if the form data is verified by the form validation rule, submit the front-end form to the back-end server.

Optionally, the front-end page is provided with a custom configuration interface, and generating a front-end form on the front-end page based on the form verification rules and the form items includes: based on the form verification rules and the form Project, generate an initial form; adjust the initial form through the custom configuration interface to obtain the front-end form.

According to another aspect of the embodiment of the present invention, a front-end form generation device is provided, including: a parsing module for parsing a target file of a predetermined class in a back-end server to obtain the data information of the predetermined class and the back-end Verification annotation; an item determination module, configured to determine the form item used to obtain the input form data on the front-end page based on the data information, wherein the front-end page and the back-end server have a separate architecture, and the separate architecture Decoupling the functional deployment of the front-end page from the functional deployment of the back-end server; a rule determination module for converting the back-end verification annotations and determining the form data for the front-end page Form verification rules for verification; a form generation module for generating a front-end form on the front-end page based on the form verification rule and the form item, wherein there is a mapping relationship between the front-end form and the target file , the target file is used to process the front-end form submitted to the back-end server.

According to another aspect of the embodiment of the present invention, a non-volatile storage medium is provided. The non-volatile storage medium stores a plurality of instructions, and the instructions are suitable for loading and executing any one of the instructions by a processor. The front-end form generation method described above.

According to another aspect of an embodiment of the present invention, an electronic device is provided, including: one or more processors and a memory, the memory being used to store one or more programs, wherein when the one or more programs When executed by the one or more processors, the one or more processors are caused to implement any one of the front-end form generation methods described above.

In the embodiment of the present invention, by parsing the target file of the predetermined class in the back-end server, the data information of the predetermined class and the back-end verification annotation are obtained; based on the data information, the method used to obtain input on the front-end page is determined. Form items of form data, wherein the front-end page and the back-end server have a separated architecture, and the separated architecture is that the functional deployment of the front-end page and the functional deployment of the back-end server are decoupled from each other; The back-end verification annotations are converted to determine the form verification rules used to verify the form data on the front-end page; based on the form verification rules and the form items, a front-end form is generated on the front-end page, wherein, There is a mapping relationship between the front-end form and the target file, and the target file is used to process the front-end form submitted to the back-end server. The purpose of automatic conversion from back-end processing to front-end forms is achieved, and the technical effect of improving the unsatisfactory front-end and back-end data conversion efficiency is achieved, thereby solving the technical problem of unsatisfactory front-end and back-end data conversion efficiency existing in related technologies.

Description of drawings

The drawings described here are used to provide a further understanding of the present invention and constitute a part of this application. The illustrative embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the attached picture:

Figure 1 is a flow chart of an optional front-end form generation method provided according to an embodiment of the present invention;

Figure 2 is a schematic flow chart of an optional front-end form generation method provided according to an embodiment of the present invention;

Figure 3 is a schematic diagram of an optional front-end form generation device provided according to an embodiment of the present invention.

Detailed ways

In order to enable those skilled in the art to better understand the solutions of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only These are some embodiments of the present invention, rather than all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts should fall within the scope of protection of the present invention.

It should be noted that the terms "first", "second", etc. in the description and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It is to be understood that the data so used are interchangeable under appropriate circumstances so that the embodiments of the invention described herein are capable of being practiced in sequences other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, e.g., a process, method, system, product, or apparatus that encompasses a series of steps or units and need not be limited to those explicitly listed. Those steps or elements may instead include other steps or elements not expressly listed or inherent to the process, method, product or apparatus.

For the convenience of description, some nouns or terms involved in the embodiments of this application are described below:

Data Transfer Object (DTO, Data Transfer Object) is used to transfer data within an application or between different systems. It is usually used to transfer data from one layer to another. DTO files are usually used to describe data transfer objects. Java class files or files in other programming languages help decouple data models and business logic, improving the flexibility and maintainability of the system.

AST (Abstract Syntax Tree) is a tree-shaped data structure that is constructed by parsing and analyzing source code. Each node in AST represents a syntax unit in the source code, such as expression, statement, function, class, etc.

The front end refers to the user interface part of the application, including the interface and logic for users to interact with the application. The role of the front-end is to display data, interact with users, and present the user interface to users to provide a user-friendly experience.

Backend refers to the server-side part of the application that handles business logic, data storage, and communication with the frontend. The role of the backend is to handle business logic, data storage and communication with the frontend, ensuring the normal operation of the application and providing corresponding functions.

The front-end and back-end separation architecture is a software architecture model in which the front-end and back-end are developed, deployed and maintained independently. The main feature of the front-end and front-end separation architecture is that there can be data interaction between the front and back ends, and data is transmitted through the network instead of directly coupled together. Decoupling front-end and back-end functions can improve development efficiency, reduce system complexity, and enable parallel development and deployment of front-end and back-end.

In related technologies, errors are prone to occur when creating front-end form items and validation rules manually or with the help of some components and frameworks, resulting in inaccurate or incomplete data interaction and affecting the stability and reliability of the system. The code language differences between the front-end and back-end also lead to maintenance difficulties. Once the back-end data structure changes, the forms in the front-end page also need to be modified accordingly, increasing maintenance costs and risks. Moreover, frequent data interaction and manual creation of front-end form items and validation rules reduce development efficiency and have poor scalability.

In response to the above problems, embodiments of the present invention provide a method embodiment for generating a front-end form. It should be noted that the steps shown in the flow chart of the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Also, although a logical order is shown in the flowchart diagrams, in some cases the steps shown or described may be performed in a different order than herein.

Figure 1 is a flow chart of a front-end form generation method according to an embodiment of the present invention. As shown in Figure 1, the optional execution subject is a software component for front-end and back-end conversion. The method includes the following steps:

Step S102, parse the target file of the predetermined class in the back-end server to obtain the data information of the predetermined class and the back-end verification annotation;

It can be understood that by parsing the target file of the predetermined class in the back-end server, the predetermined class can be lexically analyzed for the DTO class file in Java, and decomposed based on the source code, the data information and back-end verification annotations of the predetermined class can be obtained. Through the above processing, the data processing that needs to be performed on the target file in the back-end server can be extracted, which can be used to subsequently generate a front-end form in the front-end page.

In an optional embodiment, parsing the target file of the predetermined class in the back-end server to obtain the data information of the predetermined class and the back-end verification annotations includes: parsing the source code of the target file in the back-end server. , get the variable names, keywords, and operators of the predetermined class in the target file; use the variable names, keywords, and operators as nodes to generate an abstract syntax tree; traverse the abstract syntax tree to obtain data information and back-end verification annotations. .

It can be understood that the predetermined class can be Java's DTO class, perform lexical analysis on the target file, and decompose the source code into tokens, such as keywords, identifiers, operators, etc. of the DTO class. Using variable names, keywords, and operators as nodes, an abstract syntax tree is generated to represent the structure and hierarchy of the source code. Traverse the abstract syntax tree to obtain data information and back-end verification annotations.

It should be noted that the above backend verification annotations may come from manual annotations, or may be automatically added by code analysis tools. The backend verification annotations contain some additional information about the code, such as the data type of variables, return values of methods, etc. . The above-mentioned backend verification annotations may be in a predetermined annotation format.

Optionally, there are many ways to traverse the abstract syntax tree. Specific information of the source code is obtained through traversal. The traversal can be a depth-first search or a breadth-first search. The depth-first search described above searches the branches of the tree as deep as possible until all nodes reachable from the source node are found. If there are still undiscovered nodes, select one of them as the source node and repeat the above process. The entire process is repeated until all nodes in the abstract syntax tree are visited. Breadth-first search will first visit the node closer to the root of the abstract syntax tree, then visit all adjacent nodes, and then visit the adjacent nodes of these adjacent nodes.

Optionally, the keywords, identifiers, and operators of the above DTO class can be of multiple types. For example, the keywords can be keywords used to define the access rights of the class, and keywords used to define the type and implementation interface of the class. An identifier can refer to a name used to represent a class, property, method, etc., usually a string composed of letters, numbers, and underscore symbols. Operators can be assignment operators, addition, subtraction, multiplication and division operators, etc. that are used to assign and calculate attributes of a class. In addition, DTO classes may also include keywords, identifiers and operators used to represent data types, method declarations, annotations, etc.

Step S104, based on the data information, determine the form items used to obtain the input form data on the front-end page, where the front-end page and the back-end server have a separated architecture, and the separated architecture is that the functional deployment of the front-end page and the functional deployment of the back-end server are mutually exclusive. decoupling;

It can be understood that the front-end page and the back-end server have separate architectures, which decouples the functional deployment of the front-end page from the functional deployment of the back-end server. After the functions of the front-end page and back-end server are decoupled, they can be developed and maintained independently without affecting each other. This allows for more flexibility in updating and modifying page and server functionality without affecting changes in one part to another. This makes it easier to expand and upgrade. New features can be added independently to front-end pages or back-end servers to better adapt to different platforms and devices. Based on the data information parsed in the back-end server, the form items used to obtain the input form data in the front-end page can be determined.

Optionally, the above form items can be Vue form items, which are components used to collect user input data. These form items can be bound to the data attributes of the Vue instance, thereby realizing two-way binding of data. Vue form items can also contain validation rules to ensure that the data entered by the user meets the requirements. Vue (view) is used to build user interfaces and single-page applications.

In an optional embodiment, based on the data information, determining the form items used to obtain the input form data on the front-end page includes: determining the data type of the data information; determining the input box corresponding to the data type to obtain the form items.

It can be understood that according to the DOT type in the data information, the data type of the data information can be determined, the input box corresponding to the data type can be determined, and the form items can be obtained.

Optionally, when the data information is indicated as a string type, a text input box is generated as a form item; when the data information is indicated as an integer, a numeric input box is generated as a form item; when the data information is indicated as a date type In the case of , a date input box is generated as a form item, when the data information indicates an enumeration type, a drop-down box is generated as a form item, and when the data information indicates a Boolean type, a check box is generated as a form item.

Step S106, convert the back-end verification annotations and determine the form verification rules used to verify the form data on the front-end page;

It can be understood that by converting the back-end validation annotations, the form validation rules used to validate the form data on the front-end page can be determined. Before the front-end form is submitted to the back-end server, the form data will be verified on the front-end page according to the form validation rules, and then the submission to the back-end server can be performed.

In an optional embodiment, converting the back-end verification annotations and determining the form verification rules on the front-end page includes: obtaining the front-end call mapping configuration; converting the back-end verification annotations based on the front-end call mapping configuration instructions and determining The front-end calling method corresponding to the back-end verification annotation; based on the front-end calling method, form validation rules are generated.

It can be understood that the content in the front-end call mapping configuration includes the conversion mapping corresponding to the back-end verification annotation and the front-end calling method. Based on the front-end calling method obtained after converting the back-end validation annotations, form validation rules can be generated.

Optionally, the backend verification annotations can be Hibernate verification annotations extracted from the DTO class, such as @NotNull, @Max(value), @Min(value), message, etc. Hibernate validation annotations are a set of annotations used for data validation on Java objects, used to validate fields of entity classes in applications. @NotNull is used to ensure that the field is not empty (null), if the field is null, a validation error will be thrown. @Max(value) is used to specify the maximum value of the field. If the value of the data field exceeds this maximum value, a validation error will be thrown. @Min(value) is used to specify the minimum value of the field. If the value of the data field exceeds this minimum value, a validation error will be thrown. Message indicates that this property is used to specify the error message when validation fails. When the field does not meet the validation rules, the message in message will be displayed.

Optionally, according to the front-end call mapping configuration, @NotNull is converted into calling the required item verification method, @Max(value) is converted into calling the maximum value verification method, and message is converted into calling the error message method.

Step S108: Based on the form validation rules and form items, a front-end form is generated on the front-end page. There is a mapping relationship between the front-end form and the target file. The target file is used to process the front-end form submitted to the back-end server.

It can be understood that the front-end form is generated on the front-end page using the form validation rules and form items obtained above. There is a mapping relationship between the front-end form and the target file. After the front-end form is verified, the front-end form will be submitted to the back-end server. The target file in the back-end server is used to process the submitted front-end form.

In an optional embodiment, based on the form validation rules and form items, generating a front-end form on the front-end page includes: obtaining the front-end template style and front-end interface; based on the form validation rules and form items, using the front-end template style to generate the front-end form , where the front-end form is submitted to the back-end server through the front-end interface.

It can be understood that the front-end template style and front-end interface are pre-configured, the front-end template style is used to generate the front-end form, and the front-end form is submitted to the back-end server through the front-end interface.

Optionally, the above front-end forms can be of multiple types, such as Vue or React single-page files. Both Vue and React can create single page applications (SPA), and single page files are a technology used to build these applications. In Vue, single-page files usually end with the ".vue" extension and contain HTML, CSS and JavaScript code, as well as component-related logic. React's single-page files are usually ".js" or ".jsx" files. React single-page files support component development, splitting a page into multiple components. Each component has its own status and behavior, making the code Reusability and maintainability have been greatly improved.

In an optional embodiment, after the front-end form is generated on the front-end page based on the form validation rules and form items, the front-end page performs the following processing: obtain the form data entered in the form item; after the form data passes the form validation In the case of rule verification, the front-end form is submitted to the back-end server.

It can be understood that the above-mentioned execution subject is the front-end page. The front-end page generally displays data, interacts with the user, and presents the user interface to the user, and can obtain the form data input into the form item. If the form data passes the form validation rules, the front-end form will be submitted to the back-end server for processing.

In an optional embodiment, the front-end page is provided with a custom configuration interface, and based on the form validation rules and form items, a front-end form is generated on the front-end page, including: generating an initial form based on the form validation rules and form items; Define the configuration interface, adjust the initial form, and obtain the front-end form.

It is understandable that a custom configuration interface can be set up on the front-end page, and the automatically generated form validation rules and form items can be used as the initial form. The set custom configuration interface can customize the automatically set initial form to meet the needs of different projects. After adjusting the initial form through the custom configuration interface, you can get the adjusted front-end form.

Through the above-mentioned step S102, the target file of the predetermined class in the back-end server is parsed to obtain the data information of the predetermined class and the back-end verification annotation; step S104, based on the data information, determine the form used to obtain the input form data on the front-end page project, in which the front-end page and the back-end server have a separated architecture, and the separated architecture is that the functional deployment of the front-end page and the functional deployment of the back-end server are decoupled from each other; step S106, convert the back-end verification annotations and determine them for use in the front-end page Form validation rules for validating form data; step S108, based on the form validation rules and form items, generate a front-end form on the front-end page, where there is a mapping relationship between the front-end form and the target file, and the target file is used to submit to the back-end The server's front-end form is processed. It can achieve the purpose of automatic conversion from back-end processing to front-end forms, achieve the technical effect of improving the unsatisfactory front-end and back-end data conversion efficiency, and thereby solve the technical problem of unsatisfactory front-end and back-end data conversion efficiency existing in related technologies.

Based on the above embodiments and optional embodiments, the present invention proposes an optional implementation, as shown in Figure 2, which specifically includes the following steps:

Step S1: Perform lexical analysis on the target file of the DOT class in the back-end server, and decompose it to generate tokens based on the source code of the target file, such as keywords, identifiers, operators, etc. as data information. Based on the above data information, syntax analysis is performed, and keywords, identifiers, and operators are used as nodes to generate an abstract syntax tree to represent the structure and hierarchy of the source code.

Step S2: Traverse and analyze the abstract syntax tree (AST) to identify and extract the structure, field type and field name of the Java DTO class as data information.

Step S3: Based on the data information of the DTO class, form items are generated for display and use as list items of the table.

Step S4: According to the data type of the data information, convert it into corresponding Vue form items, such as text input box, number input box, time input box, drop-down box, check box, etc.

Step S5, the target file of the DOT class can also parse out the back-end verification annotations. The back-end verification annotations can be Hibernate verification annotations. There can be many types of Hibernate verification annotations extracted, such as @NotNull, @Max(value), @Min(value ), message, etc.

Step S6: Generate corresponding Vue form validation rules based on the extracted Hibernate validation annotations. For example, convert @NotNull to call the required item verification method, @Max(value) to call the maximum value verification method, and convert message to call the error reporting method. information method.

Step S7: Generate a Vue single page file based on the converted Vue form item and Vue form validation rules.

The above optional implementation methods achieve at least the following effects: Compared with the traditional method of manually creating front-end form items and validation rules, this specific implementation method uses abstract syntax trees (AST) to achieve automated conversion, without the need to create Vue or React form items and verification rules one by one. For validation rules, you only need to take the target file as input to automatically generate a front-end form, thereby speeding up development, saving time and costs, and maintaining data consistency. Through abstract syntax tree technology, it is directly converted into the corresponding front-end form. It ensures the consistency of the front-end and back-end data models, avoids potential errors caused by manual conversion, and improves the accuracy and stability of front-end and back-end data interaction. By combining AST technology with the automatic generation of front-end form items, the efficiency and quality of software development are significantly improved. Compared with the traditional manual conversion method, it has obvious advantages in data consistency and error reduction. It can focus more on business logic rather than tedious writing of forms and validation rules, speeding up the efficiency of form development.

It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions, and, although a logical sequence is shown in the flowchart, in some cases, The steps shown or described may be performed in a different order than here.

This embodiment also provides a front-end form generation device, which is used to implement the above-mentioned embodiments and preferred implementations. What has already been described will not be described again. As used below, the terms "module" and "device" may be a combination of software and/or hardware that implements a predetermined function. Although the apparatus described in the following embodiments is preferably implemented in software, implementation in hardware, or a combination of software and hardware, is also possible and contemplated.

According to an embodiment of the present invention, an embodiment of a device for implementing a front-end form generation method is also provided. Figure 3 is a schematic diagram of a front-end form generation device according to an embodiment of the present invention. As shown in Figure 3, the above-mentioned front-end form The generation device includes: an analysis module 302, an item determination module 304, a rule determination module 306, and a form generation module 308. This device will be described below.

The parsing module 302 is used to parse the target file of the predetermined class in the back-end server to obtain the data information of the predetermined class and the back-end verification annotations;

The item determination module 304 is connected to the parsing module 302 and is used to determine the form items used to obtain the input form data on the front-end page based on the data information, wherein the front-end page and the back-end server have a separate architecture, and the separation architecture is the front-end page. Function deployment is decoupled from that of the back-end server;

The rule determination module 306 is connected to the project determination module 304 and is used to convert the back-end verification annotations and determine the form verification rules used to verify the form data on the front-end page;

The form generation module 308 is connected to the rule determination module 306 and is used to generate a front-end form on the front-end page based on the form verification rules and form items. There is a mapping relationship between the front-end form and the target file, and the target file is used to submit to the back-end page. The front-end form of the end server is processed.

In a front-end form generation device provided by an embodiment of the present invention, the parsing module 302 is used to parse the target file of a predetermined class in the back-end server to obtain the data information of the predetermined class and the back-end verification annotations; the project determination module 304 , connected to the parsing module 302, used to determine the form items used to obtain the input form data on the front-end page based on the data information, where the front-end page and the back-end server are separated architectures, and the separated architecture is the function deployment of the front-end page and the back-end server. The functional deployment of the end server is decoupled from each other; the rule determination module 306 is connected to the project determination module 304, and is used to convert the back-end verification annotations and determine the form verification rules used to verify the form data on the front-end page; the form generation module 308, connected to the rule determination module 306, used to generate a front-end form on the front-end page based on the form validation rules and form items, where there is a mapping relationship between the front-end form and the target file, and the target file is used to process the data submitted to the back-end server. Front-end forms are processed. The purpose of automatic conversion from back-end processing to front-end forms is achieved, and the technical effect of improving the unsatisfactory front-end and back-end data conversion efficiency is achieved, thereby solving the technical problem of unsatisfactory front-end and back-end data conversion efficiency existing in related technologies.

As an optional embodiment, in the front-end form generation device provided by the embodiment of the present invention, the rule determination module includes: a first acquisition module, used to obtain the front-end call mapping configuration; an annotation conversion module, used to call the mapping configuration based on the front-end Instructs to convert the back-end verification annotations and determines the front-end calling method corresponding to the back-end verification annotations; the rule generation module is used to generate form verification rules based on the front-end calling methods.

As an optional embodiment, the item determination module includes: a first determination module, used to determine the data type of the data information; a second determination module, used to determine the input box corresponding to the data type to obtain the form item.

As an optional embodiment, the form generation module includes: a second acquisition module, used to obtain the front-end template style and front-end interface; a generation processing module, used to generate the front-end using the front-end template style based on the form verification rules and form items. Form, where the front-end form is submitted to the back-end server through the front-end interface.

As an optional embodiment, the parsing module includes: a first parsing module, used to parse the source code of the target file in the back-end server to obtain the variable names, keywords, and operators of the predetermined class in the target file. ; The abstract syntax tree generation module is used to generate abstract syntax trees using variable names, keywords, and operators as nodes; the traversal module is used to traverse the abstract syntax tree to obtain data information and back-end verification annotations.

As an optional embodiment, the form generation module includes: a third acquisition module, used to acquire the form data entered in the form item; a submission module, used to submit the form data when the form data passes the form verification rule verification. Submit the front-end form to the back-end server.

As an optional embodiment, the form generation module includes: an initial generation module, used to generate an initial form based on the form validation rules and form items; a custom configuration module, used to configure the initial form through a custom configuration interface Adjust to get the front-end form.

It should be noted that each of the above modules can be implemented through software or hardware. For example, the latter can be implemented in the following ways: the above modules can be located in the same processor; or the above modules can be implemented in any combination. Located in different processors.

It should be noted here that the above-mentioned parsing module 302, project determination module 304, rule determination module 306, and form generation module 308 correspond to steps S102 to S108 in the embodiment. The examples and applications implemented by the above-mentioned modules and the corresponding steps are The scenarios are the same, but are not limited to the content disclosed in the above embodiments. It should be noted that the above module can run in a computer terminal as part of the device.

It should be noted that for optional or preferred implementation modes of this embodiment, reference can be made to the relevant descriptions in the embodiments, and details will not be described again here.

The above-mentioned front-end form generation device may also include a processor and a memory. The parsing module 302, the item determination module 304, the rule determination module 306, the form generation module 308, etc. are all stored in the memory as program units, and the processor executes the programs stored in the memory. The above program units are used to implement the corresponding functions.

The processor contains a core, which retrieves the corresponding program unit from the memory. The kernel can set one or more. Memory may include non-permanent memory in computer-readable media, random access memory (RAM) and/or non-volatile memory, such as read-only memory (ROM) or flash memory (flash RAM). The memory includes at least one memory chip.

Embodiments of the present invention provide a non-volatile storage medium on which a program is stored. When the program is executed by a processor, a front-end form generation method is implemented.

An embodiment of the present invention provides an electronic device. The electronic device includes a processor, a memory, and a program stored in the memory and executable on the processor. When the processor executes the program, it implements the following steps: The target file is parsed to obtain the data information of the predetermined class and the back-end verification annotations; based on the data information, the form items used to obtain the input form data on the front-end page are determined. Among them, the front-end page and the back-end server are separated architectures. The architecture is that the functional deployment of the front-end page and the functional deployment of the back-end server are decoupled from each other; the back-end validation annotations are converted to determine the form validation rules used to validate the form data on the front-end page; based on the form validation rules and form items, A front-end form is generated on the front-end page, where there is a mapping relationship between the front-end form and the target file, and the target file is used to process the front-end form submitted to the back-end server. The devices in this article can be servers, PCs, etc.

The present invention also provides a computer program product, which, when executed on a data processing device, is suitable for executing a program initialized with the following method steps: parsing the target file of a predetermined class in the back-end server to obtain data information of the predetermined class and back-end validation annotations; based on the data information, determine the form items used to obtain the input form data on the front-end page. Among them, the front-end page and the back-end server are separated architectures, and the separated architecture is the function deployment of the front-end page and the back-end server. Function deployment is decoupled from each other; the back-end validation annotations are converted to determine the form validation rules used to validate the form data on the front-end page; based on the form validation rules and form items, a front-end form is generated on the front-end page, in which the front-end form and There is a mapping relationship between target files, and the target files are used to process front-end forms submitted to the back-end server.

Optionally, the above computer program product is also applicable to a program that performs the following initialization steps: obtains the front-end call mapping configuration; converts the back-end verification annotations based on the front-end call mapping configuration instructions, and determines the front-end calling method corresponding to the back-end verification annotations. ; Generate form validation rules based on the front-end calling method.

Optionally, the above-mentioned computer program product is also suitable for executing a program initialized with the following method steps: determining the data type of the data information; determining the input box corresponding to the data type, and obtaining the form items.

Optionally, the above computer program product is also applicable to a program that performs the following initialization steps: obtain the front-end template style and front-end interface; based on the form validation rules and form items, use the front-end template style to generate the front-end form, wherein the front-end form passes through the front-end The interface is submitted to the backend server.

Optionally, the above computer program product is also suitable for executing a program that has the following steps for initialization: parsing the source code of the target file in the back-end server to obtain the variable names, keywords, and operators of the predetermined class in the target file; Use variable names, keywords, and operators as nodes to generate an abstract syntax tree; traverse the abstract syntax tree to obtain data information and back-end verification annotations.

Optionally, the above-mentioned computer program product is also applicable to a program that performs the following initialization steps: obtaining the form data entered in the form item; and submitting the front-end form to the back-end when the form data is verified by the form validation rules. server.

Optionally, the above computer program product is also applicable to a program that performs the following initialization steps: generate an initial form based on form validation rules and form items; adjust the initial form through a custom configuration interface to obtain a front-end form.

Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Thus, the invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

The invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each process and/or block in the flowchart illustrations and/or block diagrams, and combinations of processes and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine, such that the instructions executed by the processor of the computer or other programmable data processing device produce a use A device for realizing the functions specified in one process or multiple processes of the flowchart and/or one block or multiple blocks of the block diagram.

These computer program instructions may also be stored in a computer-readable memory that causes a computer or other programmable data processing apparatus to operate in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction means, the instructions The device implements the functions specified in a process or processes of the flowchart and/or a block or blocks of the block diagram.

These computer program instructions may also be loaded onto a computer or other programmable data processing device, causing a series of operating steps to be performed on the computer or other programmable device to produce computer-implemented processing, thereby executing on the computer or other programmable device. Instructions provide steps for implementing the functions specified in a process or processes of a flowchart diagram and/or a block or blocks of a block diagram.

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

Memory may include non-volatile memory in computer-readable media, random access memory (RAM), and/or non-volatile memory in the form of read-only memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media includes both persistent and non-volatile, removable and non-removable media that can be implemented by any method or technology for storage of information. Information may be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), and read-only memory. (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, Magnetic tape cassettes, tape disk storage or other magnetic storage devices or any other non-transmission medium can be used to store information that can be accessed by a computing device. As defined in this article, computer-readable media does not include transitory media, such as modulated data signals and carrier waves.

It should also be noted that the terms "comprises," "comprises," or any other variation thereof are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements not only includes those elements, but also includes Other elements are not expressly listed or are inherent to the process, method, article or equipment. Without further limitation, an element qualified by the statement "comprises a..." does not exclude the presence of additional identical elements in the process, method, good, or device that includes the element.

It will be appreciated by those skilled in the art that embodiments of the present invention may be provided as methods, systems or computer program products. Thus, the invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

The above are only examples of the present invention and are not intended to limit the present invention. Various modifications and variations will occur to the present invention to those skilled in the art. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention shall be included in the scope of the claims of the present invention.

Claims (10)

1. A front-end form generation method, comprising:

analyzing a target file of a preset class in a back-end server to obtain data information of the preset class and a back-end verification annotation;

based on the data information, determining a form item for acquiring input form data in a front-end page, wherein the front-end page and the back-end server are of a separation architecture, and the separation architecture is that the function deployment of the front-end page and the function deployment of the back-end server are mutually decoupled;

Converting the back-end verification annotation, and determining a form verification rule for verifying the form data on the front-end page;

generating a front-end form on the front-end page based on the form verification rule and the form item, wherein a mapping relation exists between the front-end form and the target file, and the target file is used for processing the front-end form submitted to the back-end server.

2. The method of claim 1, wherein said translating the backend validation annotation to determine a form validation rule at the front-end page comprises:

acquiring front-end call mapping configuration;

converting the back-end verification annotation based on the front-end call mapping configuration instruction, and determining a front-end call method corresponding to the back-end verification annotation;

and generating the form verification rule based on the front-end calling method.

3. The method of claim 1, wherein the determining a form item for acquiring the input form data at the front-end page based on the data information comprises:

determining a data type of the data information;

And determining an input box corresponding to the data type to obtain the form item.

4. The method of claim 1, wherein the generating a front-end form on the front-end page based on the form verification rules and the form items comprises:

acquiring a front-end template pattern and a front-end interface;

and generating the front-end form by adopting the front-end template style based on the form verification rule and the form item, wherein the front-end form is submitted to the back-end server through the front-end interface.

5. The method according to claim 1, wherein the parsing the target file of the predetermined class in the back-end server to obtain the data information of the predetermined class and the back-end verification annotation includes:

analyzing the source code of the target file in the back-end server to obtain the variable names, keywords and operators of the preset classes in the target file;

generating an abstract syntax tree by taking the variable names, the keywords and the operators as nodes;

traversing the abstract syntax tree to obtain the data information and the backend verification annotation.

6. The method according to any one of claims 1 to 5, wherein after the front-end page generates a front-end form based on the form verification rule and the form item, the following processing is performed by the front-end page:

acquiring the form data input in the form item;

and submitting the front-end form to the back-end server under the condition that the form data passes the form verification rule verification.

7. The method according to any one of claims 1 to 5, wherein the front-end page is provided with a custom configuration interface, and the generating the front-end form on the front-end page based on the form verification rule and the form item includes:

generating an initial form based on the form verification rule and the form item;

and adjusting the initial form through the custom configuration interface to obtain the front-end form.

8. A front-end form generation apparatus, comprising:

the analysis module is used for analyzing the target file of the preset class in the back-end server to obtain the data information of the preset class and the back-end verification annotation;

The item determining module is used for determining a form item for acquiring input form data on a front-end page based on the data information, wherein the front-end page and the back-end server are of a separated architecture, and the separated architecture is that the function deployment of the front-end page and the function deployment of the back-end server are mutually decoupled;

the rule determining module is used for converting the back-end verification annotation and determining a form verification rule for verifying the form data on the front-end page;

the form generation module is used for generating a front-end form on the front-end page based on the form verification rule and the form item, wherein a mapping relation exists between the front-end form and the target file, and the target file is used for processing the front-end form submitted to the back-end server.

9. A non-volatile storage medium storing a plurality of instructions adapted to be loaded by a processor and to perform the front-end form generation method of any of claims 1 to 7.

10. An electronic device, comprising: one or more processors and memory for storing one or more programs, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the front-end form generation method of any of claims 1 to 7.