Application building method based on low-code platform, low-code platform, computer device and readable storage medium

Abstract

The embodiment of the present application proposes an application construction method based on a low-code platform, a low-code platform, a computer device and a readable storage medium. It relates to the field of computer technology. The low-code platform includes: a protocol processing layer, a data layer, a component layer, a rendering layer and an application layer. The method includes: obtaining the demand configuration data of the target front-end application, and parsing the demand configuration data to obtain the back-end logic data and interface description information; processing the back-end logic data and the interface description information respectively to generate a data object model and page original data; according to the data object model and the page original data, obtaining the data of multiple target interface components from the preset component library; according to the page original data and the data of the target interface component, determining the data of the target rendering strategy; integrating the data of the target rendering strategy and the data of multiple target interface components to generate a development file. This application can lower the user's development threshold and improve the user experience.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and specifically, to an application building method based on a low-code platform, a low-code platform, a computer device, and a readable storage medium. Background Art

[0002] The low-code platform is an innovative system between no-code development and full-code development. It enables users to generate common business application code without writing a lot of complex code by providing a series of tools, constraints and configuration options, so that users with non-technical backgrounds can also participate in the application development process, reducing development costs and improving development efficiency.

[0003] Although low-code platforms provide convenience to users in many aspects, users still need to have certain knowledge of development systems in the process of building and configuring low-code platforms. This means that although low-code platforms simplify the development process, users still need to have a certain understanding of programming languages, databases, and system architectures, and have certain programming skills, which raises the development threshold for users. Summary of the invention

[0004] In view of this, the purpose of this application is to provide an application construction method based on a low-code platform, a low-code platform, a computer device and a readable storage medium, which can lower the user's development threshold and improve the user experience.

[0005] In order to achieve the above purpose, the technical solution adopted in the embodiment of the present application is as follows:

[0006] In a first aspect, an embodiment of the present application provides a method for building an application based on a low-code platform, wherein the low-code platform includes: a protocol processing layer, a data layer, a component layer, a rendering layer, and an application layer, and the method includes:

[0007] The protocol processing layer is used to obtain the required configuration data of the target front-end application, and the required configuration data is parsed to obtain the back-end logic data and interface description information of the target front-end application;

[0008] The data layer is used to process the backend logic data and the interface description information respectively to generate a data object model and page original data;

[0009] Using the component layer, according to the data object model and the page original data, the data of multiple target interface components corresponding to the target front-end application are obtained from a preset component library;

[0010] Using the rendering layer, determining data of a target rendering strategy according to the original data of the page and the data of the target interface component;

[0011] The application layer is used to integrate the data of the target rendering strategy and the data of the multiple target interface components to generate a development file of the target front-end application.

[0012] Optionally, the adopting of the protocol processing layer to obtain the required configuration data of the target front-end application, and parsing the required configuration data to obtain the back-end logic data and interface description information of the target front-end application includes:

[0013] Using the protocol definition module in the protocol processing layer, the target front-end application is subjected to data structure definition and interface element configuration to obtain the required configuration data satisfying the data structure definition;

[0014] Using the verification module in the protocol processing layer to perform format verification on the required configuration data;

[0015] Using the reuse module in the protocol processing layer, based on the required configuration data after format verification, determine the target tool function reused by the target front-end application from the preset tool set;

[0016] The core module in the protocol processing layer is used to parse the required configuration data after format verification to obtain the backend logic data and the interface description information, wherein the target tool function is used to perform data processing on the backend logic data.

[0017] Optionally, the data layer is used to process the backend logic data and the interface description information respectively to generate a data object model and page original data, including:

[0018] Using the data protocol module in the data layer, the backend logic data is processed according to predefined data configuration information to generate the data object model;

[0019] The page protocol module in the data layer is used to process the interface description information according to predefined page rendering configuration information to generate the page original data.

[0020] Optionally, the adopting of the component layer to obtain data of multiple target interface components corresponding to the target front-end application from a preset component library according to the data object model and the page original data includes:

[0021] Using the component layer, according to the data object model and the page original data, the data of the target basic component is obtained from the preset basic component library;

[0022] The component layer is used to obtain data of the target desktop component from desktop component libraries corresponding to at least two different development frameworks according to the data object model and the page original data; wherein the multiple target interface components include: the target basic component and the target desktop component.

[0023] Optionally, the using the rendering layer to determine the data of the target rendering strategy according to the original data of the page and the data of the target interface component includes:

[0024] The rendering layer is used to determine the data of the target rendering strategy according to the original data of the page, the data of the target interface component, and the information of the page block where the target interface component is located.

[0025] Optionally, the adopting of the application layer to integrate the data of the target rendering strategy and the data of the plurality of target interface components to generate a development file of the target front-end application program includes:

[0026] The application layer is used to perform persistence processing on the data of the target rendering strategy and the data of the multiple target interface components according to the first usage mode, and a development file of the target front-end application is generated.

[0027] Optionally, the adopting of the application layer to integrate the data of the target rendering strategy and the data of the plurality of target interface components to generate a development file of the target front-end application program includes:

[0028] The application layer is used to perform embedded integration of the data of the target rendering strategy and the data of the multiple target interface components according to the second usage mode to generate a development file of the target front-end application.

[0029] In a second aspect, an embodiment of the present application provides a low-code platform, the low-code platform comprising: a protocol processing layer, a data layer, a component layer, a rendering layer, and an application layer;

[0030] The protocol processing layer is used to obtain the required configuration data of the target front-end application, and parse the required configuration data to obtain the back-end logic data and interface description information of the target front-end application;

[0031] The data layer is used to process the backend logic data and the interface description information respectively to generate a data object model and page original data;

[0032] The component layer is used to obtain data of multiple target interface components corresponding to the target front-end application from a preset component library according to the data object model and the original page data;

[0033] The rendering layer is used to determine the data of the target rendering strategy according to the original data of the page and the data of the target interface component;

[0034] The application layer is used to integrate the data of the target rendering strategy and the data of the multiple target interface components to generate the development file of the target front-end application.

[0035] In a third aspect, an embodiment of the present application provides a computer device, comprising: a processor and a memory, wherein the memory stores machine executable instructions that can be executed by the processor, and the processor can execute the machine executable instructions to implement any method described in the first aspect.

[0036] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements a method as described in any one of the first aspects.

[0037] Compared with the prior art, this application has the following beneficial effects:

[0038] The embodiment of the present application proposes an application construction method based on a low-code platform, a low-code platform, a computer device and a readable storage medium. The low-code platform includes: a protocol processing layer, a data layer, a component layer, a rendering layer and an application layer, and the method includes: using the protocol processing layer to obtain the required configuration data of the target front-end application, and parsing the required configuration data to obtain the back-end logic data and interface description information of the target front-end application; using the data layer, respectively processing the back-end logic data and the interface description information to generate a data object model and page original data; using the component layer, according to the data object model and the page original data, obtaining the data of multiple target interface components corresponding to the target front-end application from the preset component library, so that by taking advantage of componentized development, developers or users can respond to changes faster, reduce duplicate code, and improve the maintainability and scalability of the code; using the rendering layer, according to the page original data and the data of the target interface component, determine the data of the target rendering strategy, and through the close collaboration between the rendering layer and the data layer, the component layer and the protocol processing layer, the overall function and performance goals of the target front-end application are achieved; using the application layer, the data of the target rendering strategy and the data of multiple target interface components are integrated to generate the development file of the target front-end application. Therefore, this application uses a declarative approach to describe the target front-end application, thereby simplifying the development process. Compared with the traditional programming model, this approach effectively lowers the development threshold, allowing non-professional developers to participate in application construction, thereby greatly improving development efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0040] Figure 1 A schematic diagram of the structure of a low-code platform provided for an embodiment of the present application;

[0041] Figure 2 A schematic diagram of a method for building an application based on a low-code platform provided in an embodiment of the present application Figure 1 ;

[0042] Figure 3 A schematic diagram of a method for building an application based on a low-code platform provided in an embodiment of the present application Figure 2 ;

[0043] Figure 4 Schematic diagram of the process of building an application based on a low-code platform provided in the embodiment of the present application Figure 3 ;

[0044] Figure 5 Schematic diagram of the process of building an application based on a low-code platform provided in the embodiment of the present application Figure 4 ;

[0045] Figure 6 Schematic diagram of the process of building an application based on a low-code platform provided in the embodiment of the present application Figure 5 ;

[0046] Figure 7 A schematic diagram of the structure of an application building device based on a low-code platform provided in an embodiment of the present application;

[0047] Figure 8 A schematic diagram of the computer device structure provided in an embodiment of the present application. DETAILED DESCRIPTION

[0048] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. The components of the embodiments of the present application described and shown in the drawings here can be arranged and designed in various different configurations.

[0049] Therefore, the following detailed description of the embodiments of the present application provided in the accompanying drawings is not intended to limit the scope of the present application for which protection is sought, but merely represents selected embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present application.

[0050] It should be noted that relational terms such as "first" and "second" are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0051] In order to clearly describe the application construction method based on the low-code platform provided in the embodiment of the present application, the low-code platform is first described in detail with reference to the accompanying drawings. Figure 1A schematic diagram of the structure of a low-code platform provided in an embodiment of the present application. Figure 1 As shown, the low-code platform 100 may include: a protocol processing layer 110, a data layer 120, a component layer 130, a rendering layer 140 and an application layer 150.

[0052] The protocol processing layer 110 is located at the bottom layer of the low-code platform 100 and is responsible for processing various communication protocols and data formats. It is used to obtain the required configuration data of the target front-end application and parse the required configuration data to obtain the back-end logic data and interface description information of the target front-end application; the protocol processing layer 110 may include: a core module Core, a protocol definition module Schema, a verification module Validator, a reuse module Shared, and a protocol specification JSONSchema. Among them, the core module Core is used to parse and process the demand configuration data; the protocol definition module Schema is used to define and expand the preset communication protocol and data structure to define and expand the format and structure of the exchanged data between the front-end and the back-end, as well as the meaning and purpose of these data; the validation module Validator is responsible for verifying the format, type, range and other aspects of the input data to ensure the accuracy and consistency of the data and ensure that the input data complies with the specifications; the reuse module Shared contains a collection of tools that can be reused in the project to share and reuse between different layers and components to reduce repeated development; the protocol specification JSON Schema is a specification based on the JSON media type. It is mainly used to define and describe the structure of JSON data and is the key part of the low-code platform 100 responsible for processing and managing various protocols; the protocol specification JSON Schema not only provides data validation functions, but also helps developers or users to document JSON data, making the structure and content of the data clearer and easier to understand. In addition, the protocol specification JSON Schema also supports hyperlink navigation, making the association and reference between data more convenient. Finally, the protocol specification JSON Schema can also implement interactive control to ensure that the data remains consistent and secure during the interaction between different operating systems and applications.

[0053] The data layer 120 is located in the second layer of the low-code platform 100, and is used to process the backend logic data and interface description information respectively, generate data object models, and page original data; the data layer 120 may include: a data protocol module DataSchema and a page protocol module UI Schema.

[0054] Among them, the data protocol module Data Schema is used to define the structure, attributes, format and rule protocols of data to ensure that data is transmitted and parsed in a consistent and predictable manner between different parts of the current front-end application; the page protocol module UI Schema is a specification for describing user interface elements and layouts, which defines the raw data required in the page rendering process. These raw data include information such as the type, location, style and interaction logic of various controls, so that developers or users can quickly generate user interfaces that meet design requirements based on these specifications.

[0055] The component layer 130 is located in the third layer of the low-code platform 100, and is used to obtain data of multiple target interface components corresponding to the target front-end application from the preset component library according to the data object model and the original page data to build a user interface. The component layer 130 may include: at least one preset component library. Among them, the preset component library contains a collection of a series of predefined components, which may be created by the development team itself or obtained from a third-party library; each component encapsulates specific UI functions and styles and can be reused in different pages and scenarios. It can be selected according to actual conditions. For example, the preset component library can be selected as Antd component library, element-UI component library, or element-plus component library, etc.

[0056] It should be noted that, in the component layer 130, the present application uses a material protocol to define the behavior and interface of the component layer 130. This material protocol ensures that no matter what user interface (UI) framework is used, as long as the developer follows this material protocol and follows the agreement of the material protocol, the corresponding material components can be implemented, and these material components can be seamlessly integrated into any application platform and used normally. Among them, the material protocol refers to the description of the component layer, which is a standard defined according to experience. For example, each component in the component layer has a name attribute, a click method attribute, an event attribute for component initialization, and style attributes for length, width, and height. In addition, it should be noted that the component layer 130 can be a Widget small application.

[0057] The rendering layer 140 is located at the fourth layer of the low-code platform 100, and is used to determine the data of the target rendering strategy based on the original data of the page and the data of the target interface component, so as to convert the original data of the page and the data of the target interface component into a visual interface; the rendering layer 140 may include: at least one preset rendering database for building a user interface. Among them, the preset rendering database for building a user interface can be selected according to actual conditions. For example, the preset rendering database for building a user interface can be selected as a React library, a Vue2 library, a Vue3 library, etc.

[0058] It should be noted that the rendering layer 140 can be a Runt i me Run the rendering library.

[0059] The application layer 150 is located at the fifth layer of the low-code platform 100, and is used to integrate the data of the target rendering strategy and the data of multiple target interface components to generate the development file of the target front-end application. In the application layer 150, the data of the target rendering strategy and the data of multiple target interface components can be integrated, and the data sent by the data layer and / or the component layer can be received and passed to the rendering layer 140 for rendering.

[0060] The application layer 150 may be a design tool of a CMS (Content Management System) Designer.

[0061] In one possible implementation, the core module Core in the protocol processing layer 110 parses the required configuration data to obtain the backend logic data and interface description information of the target front-end application, and then screens out the backend logic data and interface description information that conform to the specifications of the low-code platform 100 according to the verification module Validator, thereby obtaining the data protocol module Data Schema and the page protocol module UI Schema in the data layer 120. Based on the data protocol module Data Schema and / or the page protocol module UI Schema in the data layer 120, in the component layer 130, the preset component library (such as the Antd component library) is called to obtain the data of the target basic components corresponding to the data protocol module Data Schema and / or the page protocol module UI Schema, and then in the rendering layer 140, the data of the target basic components is rendered, and finally integrated and displayed in the application layer 150 to obtain the development files of the target front-end application.

[0062] It should be noted that the protocol processing layer, data layer, component layer, rendering layer and application layer in the low-code platform can interact with each other, and this should not be understood as a limitation on this application.

[0063] The low-code platform provided in the embodiment of the present application is composed of a protocol processing layer, a data layer, a component layer, a rendering layer and an application layer. The protocol processing layer is used to obtain the required configuration data of the target front-end application, and parse the required configuration data to obtain the back-end logic data and interface description information of the target front-end application; the data layer is used to process the back-end logic data and interface description information respectively to generate a data object model and page original data; the component layer is used to obtain the data of multiple target interface components corresponding to the target front-end application from the preset component library according to the data object model and the page original data; the rendering layer is used to determine the data of the target rendering strategy according to the page original data and the data of the target interface component; the application layer is used to integrate the data of the target rendering strategy and the data of multiple target interface components to generate the development file of the target front-end application. Therefore, the low-code platform provided by the present application, because the protocol processing layer uses the protocol specification JSONSchema to define the data structure and business rules, allows users to describe the application in a declarative manner, thereby simplifying the development process. Compared with the traditional programming model, this method effectively lowers the development threshold, enabling non-professional developers to participate in the construction of application development, thereby greatly improving the efficiency of application development. That is, the low-code platform provided by this application significantly improves the efficiency and quality of software development by providing an efficient, intuitive and easy-to-maintain development model, demonstrating significant practical value and market competitiveness.

[0064] The following is a detailed explanation and description of the application building method based on the low-code platform provided in the above embodiment of the present application in conjunction with the accompanying drawings. Figure 2 A schematic diagram of a method for building an application based on a low-code platform provided in an embodiment of the present application Figure 1 .like Figure 2 As shown, the method may include:

[0065] S210, using the protocol processing layer to obtain the required configuration data of the target front-end application, and parse the required configuration data to obtain the back-end logic data and interface description information of the target front-end application.

[0066] In one possible implementation, referring to the above Figure 1 , using the protocol processing layer to obtain the user's demand configuration data in the target front-end application. For example, the user uses a declarative method to describe the demand configuration data in the target application. The demand configuration data, for example, the functional requirements of the target application, enables the protocol processing layer to obtain the demand configuration data of the target front-end application; and read and parse the demand configuration data to obtain the back-end logic data and interface description information corresponding to the target front-end application.

[0067] S220, using the data layer, respectively processing the backend logic data and the interface description information to generate a data object model and page original data.

[0068] In one possible implementation, referring to the above Figure 1 , using the protocol specification JSON Schema in the data layer and the protocol processing layer to interact, process the backend logic data (such as add, delete, modify, and query operations, etc.) and generate a data object model; at the same time, process the interface description information, such as generating page original data according to the description of user requirements. By processing the backend logic data and interface description information, the required configuration data is layered, making the target front-end application easier to maintain and expand.

[0069] The data object model is used to represent the target front-end application's internal configuration data structure and object collection, which represents the target application's business logic and data model. The page metadata is used to describe the structure and behavior of the user interface, usually including the user interface element type, attributes, layout information, and interaction rules between them.

[0070] S230, using the component layer, according to the data object model and the original page data, obtaining data of multiple target interface components corresponding to the target front-end application from the preset component library.

[0071] In one possible implementation, referring to the above Figure 1 Based on the data object model and page original data generated by the data layer, components that conform to the data object model and page original data are selected from the preset component library in the component layer (such as the Antd component library), and the data and attributes of the data object model and page original data are configured respectively. According to the configured data object model and page original data, the data of multiple target interface components corresponding to the target front-end application are obtained.

[0072] S240: Using a rendering layer, determine data of a target rendering strategy according to the original data of the page and data of a target interface component.

[0073] In one possible implementation, referring to the above Figure 1 Based on the original page data and the target interface component data generated by the component layer, the original page data and the target interface component data are rendered in the rendering layer according to a preset rendering method to obtain the data of the target rendering strategy.

[0074] The preset rendering means may be selected according to actual conditions. For example, the preset rendering means may be selected as JavaScript rendering means.

[0075] S250, using the application layer, integrating the data of the target rendering strategy and the data of multiple target interface components to generate a development file of the target front-end application.

[0076] In one possible implementation, referring to the above Figure 1 ,At the application layer, the data of the target rendering strategy and the data of multiple target interface components are integrated to ensure their coordination and consistency, and prepare for the rendering of the target front-end application, and convert the integrated data into a development file in a format that can be understood and used by the target front-end application.

[0077] The embodiment of the present application proposes a method for building an application based on a low-code platform. The low-code platform includes: a protocol processing layer, a data layer, a component layer, a rendering layer and an application layer. The method includes: using the protocol processing layer to obtain the demand configuration data of the target front-end application, and parsing the demand configuration data to obtain the back-end logic data and interface description information of the target front-end application; using the data layer to process the back-end logic data and the interface description information respectively to generate a data object model and page original data; using the component layer to obtain the data of multiple target interface components corresponding to the target front-end application from a preset component library according to the data object model and the page original data, so that by taking advantage of componentized development, developers or users can respond to changes more quickly, reduce duplicate code, and improve the maintainability and scalability of the code; using the rendering layer to determine the data of the target rendering strategy according to the page original data and the data of the target interface component, and through the close collaboration between the rendering layer and the data layer, the component layer and the protocol processing layer, the overall function and performance goals of the target front-end application are achieved; using the application layer, the data of the target rendering strategy and the data of multiple target interface components are integrated to generate the development file of the target front-end application. Therefore, this application uses a declarative approach to describe the target front-end application, thereby simplifying the development process. Compared with the traditional programming model, this approach effectively lowers the development threshold, enabling non-professional developers to participate in application construction, thereby greatly improving development efficiency. Secondly, given that the protocol specification JSON Schema itself has excellent readability and easy editing, developers or users can intuitively review the definition of data structure and business logic, which helps to reduce the error rate and iteration frequency in the development process, and significantly shortens the product design to launch cycle. Finally, the low-code platform also demonstrates a high degree of configurability and scalability. Through the protocol specification JSON Schema, various data types and business rules can be flexibly defined, so that the low-code platform can adapt to the needs of different industries and scenarios. At the same time, low-code platforms are usually equipped with a rich component library and templates, on which developers or users can customize and expand development to meet specific business needs. In addition, low-code platforms play a positive role in improving the maintainability and consistency of applications. Given that both business logic and data structure are managed through the protocol specification JSON Schema, this makes application maintenance and upgrades easier and more intuitive. Furthermore, a unified data description method also facilitates team collaboration and knowledge sharing.

[0078] exist Figure 2 On the basis of Figure 3 Schematic diagram of the process of building an application based on a low-code platform provided in the embodiment of the present application Figure 2 .like Figure 3As shown above, the protocol processing layer is used to obtain the required configuration data of the target front-end application, and the required configuration data is parsed to obtain the back-end logic data and interface description information of the target front-end application, which may include:

[0079] S310. Using the protocol definition module in the protocol processing layer, define the data structure and configure the interface elements of the target front-end application to obtain the required configuration data that meets the data structure definition.

[0080] In one possible implementation, referring to the above Figure 1 , the protocol definition module Schema in the protocol processing layer is used to define the data structure of the target front-end application, so that the data structure in the target front-end application conforms to the data structure definition of the back-end. At the same time, in addition to the data structure definition, the protocol definition module Schema also needs to configure the interface elements of the target front-end application to ensure that the target front-end application can be presented on the user interface in the expected manner and interact with the user. This allows users to more intuitively build and manage the user interface of the target front-end application. That is, the protocol definition module Schema provided in this application can provide developers or users with an efficient and intuitive way to define and extend protocols, thereby meeting various complex user interface requirements.

[0081] S320. Use the verification module in the protocol processing layer to perform format verification on the required configuration data.

[0082] In one possible implementation, referring to the above Figure 1 , the verification module Validator in the protocol processing layer is used to perform format verification on the demand configuration data obtained in step S310. For example, the structure, field name, data type, data length, etc. of the demand configuration data are checked to ensure that they meet the predefined format requirements, thereby ensuring that the configuration data will not be incorrectly parsed or processed during transmission and storage, thereby improving the accuracy of the configuration data, enhancing the stability of the low-code platform, and improving development efficiency.

[0083] S330. Using the reuse module in the protocol processing layer, based on the required configuration data after format verification, determine the target tool function reused by the target front-end application from the preset tool set.

[0084] Among them, the target tool function is used to process the backend logical data.

[0085] In one possible implementation, referring to the above Figure 1Based on the demand configuration data after format verification in the above step S320, the reuse module Shared in the protocol processing layer is used to screen out target tool functions that match the demand configuration data of the target front-end application from the preset tool set according to the information of the demand configuration data, so as to improve code reusability, development efficiency and software quality.

[0086] The preset tool set is a collection of various commonly used tool functions, components or code snippets, which can be selected according to actual conditions. For example, the preset tool set can choose to print logs or deep clone, etc.

[0087] S340. Using the core module in the protocol processing layer, the required configuration data after format verification is parsed to obtain backend logic data and interface description information.

[0088] In one possible implementation, referring to the above Figure 1 , using the core module Core in the protocol processing layer, the structure and content of the required configuration data after format verification are analyzed to obtain the back-end logic data and interface description information, which improves the processing efficiency of the back-end low-code platform and the user experience of the target front-end user interface. Among them, the back-end logic data can be obtained based on the target tool function, which is used for the back-end to guide how to process business logic data; the interface description information is used by the back-end to describe how the target front-end user interface displays and interacts.

[0089] The application construction method based on the low-code platform provided in the embodiment of the present application adopts the protocol definition module in the protocol processing layer to define the data structure and configure the interface elements of the target front-end application, obtain the required configuration data that meets the data structure definition, improve the development efficiency, reduce the communication cost, and ensure the consistency and accuracy of the data exchange between the front and back ends. At the same time, it also promotes the maintainability and scalability of the target front-end application, so that developers or users can respond to demand changes and technical updates more flexibly; adopts the verification module in the protocol processing layer to format the required configuration data to ensure the accuracy and consistency of the required configuration data, thereby improving the stability, development efficiency and reliability of the system; adopts the reuse module in the protocol processing layer, based on the required configuration data after format verification, from the preset tool set, determine the target tool function reused by the target front-end application to improve code reusability, development efficiency and software quality; adopts the core module in the protocol processing layer to parse the required configuration data after format verification to obtain the back-end logic data and interface description information, so as to extract the required configuration data after format verification respectively, so that the back-end logic data and interface description information can be developed in parallel, thereby improving the development efficiency and performance of the low-code platform. Among them, the target tool function is used to process the backend logical data to ensure the accuracy and consistency of the backend logical data, while improving the processing efficiency of the backend low-code platform and the user experience of the user interface of the target front-end application.

[0090] Figure 4 Schematic diagram of the process of building an application based on a low-code platform provided in the embodiment of the present application Figure 3 .like Figure 4 As shown above, the data layer is used to process the backend logic data and interface description information respectively to generate a data object model and page original data, which may include:

[0091] S410: Using the data protocol module in the data layer, according to predefined data configuration information, process the backend logic data to generate a data object model.

[0092] In one possible implementation, referring to the above Figure 1 , using the data protocol module DataSchema in the data layer, the backend logical data is processed according to the predefined data configuration information to generate a data object model, so that the generated data object model after processing meets the internal program running requirements of the target front-end application.

[0093] The predefined data configuration information can be understood as a series of data configuration parameters set during the target front-end application development phase, which are used to guide the data protocol module Data Schema on how to process the back-end logical data. The series of data configuration parameters may include: data format, structure, field mapping, data verification rules, etc., which are not limited here.

[0094] S420: Using the page protocol module in the data layer, according to the predefined page rendering configuration information, the interface description information is processed to generate page original data.

[0095] In one possible implementation, referring to the above Figure 1 , the page protocol module UISchema in the data layer is used to process the interface description information according to the predefined page rendering configuration information to generate page original data, so that the processed page original data can be correctly rendered in the target front-end application.

[0096] The predefined page rendering configuration information can be understood as a series of page configuration parameters set during the target front-end application development phase, which are used to guide the page protocol module UI Schema on how to process the interface description information. The series of page configuration parameters may include the layout of the page, the style of the components, the display method of the data, etc., which are not limited here.

[0097] The application construction method based on the low-code platform provided in the embodiment of the present application adopts the data protocol module in the data layer to process the back-end logical data according to the predefined data configuration information, and generate a data object model, so that the data object model generated after processing meets the internal program running requirements of the target front-end application; adopts the page protocol module in the data layer to process the interface description information according to the predefined page rendering configuration information, and generates the page original data, so that the page original data generated after processing can be correctly rendered in the target front-end application. Therefore, the present application helps to realize the fast, accurate and consistent generation of pages through the processing of the back-end logical data and interface description information by the data layer, improves the development efficiency and user experience, and ensures the compatibility and consistency of the user interface on different devices and preset platforms.

[0098] Figure 5 Schematic diagram of the process of building an application based on a low-code platform provided in the embodiment of the present application Figure 4 .like Figure 5 As shown above, the component layer is used to obtain data of multiple target interface components corresponding to the target front-end application from the preset component library according to the data object model and the original page data, which may include:

[0099] S510, using the component layer, according to the data object model and the original data of the page, obtaining the data of the target basic component from the preset basic component library.

[0100] In one possible implementation, referring to the above Figure 1 , using the component layer, according to the data object model and the page original data, select the required components that meet the data object model and the page original data from the preset basic component library, and then obtain the data of the target basic component based on these required components.

[0101] The preset basic component library contains a collection of basic components. These basic components are the cornerstones for building more complex UI components. They usually provide common UI functions (such as buttons, input boxes, lists, etc.) and styles, etc., which are not limited here.

[0102] S520, using the component layer, according to the data object model and the original page data, obtaining the data of the target desktop component from the desktop component libraries corresponding to at least two different development frameworks.

[0103] In one possible implementation, referring to the above Figure 1 , using the component layer, according to the data object model and the page original data, select the required components that meet the data object model and the page original data from the desktop component libraries corresponding to at least two different development frameworks, and then obtain the data of the target desktop component according to these required components. Among them, the multiple target interface components may include: target basic components and target desktop components.

[0104] Among them, at least two different development frameworks can be selected according to actual conditions, for example, the at least two different development frameworks can be selected as DOM (Document Object Model) development frameworks. It should be noted that each development framework has its own set of corresponding component libraries for building the user interface of the application.

[0105] The desktop component library contains various UI components required to build desktop applications, such as buttons, input boxes, windows, menus, etc. There is no restriction here.

[0106] The application construction method based on the low-code platform provided in the embodiment of the present application adopts a component layer to obtain the data of the target basic component from the preset basic component library according to the data object model and the page original data; adopts a component layer to obtain the data of the target desktop component from the desktop component library corresponding to at least two different development frameworks according to the data object model and the page original data; wherein the multiple target interface components include: a target basic component and a target desktop component. Therefore, when constructing the data of multiple target interface components corresponding to the target front-end application, the present application involves directly obtaining the data of the target basic component from the preset basic component library and obtaining the data of the target desktop component from the component library of multiple different development frameworks. This process generally requires the developer or user to have the ability to develop across frameworks, but according to the application construction method based on the low-code platform provided in the present application, it is possible to simply and effectively manage and integrate components from different sources, thereby improving development efficiency and user experience. At the same time, the developer or user can focus on the specific implementation of the components in the component layer without worrying about compatibility issues with the preset platform, thereby greatly simplifying the development and integration process.

[0107] Optionally, as an optional implementation, the rendering layer is used as shown above, and the data of the target rendering strategy is determined according to the original data of the page and the data of the target interface component, which may include:

[0108] The rendering layer is used to determine the data of the target rendering strategy according to the original data of the page, the data of the target interface component, and the information of the page block where the target interface component is located.

[0109] In one possible implementation, referring to the above Figure 1 , using at least one preset rendering database for building a user interface in the rendering layer, such as a React library, the original page data and the data of the target interface component in the component layer, as well as the information of the page block where the target interface component is located, for example, the position on the page block or the page block to which it belongs (such as a header, a footer, a sidebar, a main content area, etc.), are rendered according to a preset rendering method (such as a JavaScript rendering method) to obtain data of the target rendering strategy.

[0110] It should be noted that in the process of the core module Core in the protocol processing layer parsing the required configuration data, or parsing the original page data and the data of the target interface component in the component layer, as well as the information of the page block where the target interface component is located, the rendering layer can adopt different rendering strategies according to different application scenarios, such as pages, blocks and materials. This flexible rendering method ensures that efficient and optimized rendering performance can be provided in various scenarios to meet the needs of different users. Whether it is a large page or a small component, the rendering layer can perform targeted optimized rendering according to its data characteristics to ensure that the final rendering effect is both fast and accurate.

[0111] The application building method based on the low-code platform provided in the embodiment of the present application adopts a rendering layer to determine the data of the target rendering strategy according to the original data of the page, the data of the target interface component, and the information of the page block where the target interface component is located, thereby ensuring that the rendered page meets the design requirements and can provide an efficient interactive experience.

[0112] Optionally, as an optional implementation, the application layer is used as shown above to integrate the data of the target rendering strategy and the data of multiple target interface components to generate the development file of the target front-end application, which may include:

[0113] The application layer is used to perform persistence processing on the data of the target rendering strategy and the data of multiple target interface components according to the first usage mode, and a development file of the target front-end application is generated.

[0114] Among them, the first usage mode is that the application layer can choose to use the renderer and designer components provided by the target front-end application. At this time, the application layer itself needs to be responsible for maintaining the persistent management of the protocol. This means that the application layer needs to have certain development capabilities in order to be able to integrate and use these components. In this way, the application layer can better control the design and management process of the protocol, thereby achieving more flexible customization requirements.

[0115] In one possible implementation, referring to the above Figure 1 In the application layer, according to the first usage mode (such as using the renderer and designer components provided by the target front-end application), the data of the target rendering strategy and the data of multiple target interface components are persisted so that they can be accessed and used again when needed, and then the source code and resource files required by the target front-end application, i.e., development files, are created for the persisted data.

[0116] The application building method based on the low-code platform provided in the embodiment of the present application adopts the application layer, and according to the first usage method, persists the data of the target rendering strategy and the data of multiple target interface components, and generates the development file of the target front-end application to ensure that the target front-end application can correctly display the data and provide a good user experience, while improving the maintainability and scalability of the target front-end application, and enhancing the functionality and user experience of the application layer.

[0117] Optionally, as an optional implementation, the application layer is used as shown above to integrate the data of the target rendering strategy and the data of multiple target interface components to generate the development file of the target front-end application, which may include:

[0118] By using the application layer, according to the second usage mode, embedded integration is performed on the data of the target rendering strategy and the data of multiple target interface components to generate a development file of the target front-end application program.

[0119] Among them, the second usage mode is that the application layer can choose to use the built-in service provided by the target front-end application to perform protocol design and management. In this way, the application layer does not need to maintain the persistent management of the protocol by itself, but can directly use the built-in service provided by the target front-end application to complete the design and management of the protocol. And in the actual usage scenario, the application layer can render the page in an embedded manner, and integrate the designed protocol into the application layer in an embedded manner. This method is relatively simple and suitable for scenarios that do not have development capabilities or expect rapid integration.

[0120] In one possible implementation, referring to the above Figure 1 In the application layer, according to the second usage mode (e.g., using the built-in services provided by the target front-end application), the data of the target rendering strategy and the data of multiple target interface components are embedded integrated to ensure the immediate availability of the development files of the embedded integrated target front-end application and reduce the dependence on external services.

[0121] It should be noted that third-party applications can choose the appropriate usage method to integrate the development file according to their own needs and development capabilities. Whether choosing to use the renderer and designer components for persistence management, or choosing to use the built-in service for protocol design management and embedding for page rendering, effective integration with the development file can be achieved, thereby improving the application's functionality and user experience.

[0122] The application building method based on the low-code platform provided in the embodiment of the present application adopts the application layer, and according to the second usage method, embeds the data of the target rendering strategy and the data of multiple target interface components to generate the development file of the target front-end application, so as to ensure that the target front-end application can correctly display and process data, while reducing the dependence on external services, improving the immediate availability and performance of the development files of the target front-end application, and enhancing the functions and user experience of the application layer.

[0123] To facilitate understanding of the above-mentioned application construction method based on the low-code platform, the embodiment of the present application also provides an example of the process of the application application method based on the low-code platform, which is further described in conjunction with the accompanying drawings as follows: Figure 6 The following is a flow chart of an application application method based on a low-code platform provided in an embodiment of the present application. Figure 6 As shown, the application method provided by the embodiment of the present application may include:

[0124] S610. In the target front-end application, install the development files of the low-code platform.

[0125] Specifically, in the target front-end application, it can be installed by calling the development files or other forms of the low-code platform provided by this application.

[0126] It should be noted that the method of installing the development files of the low-code platform in the target front-end application can be selected according to the actual situation, and there are no restrictions here.

[0127] S620: Obtain required configuration data of the target front-end application.

[0128] Specifically, the user or developer performs requirement configuration on the target front-end application so that the application layer of the target front-end application obtains the requirement configuration data.

[0129] S630: parse the required configuration data to generate a data object model and page original data.

[0130] Specifically, the application layer of the low-code platform passes the demand configuration data to the rendering layer. The rendering layer calls the core module Core in the protocol processing layer to parse the demand configuration data and obtain the back-end logic data and interface description information of the parsed target front-end application. Then, the validation module Validator is used to perform format validation on the back-end logic data and interface description information of the target front-end application to ensure that they meet the predefined format requirements. Finally, the data protocol module Data Schema in the data layer is used to process the back-end logic data according to the predefined data configuration information to generate a data object model; at the same time, the page protocol module UI Schema in the data layer is used to process the interface description information according to the predefined page rendering configuration information to generate the page original data.

[0131] S640: Based on the data object model and the original page data, data of multiple target interface components corresponding to the target front-end application are obtained from the preset component library.

[0132] Specifically, according to the data object model and the page original data, the required components that meet the data object model and the page original data are selected from the preset basic component library, and then the data of the target basic components are obtained according to these required components.

[0133] It should be noted that if a component that meets the requirements of the data object model and the page original data is not selected from the preset basic component library, it is necessary to re-register the corresponding component based on the data object model and the page original data.

[0134] S650: Rendering the data of multiple target interface components and the original page data.

[0135] Specifically, when rendering the data of multiple target interface components and the original data of the page, all the attribute information that the data of multiple target interface components found by the component layer and the original data of the page depend on can be rendered to obtain the data of the rendered target rendering strategy.

[0136] S660: Integrate the data of the target rendering strategy and the data of multiple target interface components to generate a user interface of the target front-end application.

[0137] Specifically, the data of the target rendering strategy and the data of multiple target interface components are integrated according to a first usage mode (e.g., using the renderer and designer components provided by the target front-end application) or according to a second usage mode (e.g., using the built-in services provided by the target front-end application) to generate a development file of the target front-end application. The development file allows users to describe the target front-end application based on their own declarative means, automatically generates a user interface that meets user expectations, effectively lowers the development threshold, and enables non-professional developers to participate in application construction, thereby greatly improving development efficiency.

[0138] The application construction method based on the low-code platform provided in the embodiment of the present application is to install the development files of the low-code platform in the target front-end application, obtain the required configuration data of the target front-end application; parse the required configuration data to generate a data object model and page original data; based on the data object model and page original data, obtain the data of multiple target interface components corresponding to the target front-end application from the preset component library; render the data of multiple target interface components and the page original data, and integrate the data of the target rendering strategy and the data of multiple target interface components to generate the user interface of the target front-end application. Therefore, the present application adopts a declarative method to describe the target front-end application, thereby simplifying the development process. Compared with the traditional programming model, this method effectively lowers the development threshold, enabling non-professional developers to participate in application construction, thereby greatly improving development efficiency.

[0139] Based on the same inventive concept, an embodiment of the present application also provides an application construction device based on a low-code platform. Since the principle of solving the problem by the device in the embodiment of the present application is similar to the above-mentioned application construction method based on the low-code platform in the embodiment of the present application, the implementation of the device can refer to the implementation of the method, and the repeated parts will not be repeated.

[0140] Figure 7 A schematic diagram of a structure of an application building device based on a low-code platform provided in an embodiment of the present application. Figure 7 As shown, the application building device 70 based on the low-code platform includes: a protocol processing layer, a data layer, a component layer, a rendering layer and an application layer, which may include:

[0141] The parsing module 71 is used to obtain the required configuration data of the target front-end application using the protocol processing layer, and parse the required configuration data to obtain the back-end logic data and interface description information of the target front-end application;

[0142] The processing module 72 is used to process the backend logic data and the interface description information respectively using the data layer to generate a data object model and page original data;

[0143] The acquisition module 73 is used to acquire data of multiple target interface components corresponding to the target front-end application from the preset component library using the component layer according to the data object model and the original page data;

[0144] A determination module 74 is used to use a rendering layer to determine data of a target rendering strategy according to the original data of the page and the data of the target interface component;

[0145] The integration module 75 is used to integrate the data of the target rendering strategy and the data of multiple target interface components by using the application layer to generate the development file of the target front-end application program.

[0146] In an optional embodiment, the parsing module 71 is specifically used to: use the protocol definition module in the protocol processing layer to define the data structure and configure the interface elements of the target front-end application to obtain the required configuration data that meets the data structure definition; use the verification module in the protocol processing layer to perform format verification on the required configuration data; use the reuse module in the protocol processing layer to determine the target tool function reused by the target front-end application from a preset tool set based on the required configuration data after format verification; use the core module in the protocol processing layer to parse the required configuration data after format verification to obtain back-end logic data and interface description information, wherein the target tool function is used to perform data processing on the back-end logic data.

[0147] In an optional embodiment, the processing module 72 is specifically used to: use the data protocol module in the data layer to process the backend logical data according to predefined data configuration information to generate a data object model; use the page protocol module in the data layer to process the interface description information according to predefined page rendering configuration information to generate page original data.

[0148] In an optional embodiment, the acquisition module 73 is specifically used to: adopt a component layer to acquire data of a target basic component from a preset basic component library according to a data object model and page original data; adopt a component layer to acquire data of a target desktop component from a desktop component library corresponding to at least two different development frameworks according to a data object model and page original data; wherein the multiple target interface components include: a target basic component and a target desktop component.

[0149] In an optional implementation, the determination module 74 is specifically used to: use a rendering layer to determine the data of a target rendering strategy according to the original data of the page, the data of the target interface component, and the information of the page block where the target interface component is located.

[0150] In an optional implementation, the integration module 75 is specifically used to: use the application layer, according to the first usage mode, to persist the data of the target rendering strategy and the data of multiple target interface components, and generate the development file of the target front-end application.

[0151] In an optional implementation, the integration module 75 is specifically used to: adopt the application layer, according to the second usage mode, perform embedded integration on the data of the target rendering strategy and the data of multiple target interface components, and generate a development file of the target front-end application.

[0152] It should be noted that for details not disclosed in the application building device based on the low-code platform in the embodiment of the present application, please refer to the details disclosed in the application building method based on the low-code platform in the embodiment of the present application, and the details will not be repeated here.

[0153] Optionally, the embodiment of the present application further provides a computer device 80, such as Figure 8 As shown, Figure 8 Schematic diagram of the computer device structure provided in the embodiment of the present application. The computer device 80 may include: a processor 81, a memory 82, and optionally, a bus. The memory 82 stores machine-readable instructions executable by the processor 81 (for example, Figure 7 The parsing module, processing module, acquisition module, determination module and execution instructions corresponding to the integration module in the device, etc.), when the computer device 80 is running, the processor 81 communicates with the memory 82 through a bus, and when the machine-readable instructions are executed by the processor 81, the method steps described in the aforementioned method embodiment are executed.

[0154] Among them, the memory 82 can be, but is not limited to, random access memory (Random Access Memory, RAM), read only memory (Read Only Memory, ROM), programmable read-only memory (Programmable Read-Only Memory, PROM), erasable programmable read-only memory (Erasable Programmable Read-Only Memory, EPROM), electrically erasable read-only memory (Electric Erasable Programmable Read-Only Memory, EEPROM), etc.

[0155] Optionally, the embodiment of the present application further provides a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, the steps of the above-mentioned method for building an application based on a low-code platform are executed. The specific implementation method and technical effect are similar and will not be repeated here.

[0156] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0157] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0158] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of hardware plus software functional units.

[0159] The above-mentioned integrated unit implemented in the form of a software functional unit can be stored in a computer-readable storage medium. The above-mentioned software functional unit is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor (English: processor) to perform some steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (English: Read-Only Memory, abbreviated: ROM), random access memory (English: Random Access Memory, abbreviated: RAM), disk or optical disk and other media that can store program codes.

[0160] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions that can be easily thought of by a person skilled in the art within the technical scope disclosed in the present application should be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be based on the protection scope of the claims.

Claims

1. A method for building an application based on a low-code platform, characterized in that: The low-code platform includes: a protocol processing layer, a data layer, a component layer, a rendering layer and an application layer. The method includes: The protocol processing layer is used to obtain the required configuration data of the target front-end application, and the required configuration data is parsed to obtain the back-end logic data and interface description information of the target front-end application; The data layer is used to process the backend logic data and the interface description information respectively to generate a data object model and page original data; Using the component layer, according to the data object model and the page original data, the data of multiple target interface components corresponding to the target front-end application are obtained from a preset component library; Using the rendering layer, determining data of a target rendering strategy according to the original data of the page and the data of the target interface component; The application layer is used to integrate the data of the target rendering strategy and the data of the multiple target interface components to generate a development file of the target front-end application.

2. The method for building an application based on a low-code platform according to claim 1, characterized in that: The protocol processing layer is used to obtain the required configuration data of the target front-end application, and the required configuration data is parsed to obtain the back-end logic data and interface description information of the target front-end application, including: Using the protocol definition module in the protocol processing layer, the target front-end application is subjected to data structure definition and interface element configuration to obtain the required configuration data satisfying the data structure definition; Using the verification module in the protocol processing layer to perform format verification on the required configuration data; Using the reuse module in the protocol processing layer, based on the required configuration data after format verification, determine the target tool function reused by the target front-end application from the preset tool set; The core module in the protocol processing layer is used to parse the required configuration data after format verification to obtain the backend logic data and the interface description information, wherein the target tool function is used to perform data processing on the backend logic data.

3. The method for building an application based on a low-code platform according to claim 1, characterized in that: The data layer is used to process the backend logic data and the interface description information respectively to generate a data object model and page original data, including: Using the data protocol module in the data layer, the backend logic data is processed according to predefined data configuration information to generate the data object model; The page protocol module in the data layer is used to process the interface description information according to predefined page rendering configuration information to generate the page original data.

4. The method for building an application based on a low-code platform according to claim 1, characterized in that: The adopting of the component layer to obtain data of a plurality of target interface components corresponding to the target front-end application from a preset component library according to the data object model and the page original data includes: Using the component layer, according to the data object model and the page original data, the data of the target basic component is obtained from the preset basic component library; The component layer is used to obtain data of the target desktop component from desktop component libraries corresponding to at least two different development frameworks according to the data object model and the page original data; wherein the multiple target interface components include: the target basic component and the target desktop component.

5. The method for building an application based on a low-code platform according to claim 1, characterized in that: The using the rendering layer to determine the data of the target rendering strategy according to the original data of the page and the data of the target interface component includes: The rendering layer is used to determine the data of the target rendering strategy according to the original data of the page, the data of the target interface component, and the information of the page block where the target interface component is located.

6. The method for building an application based on a low-code platform according to claim 1, characterized in that: The adopting of the application layer to integrate the data of the target rendering strategy and the data of the plurality of target interface components to generate the development file of the target front-end application program includes: The application layer is used to perform persistence processing on the data of the target rendering strategy and the data of the multiple target interface components according to the first usage mode, and a development file of the target front-end application is generated.

7. The method for building an application based on a low-code platform according to claim 1, characterized in that: The adopting of the application layer to integrate the data of the target rendering strategy and the data of the plurality of target interface components to generate the development file of the target front-end application program includes: The application layer is used to perform embedded integration of the data of the target rendering strategy and the data of the multiple target interface components according to the second usage mode to generate a development file of the target front-end application.

8. A low-code platform, characterized in that: The low-code platform includes: a protocol processing layer, a data layer, a component layer, a rendering layer, and an application layer; The protocol processing layer is used to obtain the required configuration data of the target front-end application, and parse the required configuration data to obtain the back-end logic data and interface description information of the target front-end application; The data layer is used to process the backend logic data and the interface description information respectively to generate a data object model and page original data; The component layer is used to obtain data of multiple target interface components corresponding to the target front-end application from a preset component library according to the data object model and the original page data; The rendering layer is used to determine the data of the target rendering strategy according to the original data of the page and the data of the target interface component; The application layer is used to integrate the data of the target rendering strategy and the data of the multiple target interface components to generate the development file of the target front-end application.

9. A computer device, characterized in that: include: A processor and a memory, wherein the memory stores machine executable instructions that can be executed by the processor, and the processor can execute the machine executable instructions to implement any method of claims 1-7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.

Images