Low-code development method and device, computer equipment and storage medium

Abstract

The embodiment of the invention belongs to the field of research and development management, and relates to a low-code development method which comprises the following steps: acquiring a plug-in package of a low-code development platform; obtaining a project configuration file of a to-be-developed project, wherein the project configuration file records resources required by the to-be-developed project; registering the plug-in package to the to-be-developed project according to the project configuration file to obtain a low-code development plug-in; and performing low-code development on the to-be-developed project through the low-code development plug-in. The invention further provides a low-code development device, computer equipment and a storage medium. In addition, the invention also relates to a block chain technology, and the plug-in package can be stored in a block chain. According to the invention, the flexibility of low-code development is improved.

Description

Technical Field

[0001] The present application relates to the field of R&D management technology, and in particular to a low-code development method, apparatus, computer equipment and storage medium. Background Art

[0002] At present, software development technology is becoming increasingly mature, but it still takes a lot of time and manpower to develop a complete software system. For this reason, low-code development technology came into being. Low-code development technology reduces the amount of coding and speeds up application delivery through visual software development methods. However, low-code development technology also has some obvious shortcomings in application. Many front-end low-code platforms integrate specific component libraries, which restricts developers from using frameworks and component libraries that they are familiar with or need, affecting the flexibility of development. Taking some platforms as an example, if the built-in Element UI component library is the Element UI component library, and the developer needs to use the Vue i View or Ant Design Vue component library, this mismatch will bring many inconveniences. In addition, existing projects also face many challenges when using low-code development. Existing projects often contain a large number of custom components and public methods, which are difficult to reuse directly on low-code platforms, affecting the flexibility and efficiency of low-code development. Summary of the invention

[0003] The purpose of the embodiments of the present application is to propose a low-code development method, apparatus, computer equipment and storage medium to solve the problem of poor flexibility of low-code development.

[0004] In order to solve the above technical problems, the embodiment of the present application provides a low-code development method, which adopts the following technical solution:

[0005] Get the plugin package for the low-code development platform;

[0006] Obtaining a project configuration file of a project to be developed, wherein the project configuration file records resources required by the project to be developed;

[0007] Registering the plug-in package to the project to be developed according to the project configuration file to obtain a low-code development plug-in;

[0008] The low-code development plug-in is used to perform low-code development on the project to be developed.

[0009] In order to solve the above technical problems, the embodiment of the present application also provides a low-code development device, which adopts the following technical solution:

[0010] The plug-in package acquisition module is used to obtain the plug-in package of the low-code development platform;

[0011] A configuration acquisition module is used to acquire a project configuration file of a project to be developed, wherein the project configuration file records resources required by the project to be developed;

[0012] A plug-in registration module, used to register the plug-in package to the project to be developed according to the project configuration file to obtain a low-code development plug-in;

[0013] A project development module is used to perform low-code development on the project to be developed through the low-code development plug-in.

[0014] In order to solve the above technical problems, the embodiment of the present application further provides a computer device, which adopts the following technical solution:

[0015] Get the plugin package for the low-code development platform;

[0016] Obtaining a project configuration file of a project to be developed, wherein the project configuration file records resources required by the project to be developed;

[0017] Registering the plug-in package to the project to be developed according to the project configuration file to obtain a low-code development plug-in;

[0018] The low-code development plug-in is used to perform low-code development on the project to be developed.

[0019] In order to solve the above technical problems, the embodiment of the present application further provides a computer-readable storage medium, which adopts the following technical solution:

[0020] Get the plugin package for the low-code development platform;

[0021] Obtaining a project configuration file of a project to be developed, wherein the project configuration file records resources required by the project to be developed;

[0022] Registering the plug-in package to the project to be developed according to the project configuration file to obtain a low-code development plug-in;

[0023] The low-code development plug-in is used to perform low-code development on the project to be developed.

[0024] Compared with the prior art, the embodiments of the present application mainly have the following beneficial effects: obtaining a plug-in package of a low-code development platform and obtaining a project configuration file of a project to be developed, the project configuration file recording the resources required for the project to be developed; the low-code development platform is used as an auxiliary tool and does not have built-in basic components; the plug-in package is registered to the project to be developed according to the project configuration file to obtain a low-code development plug-in, and the low-code platform dynamically loads the required resources by reading the project configuration file of the project to be developed, thereby avoiding the problem of the low-code development platform's dependence on a specific component library, being able to use the component library and custom resources of the project to be developed itself, and being flexibly applied to different development environments; performing low-code development on the project to be developed through a low-code development plug-in greatly improves the flexibility and compatibility of low-code development. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] In order to more clearly illustrate the scheme in the present application, a brief introduction is given below to the drawings required for use in the description of the embodiments of the present application. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0026] Figure 1 is an exemplary system architecture diagram to which the present application may be applied;

[0027] Figure 2 is a flowchart of an embodiment of a low-code development method according to the present application;

[0028] Figure 3 is a structural schematic diagram of an embodiment of a low-code development device according to the present application;

[0029] Figure 4 It is a structural diagram of an embodiment of a computer device according to the present application. DETAILED DESCRIPTION

[0030] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by technicians in the technical field of the present application; the terms used in the specification of the application herein are only for the purpose of describing specific embodiments and are not intended to limit the present application; the terms "including" and "having" and any variations thereof in the specification and claims of the present application and the above-mentioned drawings are intended to cover non-exclusive inclusions. The terms "first", "second", etc. in the specification and claims of the present application or the above-mentioned drawings are used to distinguish different objects, not to describe a specific order.

[0031] Reference to "embodiments" herein means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present application. The appearance of the phrase in various locations in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0032] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the accompanying drawings.

[0033] like Figure 1 As shown, the system architecture 100 may include terminal devices 101, 102, 103, a network 104 and a server 105. The network 104 is used to provide a medium for communication links between the terminal devices 101, 102, 103 and the server 105. The network 104 may include various connection types, such as wired, wireless communication links or optical fiber cables, etc.

[0034] Users can use terminal devices 101, 102, 103 to interact with server 105 through network 104 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 101, 102, 103, such as web browser applications, shopping applications, search applications, instant messaging tools, email clients, social platform software, etc.

[0035] The terminal devices 101, 102, and 103 can be various electronic devices with display screens and supporting web browsing, including but not limited to smart phones, tablet computers, e-book readers, MP3 players (Moving Picture Experts Group Audio Layer III), MP4 (Moving Picture Experts Group Audio Layer IV) players, laptop computers, desktop computers, etc.

[0036] The server 105 may be a server that provides various services, such as a background server that provides support for web pages displayed on the terminal devices 101 , 102 , and 103 .

[0037] It should be noted that the low-code development method provided in the embodiment of the present application is generally executed by a terminal device, and accordingly, the low-code development device is generally set in the terminal device.

[0038] It should be understood that Figure 1The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to implementation requirements.

[0039] Continue to refer Figure 2 , showing a flow chart of an embodiment of a low-code development method according to the present application. The low-code development method comprises the following steps:

[0040] Step S201, obtain the plug-in package of the low-code development platform.

[0041] In this embodiment, the electronic device (e.g. Figure 1 The server / terminal device shown in the figure can communicate via a wired connection or a wireless connection. It should be noted that the wireless connection method may include but is not limited to 3G / 4G / 5G connection, Wi-Fi connection, Bluetooth connection, Wi MAX connection, Zigbee connection, UWB (Ultra Wi-Fi Band) connection, and other wireless connection methods currently known or to be developed in the future.

[0042] Specifically, first obtain the plug-in package of the low-code development platform. This application has plug-in-ized the low-code development platform. The plug-in package includes the core functions of the low-code development platform, such as a visual editing engine, a code generation engine, etc.

[0043] Furthermore, before the above step S201, it may also include: packaging the low-code platform to generate an NPM package file; publishing the NPM package file as a plug-in package to NPM for download by each project to be developed.

[0044] Specifically, the low-code platform is packaged in advance to generate an NPM package file.

[0045] NPM (Node Package Manager) is a package manager for Node.js, which makes the installation, version control, and dependency management of Node.js packages (such as libraries, tools, and builds) simple. NPM also provides functions such as publishing and sharing code, managing dependencies, and version control. NPM allows developers to install, update, and manage Node.js software packages from its registry; it can automatically handle the installation and version control of project dependencies; developers can also upload their own packaged resource packages.

[0046] NPM packages cover almost all code packages that can be installed through NPM, including but not limited to libraries, frameworks, tools, etc. NPM packages can have a variety of uses, such as providing function libraries for data processing, build tools, development frameworks, etc. NPM packages can also be used as plug-ins, especially those that provide extended functionality for specific software or platforms.

[0047] The packaging process includes packaging the core functions of the low-code development platform into an independent package that can be managed through NPM. The generated NPM package file is then published to the public repository of NPM. In this way, all developers can download and use the plug-in package of the low-code development platform through NPM.

[0048] In this embodiment, the low-code platform is packaged to generate an NPM package file; the NPM package file is published to NPM as a plug-in package for download by each project to be developed, making the distribution and use of the low-code development platform more convenient and standardized. Developers can add the plug-in package of the low-code development platform to the project through NPM, which simplifies the management and use of the plug-in package; through the version management function of the NPM warehouse, the low-code development platform can be easily updated and maintained to ensure that the plug-in package is always the latest version, reducing version compatibility issues.

[0049] Furthermore, in another embodiment, before the above-mentioned step S201, it may also include: obtaining a plug-in generation configuration file of the low-code development platform; extracting the function type recorded in the plug-in generation configuration file, and obtaining the function code corresponding to the function type; plug-in-processing the obtained function code to obtain a plug-in package of the low-code development platform.

[0050] Specifically, the plug-in generation configuration file of the low-code development platform is obtained, and the plug-in generation configuration file records the functions of the low-code development platform selected by the developer. This application disassembles the core functions of the low-code development platform (such as component visualization function, visual editing engine, code generation engine, component management, etc.), and developers can select different function types as needed, flexibly combine the required functions, and obtain the plug-in generation configuration file.

[0051] Parse the plugin to generate a configuration file, extract the function type from it, and obtain the function code corresponding to each function type. Then, process the obtained function code into a plug-in, including packaging the function code in a preset package format (such as NPM package format), and ensure that it can be used as an independent plug-in package, and finally generate a plug-in package for the low-code development platform.

[0052] In this embodiment, the corresponding function code is obtained according to the function type pre-selected by the developer in the plug-in generation configuration file; the function code is plug-in-processed to obtain a plug-in package for the low-code development platform, thereby realizing flexible selection and combination of the core functions of the low-code development platform according to project requirements, improving the reusability, flexibility and adaptability of the plug-in package, and avoiding the waste of resources caused by unnecessary functions.

[0053] Step S202: obtaining a project configuration file of the project to be developed, where the project configuration file records the resources required by the project to be developed.

[0054] Specifically, it is also necessary to obtain the project configuration file of the project to be developed, which records the various resources required for the project to be developed. In this application, the low-code development platform / low-code development plug-in will no longer have a built-in specific basic component library, but will dynamically load the component library according to the project configuration file of the current project. For example, Project A uses the Vue framework and the Ant Design Vue component library. After installing the low-code development plug-in through the NPM package file, the Ant Design Vue component library can be automatically loaded and used according to the project configuration file of Project A without changing the original code. For another example, there is an existing project B, which already has many customized business components and public methods. This application allows these customized components and methods to be directly loaded into the low-code development plug-in for use through the project configuration file without the need for manual migration or adaptation. This application solves the problems of component library limitations and poor adaptability of existing projects brought about by traditional low-code development platforms through project configuration files.

[0055] Furthermore, before the above step S202, it can also include: determining the resources required for the project to be developed, the resources include component libraries, custom components, public methods and page templates; obtaining resource paths of various resources; generating a path file according to the resource paths of various resources, and generating a project configuration file for the project to be developed according to the path file.

[0056] Specifically, the developer determines the resources required for the project to be developed, which include but are not limited to component libraries, custom components, public methods, and page templates. The developer needs to list all necessary resources according to the project requirements.

[0057] Get the resource path of various resources. The resource path is the specific storage location of the resource in the project. It can be a local file path or the address of a remote warehouse. Generate a path file based on the resource path to record the path information of all resources for subsequent parsing and loading. Format the information in the path file to generate a project configuration file that meets the requirements of the plug-in package.

[0058] In this embodiment, the component library, custom components, public methods, page templates, etc. required for the project to be developed are determined; the resource paths of these resources are obtained and a path file is generated, and a project configuration file for the project to be developed is generated based on the path file, thereby ensuring that the required resources can be correctly identified and loaded in the future, improving maintainability and scalability, solving the shortcomings of existing low-code development platforms in resource loading and management, and enhancing the flexibility of low-code development.

[0059] Step S203: register the plug-in package to the project to be developed according to the project configuration file to obtain a low-code development plug-in.

[0060] Specifically, the plug-in package is registered to the project to be developed to obtain a low-code development plug-in. The registration process requires the use of a project configuration file so that the low-code development plug-in can identify and obtain the resources used by the project to be developed.

[0061] Furthermore, the above step S203 may include: adding the plug-in package to the project to be developed; parsing the project configuration file to obtain project configuration parameters; exposing the entry method of the plug-in package; registering the plug-in package to the project instance in the project to be developed through the entry method, and passing in the project configuration parameters during the registration process to obtain a low-code development plug-in, and the project configuration parameters instruct the low-code development plug-in to obtain the resources required for the project to be developed, and the resources include component libraries, custom components, public methods and page templates.

[0062] Specifically, the plug-in package is placed into the project to be developed through a package management tool (such as NPM), and then the project configuration file is parsed to obtain project configuration parameters. The project configuration parameters may be resource types and their corresponding resource paths.

[0063] . Then expose the entry method of the plug-in package. The entry method of the plug-in package refers to the specific method of registering and initializing the plug-in package in the project to be developed. For example, the common method for registering plug-ins in Vue.js is Vue.use().

[0064] The plug-in package is registered to the project instance in the project to be developed through the entry method. During the registration process, the project configuration parameters are also passed to the plug-in package through the entry method, so that the low-code development plug-in can identify and obtain the resources pointed to by the project configuration parameters, including component libraries, custom components, public methods, and page templates, so that these resources can be correctly loaded and used. The generated low-code development plug-in supports developers in low-code development by loading the resources of the project to be developed and providing functions such as visual editing and code generation.

[0065] In this embodiment, the project configuration file is parsed to obtain the project configuration parameters; the plug-in package is registered to the project instance in the project to be developed through the entry method of the plug-in package, and the project configuration parameters are passed in to ensure that the low-code development plug-in can correctly load and use the resources required for the project to be developed, including component libraries, custom components, public methods and page templates, which simplifies the registration and initialization process of the plug-in package and improves development efficiency.

[0066] Step S204: Perform low-code development on the project to be developed through a low-code development plug-in.

[0067] Specifically, developers use low-code development plug-ins to perform low-code development on the projects to be developed. The low-code development plug-in provides a visual interface, and developers can quickly build the application interface and generate the corresponding code by dragging and dropping components and configuring parameters. During the development process, the project to be developed is the main one, and the low-code development plug-in is supplemented as an auxiliary tool; the low-code development plug-in can dynamically load the component library, custom components, public methods, and page templates of the project to be developed, which can flexibly adapt to project needs without replacing any existing components.

[0068] Furthermore, the above step S204 may include: displaying the visual editing interface of the low-code development plug-in through the terminal, and obtaining the visual editing operation triggered in the visual editing interface; loading the resources corresponding to the visual editing operation through the low-code development plug-in, and performing low-code development based on the resources; when the low-code development is completed, generating project code through the low-code development plug-in, and integrating the project code into the project to be developed to obtain a completed project.

[0069] Specifically, the visual editing interface of the low-code development plug-in is displayed through the terminal held by the developer. The visual editing interface is an operating interface for developers to drag components, configure properties, and layout pages through a graphical interface. Developers trigger visual editing operations in the visual editing interface, including specific operations such as dragging components, configuring properties, and binding events.

[0070] The low-code development plug-in loads the resources corresponding to the visual editing operations, including calling components in the component library, custom components, public methods, and page templates, thereby assisting developers in achieving low-code development and reducing the amount of code editing.

[0071] After the developer completes the low-code development, the low-code development plug-in will convert the configuration generated by the low-code development operation (including the previous visual editing operation) into project code based on its core functions, and integrate the code into the project to be developed to obtain the completed project. The generated project code can be used directly in the project without additional conversion or configuration.

[0072] In this embodiment, the visual editing interface enables developers to intuitively perform component dragging, property configuration, and page layout operations, which simplifies the development process and reduces the difficulty of development; the low-code development plug-in can directly load and use the resources corresponding to the visual editing operations, assist in low-code development, automatically generate project code and integrate it into the project to be developed, improve the quality and consistency of the code, reduce manual coding, and improve development efficiency.

[0073] Furthermore, after the above step S204, it may also include: after obtaining the completed project, removing the low-code development plug-in from the project, and performing operation verification on the project after removal.

[0074] Specifically, after the development is completed, the low-code development platform can be removed from the project, and all codes related to the low-code development plug-in can be removed from the project, including the registration code in the entry file and any components or configurations that use the low-code development plug-in, to reduce the size and dependencies of the project. After the removal, the project is fully tested and verified to ensure that the project can still run normally after the plug-in is removed.

[0075] In this embodiment, after development is completed, the low-code development plug-in is removed from the project to reduce the project size, and the project is run verified after removal to ensure that the project can run normally.

[0076] In this embodiment, a plug-in package of the low-code development platform is obtained, and a project configuration file of the project to be developed is obtained, and the project configuration file records the resources required for the project to be developed; the low-code development platform is used as an auxiliary tool and does not have built-in basic components; the plug-in package is registered to the project to be developed according to the project configuration file to obtain a low-code development plug-in, and the low-code platform dynamically loads the required resources by reading the project configuration file of the project to be developed, thereby avoiding the problem of the low-code development platform's dependence on specific component libraries, being able to use the component libraries and custom resources of the project to be developed itself, and being flexibly applied to different development environments; low-code development is performed on the project to be developed through the low-code development plug-in, which greatly improves the flexibility and compatibility of low-code development.

[0077] It should be emphasized that in order to further ensure the privacy and security of the above-mentioned plug-in package, the above-mentioned plug-in package can also be stored in a node of a blockchain.

[0078] The blockchain referred to in this application is a new application model of computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanism, encryption algorithm, etc. Blockchain is essentially a decentralized database, a string of data blocks generated by cryptographic methods. Each data block contains a batch of network transaction information, which is used to verify the validity of its information (anti-counterfeiting) and generate the next block. Blockchain can include the underlying blockchain platform, platform product service layer, and application service layer.

[0079] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through computer-readable instructions, and the computer-readable instructions can be stored in a computer-readable storage medium. When the program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, the aforementioned storage medium can be a non-volatile storage medium such as a disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

[0080] It should be understood that, although the steps in the flowchart of the accompanying drawings are displayed in sequence as indicated by the arrows, these steps are not necessarily executed in sequence in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least a part of the steps in the flowchart of the accompanying drawings may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily executed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be executed in turn or alternately with other steps or at least a part of the sub-steps or stages of other steps.

[0081] Further references Figure 3 , as a response to the above Figure 2 The present application provides an embodiment of a low-code development device, and the device embodiment is similar to Figure 2 Corresponding to the method embodiment shown, the device can be specifically applied to various electronic devices.

[0082] like Figure 3 As shown, the low-code development device 300 described in this embodiment includes: a plug-in package acquisition module 301, a configuration acquisition module 302, a plug-in registration module 303 and a project development module 304, wherein:

[0083] The plug-in package acquisition module 301 is used to obtain the plug-in package of the low-code development platform.

[0084] The configuration acquisition module 302 is used to acquire a project configuration file of the project to be developed. The project configuration file records the resources required by the project to be developed.

[0085] The plug-in registration module 303 is used to register the plug-in package to the project to be developed according to the project configuration file to obtain a low-code development plug-in.

[0086] The project development module 304 is used to perform low-code development on the development project through a low-code development plug-in.

[0087] In this embodiment, a plug-in package of the low-code development platform is obtained, and a project configuration file of the project to be developed is obtained, and the project configuration file records the resources required for the project to be developed; the low-code development platform is used as an auxiliary tool and does not have built-in basic components; the plug-in package is registered to the project to be developed according to the project configuration file to obtain a low-code development plug-in, and the low-code platform dynamically loads the required resources by reading the project configuration file of the project to be developed, thereby avoiding the problem of the low-code development platform's dependence on specific component libraries, being able to use the component libraries and custom resources of the project to be developed itself, and being flexibly applied to different development environments; low-code development is performed on the project to be developed through the low-code development plug-in, which greatly improves the flexibility and compatibility of low-code development.

[0088] In some optional implementations of this embodiment, the low-code development device 300 may further include: a platform packaging module and a file uploading module, wherein:

[0089] The platform packaging module is used to package the low-code platform and generate NPM package files.

[0090] The file upload module is used to publish NPM package files as plug-in packages to NPM for download by various projects to be developed.

[0091] In this embodiment, the low-code platform is packaged to generate an NPM package file; the NPM package file is published to NPM as a plug-in package for download by each project to be developed, making the distribution and use of the low-code development platform more convenient and standardized. Developers can add the plug-in package of the low-code development platform to the project through NPM, which simplifies the management and use of the plug-in package; through the version management function of the NPM warehouse, the low-code development platform can be easily updated and maintained to ensure that the plug-in package is always the latest version, reducing version compatibility issues.

[0092] In some optional implementations of this embodiment, the low-code development device 300 may further include: a file acquisition module, a function acquisition module, and a plug-in processing module, wherein:

[0093] The file acquisition module is used to obtain the plug-in generation configuration file of the low-code development platform.

[0094] The function acquisition module is used to extract the function type recorded in the plug-in generation configuration file and obtain the function code corresponding to the function type.

[0095] The plug-in processing module is used to perform plug-in processing on the acquired function code to obtain a plug-in package for the low-code development platform.

[0096] In this embodiment, the corresponding function code is obtained according to the function type pre-selected by the developer in the plug-in generation configuration file; the function code is plug-in-processed to obtain a plug-in package for the low-code development platform, thereby realizing flexible selection and combination of the core functions of the low-code development platform according to project requirements, improving the reusability, flexibility and adaptability of the plug-in package, and avoiding the waste of resources caused by unnecessary functions.

[0097] In some optional implementations of this embodiment, the low-code development device 300 may further include: a resource determination module, a path acquisition module, and a configuration generation module, wherein:

[0098] The resource determination module is used to determine the resources required for the project to be developed. The resources include component libraries, custom components, public methods, and page templates.

[0099] The path acquisition module is used to obtain the resource paths of various resources.

[0100] The configuration generation module is used to generate a path file according to the resource paths of various resources, and to generate a project configuration file for the project to be developed according to the path file.

[0101] In this embodiment, the component library, custom components, public methods, page templates, etc. required for the project to be developed are determined; the resource paths of these resources are obtained and a path file is generated, and a project configuration file for the project to be developed is generated based on the path file, thereby ensuring that the required resources can be correctly identified and loaded in the future, improving maintainability and scalability, solving the shortcomings of existing low-code development platforms in resource loading and management, and enhancing the flexibility of low-code development.

[0102] In some optional implementations of this embodiment, the plug-in registration module 303 may include: a plug-in package adding submodule, a configuration parsing submodule, a method exposing submodule and a plug-in package registering submodule, wherein:

[0103] The plugin package adds a submodule, which is used to add the plugin package to the project to be developed.

[0104] The configuration parsing submodule is used to parse the project configuration file to obtain the project configuration parameters.

[0105] The method exposure submodule is used to expose the entry method of the plug-in package.

[0106] The plug-in package registration sub-module is used to register the plug-in package to the project instance in the project to be developed through the entry method, and pass in the project configuration parameters during the registration process to obtain the low-code development plug-in. The project configuration parameters instruct the low-code development plug-in to obtain the resources required for the project to be developed. The resources include component libraries, custom components, public methods and page templates.

[0107] In this embodiment, the project configuration file is parsed to obtain the project configuration parameters; the plug-in package is registered to the project instance in the project to be developed through the entry method of the plug-in package, and the project configuration parameters are passed in to ensure that the low-code development plug-in can correctly load and use the resources required for the project to be developed, including component libraries, custom components, public methods and page templates, which simplifies the registration and initialization process of the plug-in package and improves development efficiency.

[0108] In some optional implementations of this embodiment, the project development module 304 may include: an interface display submodule, a resource loading submodule, and a code generation submodule, wherein:

[0109] The interface display submodule is used to display the visual editing interface of the low-code development plug-in through the terminal and obtain the visual editing operations triggered in the visual editing interface.

[0110] The resource loading submodule is used to load the resources corresponding to the visual editing operations through the low-code development plug-in, and perform low-code development based on the resources.

[0111] The code generation sub-module is used to generate project code through the low-code development plug-in after completing the low-code development, and integrate the project code into the project to be developed to obtain a completed project.

[0112] In this embodiment, the visual editing interface enables developers to intuitively perform component dragging, property configuration, and page layout operations, which simplifies the development process and reduces the difficulty of development; the low-code development plug-in can directly load and use the resources corresponding to the visual editing operations, assist in low-code development, automatically generate project code and integrate it into the project to be developed, improve the quality and consistency of the code, reduce manual coding, and improve development efficiency.

[0113] In some optional implementations of this embodiment, the low-code development device 300 may also include: a removal module, which is used to remove the low-code development plug-in from the project after the development is completed, and perform operation verification on the project after removal.

[0114] In this embodiment, after development is completed, the low-code development plug-in is removed from the project to reduce the project size, and the project is run verified after removal to ensure that the project can run normally.

[0115] To solve the above technical problems, the present application also provides a computer device. Figure 4 , Figure 4 This is a basic structural block diagram of the computer device in this embodiment.

[0116] The computer device 4 includes a memory 41, a processor 42, and a network interface 43 that are interconnected through a system bus. It should be noted that the figure only shows a computer device 4 with components 41-43, but it should be understood that it is not required to implement all the components shown, and more or fewer components can be implemented instead. Among them, those skilled in the art can understand that the computer device here is a device that can automatically perform numerical calculations and / or information processing according to pre-set or stored instructions, and its hardware includes but is not limited to microprocessors, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), digital processors (DSPs), embedded devices, etc.

[0117] The computer device may be a computing device such as a desktop computer, a notebook, a PDA, a cloud server, etc. The computer device may interact with a user through a keyboard, a mouse, a remote controller, a touch pad, or a voice control device.

[0118] The memory 41 includes at least one type of readable storage medium, and the readable storage medium includes flash memory, hard disk, multimedia card, card-type memory (for example, SD or DX memory, etc.), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, disk, optical disk, etc. In some embodiments, the memory 41 can be an internal storage unit of the computer device 4, such as a hard disk or memory of the computer device 4. In other embodiments, the memory 41 can also be an external storage device of the computer device 4, such as a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (FlashCard), etc. equipped on the computer device 4. Of course, the memory 41 can also include both the internal storage unit of the computer device 4 and its external storage device. In this embodiment, the memory 41 is generally used to store the operating system and various application software installed on the computer device 4, such as computer-readable instructions of the low-code development method, etc. In addition, the memory 41 can also be used to temporarily store various types of data that have been output or are to be output.

[0119] The processor 42 may be a central processing unit (CPU), a controller, a microcontroller, a microprocessor, or other data processing chip in some embodiments. The processor 42 is generally used to control the overall operation of the computer device 4. In this embodiment, the processor 42 is used to run computer-readable instructions stored in the memory 41 or process data, such as computer-readable instructions for running the low-code development method.

[0120] The network interface 43 may include a wireless network interface or a wired network interface. The network interface 43 is generally used to establish a communication connection between the computer device 4 and other electronic devices.

[0121] The computer device provided in this embodiment can execute the above-mentioned low-code development method. Here, the low-code development method can be the low-code development method of each of the above-mentioned embodiments.

[0122] In this embodiment, a plug-in package of the low-code development platform is obtained, and a project configuration file of the project to be developed is obtained, and the project configuration file records the resources required for the project to be developed; the low-code development platform is used as an auxiliary tool and does not have built-in basic components; the plug-in package is registered to the project to be developed according to the project configuration file to obtain a low-code development plug-in, and the low-code platform dynamically loads the required resources by reading the project configuration file of the project to be developed, thereby avoiding the problem of the low-code development platform's dependence on specific component libraries, being able to use the component libraries and custom resources of the project to be developed itself, and being flexibly applied to different development environments; low-code development is performed on the project to be developed through the low-code development plug-in, which greatly improves the flexibility and compatibility of low-code development.

[0123] The present application also provides another embodiment, namely, providing a computer-readable storage medium, which stores computer-readable instructions, and the computer-readable instructions can be executed by at least one processor to enable the at least one processor to perform the steps of the low-code development method as described above.

[0124] In this embodiment, a plug-in package of the low-code development platform is obtained, and a project configuration file of the project to be developed is obtained, and the project configuration file records the resources required for the project to be developed; the low-code development platform is used as an auxiliary tool and does not have built-in basic components; the plug-in package is registered to the project to be developed according to the project configuration file to obtain a low-code development plug-in, and the low-code platform dynamically loads the required resources by reading the project configuration file of the project to be developed, thereby avoiding the problem of the low-code development platform's dependence on specific component libraries, being able to use the component libraries and custom resources of the project to be developed itself, and being flexibly applied to different development environments; low-code development is performed on the project to be developed through the low-code development plug-in, which greatly improves the flexibility and compatibility of low-code development.

[0125] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for a terminal device (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in each embodiment of the present application.

[0126] Obviously, the embodiments described above are only some embodiments of the present application, rather than all embodiments. The preferred embodiments of the present application are given in the accompanying drawings, but they do not limit the patent scope of the present application. The present application can be implemented in many different forms. On the contrary, the purpose of providing these embodiments is to make the understanding of the disclosure of the present application more thorough and comprehensive. Although the present application is described in detail with reference to the aforementioned embodiments, for those skilled in the art, it is still possible to modify the technical solutions recorded in the aforementioned specific implementation methods, or to perform equivalent replacement of some of the technical features therein. Any equivalent structure made using the contents of the specification and drawings of this application, directly or indirectly used in other related technical fields, is similarly within the scope of patent protection of this application.

Claims

1. A low-code development method, characterized in that: The steps include: Get the plugin package for the low-code development platform; Obtaining a project configuration file of a project to be developed, wherein the project configuration file records resources required by the project to be developed; Registering the plug-in package to the project to be developed according to the project configuration file to obtain a low-code development plug-in; The low-code development plug-in is used to perform low-code development on the project to be developed.

2. The low-code development method according to claim 1, characterized in that: Before the step of obtaining the plug-in package of the low-code development platform, it also includes: Package the low-code platform and generate NPM package files; The NPM package file is published as a plug-in package to NPM for download by each project to be developed.

3. The low-code development method according to claim 1, characterized in that: Before the step of obtaining the plug-in package of the low-code development platform, it also includes: Obtain the plugin generation configuration file for the low-code development platform; Extract the function type recorded in the plug-in generation configuration file, and obtain the function code corresponding to the function type; The acquired function code is processed into a plug-in to obtain a plug-in package for the low-code development platform.

4. The low-code development method according to claim 1, characterized in that: Before the step of obtaining the project configuration file of the project to be developed, the method further includes: Determine the resources required for the project to be developed, including component libraries, custom components, public methods, and page templates; Get the resource paths of various resources; A path file is generated according to the resource paths of the various resources, and a project configuration file of the project to be developed is generated according to the path file.

5. The low-code development method according to claim 1, characterized in that: The step of registering the plug-in package to the project to be developed according to the project configuration file to obtain the low-code development plug-in includes: Adding the plug-in package to the project to be developed; Parsing the project configuration file to obtain project configuration parameters; Expose the entry method of the plug-in package; The plug-in package is registered to the project instance in the project to be developed through the entry method, and the project configuration parameters are passed in during the registration process to obtain a low-code development plug-in. The project configuration parameters instruct the low-code development plug-in to obtain the resources required for the project to be developed, and the resources include component libraries, custom components, public methods and page templates.

6. The low-code development method according to claim 5, characterized in that: The step of performing low-code development on the project to be developed by using the low-code development plug-in includes: Displaying a visual editing interface of the low-code development plug-in through a terminal, and obtaining a visual editing operation triggered in the visual editing interface; Loading resources corresponding to the visual editing operation through the low-code development plug-in, and performing low-code development based on the resources; After the low-code development is completed, the project code is generated through the low-code development plug-in, and the project code is integrated into the project to be developed to obtain a completed project.

7. The low-code development method according to claim 1, characterized in that: After the step of performing low-code development on the project to be developed by using the low-code development plug-in, the step further includes: After obtaining the completed project, the low-code development plug-in is removed from the project, and the project is run and verified after removal.

8. A low-code development device, characterized in that: include: The plug-in package acquisition module is used to obtain the plug-in package of the low-code development platform; A configuration acquisition module is used to acquire a project configuration file of a project to be developed, wherein the project configuration file records resources required by the project to be developed; A plug-in registration module, used to register the plug-in package to the project to be developed according to the project configuration file to obtain a low-code development plug-in; A project development module is used to perform low-code development on the project to be developed through the low-code development plug-in.

9. A computer device comprising a memory and a processor, wherein the memory stores computer-readable instructions, and the processor implements the steps of the low-code development method as described in any one of claims 1 to 7 when executing the computer-readable instructions.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-readable instructions, which, when executed by a processor, implement the steps of the low-code development method as described in any one of claims 1 to 7.

Images