CN118227105A

CN118227105A - Component management method and device for low-code platform

Info

Publication number: CN118227105A
Application number: CN202410198511.2A
Authority: CN
Inventors: 闫斌
Original assignee: Qingdao Haier Technology Co Ltd; Haier Smart Home Co Ltd; Haier Uplus Intelligent Technology Beijing Co Ltd
Current assignee: Qingdao Haier Technology Co Ltd; Haier Smart Home Co Ltd; Haier Uplus Intelligent Technology Beijing Co Ltd
Priority date: 2024-02-22
Filing date: 2024-02-22
Publication date: 2024-06-21

Abstract

The application discloses a component management method and device of a low-code platform, which relate to the technical field of intelligent home/intelligent families and are applied to a server, wherein the method comprises the following steps: receiving a target request sent by a low-code platform and used for acquiring a target component; inquiring a storage path corresponding to the latest version of the target component based on the target request; and determining the component file of the target component based on the storage path, and sending the component file of the target component to the low-code platform so that the low-code platform renders the target component based on the component file of the target component. According to the method provided by the application, the storage path corresponding to the latest version of the target component is queried, so that the low-code platform renders the target component based on the component files of the latest version of the target component, and as the component files corresponding to each target component are independently existing, independent upgrading of the target component can be realized, and the research and development cost is reduced.

Description

Component management method and device for low-code platform

Technical Field

The present application relates to the field of software development technologies, and in particular, to a method and an apparatus for managing components of a low code platform.

Background

The low-code development is a development form gradually optimized and evolved on the basis of traditional software development, provides a lower application building threshold, not only can enable non-professional technicians to build an application platform after simple learning, but also is high in development speed.

An existing low-code component library is an overall project that contains multiple components. When new functions need to be added, errors repaired, or existing functions improved, the entire project engineering needs to be released and updated. This is because the individual components in the component library may depend on each other and need to be updated simultaneously to ensure the stability and correctness of the overall system. Therefore, each time a function iteration or bug repair is performed, the entire project engineering needs to be issued and updated to ensure that all components can work cooperatively and provide the user with the best use experience, which results in low efficiency and high development cost.

How to develop based on the independent components of the latest version, and reducing the research and development cost are technical problems to be solved at present.

Disclosure of Invention

The application provides a component management method and device of a low-code platform, which are used for solving the defects in the prior art.

The application provides a component management method of a low-code platform, which is applied to a server and comprises the following steps:

receiving a target request sent by a low-code platform and used for acquiring a target component;

Inquiring a storage path corresponding to the latest version of the target component based on the target request;

and determining the component file of the target component based on the storage path, and sending the component file of the target component to the low-code platform so that the low-code platform renders the target component based on the component file of the target component.

According to the component management method of the low-code platform provided by the application, the component file of the target component is determined based on the storage path, and the component file of the target component is sent to the low-code platform, and the method comprises the following steps:

Receiving a script tag sent by the low-code platform; the script tag is created by the low-code platform based on a storage path corresponding to the latest version of the target component returned by the server;

and determining the component file of the target component based on the script tag, and sending the component file of the target component to the low-code platform.

According to the component management method of the low-code platform, before receiving the target request for acquiring the target component sent by the low-code platform, the method further comprises the following steps:

Receiving a network request sent by a low-code platform and used for acquiring a component menu list; wherein the component menu list includes a plurality of components;

And sending the component menu list to the low code platform based on the network request.

Acquiring a to-be-processed component and a configuration file and an entry file corresponding to the to-be-processed component;

and constructing the component to be processed into an independent component file by constructing a script based on the entry file.

According to the component management method of the low-code platform provided by the application, after the component to be processed is constructed into the independent component file by constructing a script based on the entry file, the method further comprises the following steps:

Analyzing the configuration file corresponding to the component to be processed to obtain the component name and the component version information;

creating a component catalog corresponding to the component to be processed based on the component name and the component version information;

And storing the independent component files into component catalogs corresponding to the components to be processed through a network interface to generate components and corresponding component information.

According to the component management method of the low-code platform provided by the application, after the independent component file is stored into the component catalog corresponding to the component to be processed through the network interface to generate the component and the corresponding component information, the method further comprises the following steps:

And storing the components and the corresponding component information into a database.

According to the component management method of the low-code platform provided by the application, after the components and the corresponding component information are stored in the database, the method further comprises the following steps:

Under the condition that the component version information corresponding to the component is updated, acquiring the component version information of the latest version;

and updating the component information of the components in the database based on the latest version of the component version information.

The application also provides a component management device of the low-code platform, which is applied to a server and comprises:

The receiving module is used for receiving a target request sent by the low-code platform and used for acquiring a target component;

the query module is used for querying a storage path corresponding to the latest version of the target component based on the target request;

and the sending module is used for determining the component file of the target component based on the storage path and sending the component file of the target component to the low-code platform so that the low-code platform renders the target component based on the component file of the target component.

The application also provides an electronic device comprising a memory in which a computer program is stored and a processor arranged to implement a component management method of a low code platform as any one of the above by execution of the computer program.

The present application also provides a computer-readable storage medium including a stored program, wherein the program when run performs a component management method implementing any one of the low-code platforms described above.

The application also provides a computer program product comprising a computer program which when executed by a processor implements a component management method of a low code platform as described in any one of the above.

The application provides a component management method and device of a low-code platform, which are applied to a server, and are used for inquiring a storage path corresponding to the latest version of a target component based on a target request by receiving the target request sent by the low-code platform and used for acquiring the target component, determining a component file of the target component based on the storage path, and sending the component file of the target component to the low-code platform so that the low-code platform renders the target component based on the component file of the target component. Therefore, the application can make the low code platform render the target assembly based on the assembly files of the latest version of the target assembly by inquiring the storage path corresponding to the latest version of the target assembly.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application.

In order to more clearly illustrate the embodiments of the application or the technical solutions of the prior art, the drawings which are used in the description of the embodiments or the prior art will be briefly described, and it will be obvious to a person skilled in the art that other drawings can be obtained from these drawings without inventive effort.

FIG. 1 is a schematic diagram of a hardware environment for a component management method of a low code platform according to an embodiment of the present application;

FIG. 2 is a flow chart of a method for managing components of a low-code platform according to the present application;

FIG. 3 is a schematic diagram of component rendering in a component management method of a low code platform provided by the present application;

FIG. 4 is a schematic flow chart of generating common components provided by the present application;

FIG. 5 is a second flowchart of a method for managing components of a low-code platform according to the present application;

FIG. 6 is a complete flow chart of a method of component management for a low code platform provided by the present application;

FIG. 7 is a schematic diagram of a component management apparatus of a low code platform according to the present application;

fig. 8 is a schematic structural diagram of an electronic device provided by the present application.

Detailed Description

In order that those skilled in the art will better understand the present application, a technical solution in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in which it is apparent that the described embodiments are only some embodiments of the present application, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the present application without making any inventive effort, shall fall within the scope of the present application.

It should be noted that the terms "first," "second," and the like in the description and the claims of the present application and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the application described herein may be implemented in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

According to one aspect of the embodiment of the application, a component management method of a low-code platform is provided. The component management method of the low-code platform is widely applied to full-house intelligent digital control application scenes such as intelligent Home (Smart Home), intelligent Home equipment ecology, intelligent Home (INTELLIGENCE HOUSE) ecology and the like. Alternatively, in the present embodiment, the component management method of the low-code platform described above may be applied to a hardware environment constituted by the terminal device 102 and the server 104 as shown in fig. 1. As shown in fig. 1, the server 104 is connected to the terminal device 102 through a network, and may be used to provide services (such as application services and the like) for a terminal or a client installed on the terminal, a database may be set on the server or independent of the server, for providing data storage services for the server 104, and cloud computing and/or edge computing services may be configured on the server or independent of the server, for providing data computing services for the server 104.

The network may include, but is not limited to, at least one of: wired network, wireless network. The wired network may include, but is not limited to, at least one of: a wide area network, a metropolitan area network, a local area network, and the wireless network may include, but is not limited to, at least one of: WIFI (WIRELESS FIDELITY ), bluetooth. The terminal device 102 may not be limited to a PC, a mobile phone, a tablet computer, an intelligent air conditioner, an intelligent smoke machine, an intelligent refrigerator, an intelligent oven, an intelligent cooking range, an intelligent washing machine, an intelligent water heater, an intelligent washing device, an intelligent dish washer, an intelligent projection device, an intelligent television, an intelligent clothes hanger, an intelligent curtain, an intelligent video, an intelligent socket, an intelligent sound box, an intelligent fresh air device, an intelligent kitchen and toilet device, an intelligent bathroom device, an intelligent sweeping robot, an intelligent window cleaning robot, an intelligent mopping robot, an intelligent air purifying device, an intelligent steam box, an intelligent microwave oven, an intelligent kitchen appliance, an intelligent purifier, an intelligent water dispenser, an intelligent door lock, and the like.

The following describes a component management method and apparatus of a low code platform according to the present application in conjunction with fig. 2-8.

It should be noted that low-code development is a development form gradually optimized and evolved on the basis of traditional software development, which provides a lower application building threshold, so that non-professional technicians can build an application platform after simple learning, and the development speed is high.

An existing low-code component library is an overall project that contains multiple components. When new functions need to be added, errors repaired, or existing functions improved, the entire project engineering needs to be released and updated. This is because the individual components in the component library may depend on each other and need to be updated simultaneously to ensure the stability and correctness of the overall system. Therefore, each time a function iteration or bug repair is performed, the entire project engineering needs to be issued and updated to ensure that all components can work cooperatively and provide the user with the best use experience, which results in low efficiency and high development cost. Based on the above, the present application provides a component management method for a low-code platform, which is used for solving the above-mentioned problems.

Fig. 2 is a flow chart of a component management method of a low-code platform provided by the present application, and as shown in fig. 2, the component management method of a low-code platform provided by the present application is applied to a server, and the method includes:

Step 100, receiving a target request sent by a low code platform for acquiring a target component.

It should be noted that the Low code platform (Low-Code Development Platform) is an application development platform, which allows an developer to create an application program with less coding effort through a graphical interface and a visual modeling manner. Low code platforms typically provide a set of pre-built components and modules, and a visual design environment, which a developer can quickly build applications by dragging and configuring. The application field of the low-code platform is very wide, including enterprise-level applications, mobile applications, web applications, internet of things applications, and the like. Some well known low code platforms include OutSystems, mendix, appian, microsoft Power Apps, and the like.

An existing Component (Component) refers in software development to a unit of software that can be reused, has a specific function, and can be combined with other components to create an application. Components are typically designed as stand-alone, reusable code modules, with clear interfaces and functions, which can be used by different applications or systems. The components may be Graphical User Interface (GUI) controls, data processing modules, algorithm implementations, web services, and the like. By using components, developers can build applications more efficiently because they can create new applications with existing components without having to write code from scratch. Development time and cost can be reduced, and quality and maintainability of code can be improved.

It should be noted that, the components in this embodiment are preconfigured, and may be independently upgraded.

Specifically, when a user develops a detail page, for example, an http request is first sent to a server through a low-code platform to obtain component menu data, where the component menu data includes a plurality of components of different types and component information available for each component, such as a component name, a version number, a path, and the like, and these data are generally transmitted in JSON format and are parsed and processed at a front end.

Further, after the component menu data is obtained, the low code platform renders the data into a list of component menus for user selection. The user may select a desired component from this list and drag it to a designated location on the canvas. This process is typically implemented through the drag and drop APIs of JavaScript and HTML 5.

In one embodiment, the components in the component menu list may be arranged in categories, e.g., categories may be categorized into general components, logistic components, manufacturing components, legal components, research and development components, quality components, etc.; each category contains several specific components, for example, general components may include: some specific components of the to-do center, the work schedule, the personal information and the like. Based on specific classification, detail page development users can quickly locate the components required by the users, and development efficiency is improved. The present embodiment is not limited in any way to the specific classification in the component menu list.

Step 200, based on the target request, inquiring a storage path corresponding to the latest version of the target component.

Specifically, when the user drags the target component onto the canvas, the low code platform downloads the component file of the component from the server by remote access, also typically by http request, based on the stored path of the path field of the target component.

The code for remotely accessing the component files according to the storage path is as follows:

<component

:is＝"currNode"

:class＝"element-on-edit-pane n

v-bind＝"{...info.propsValue,...projectData.globalprops[info.elNam]}

:element＝"info"

:uuid＝"info.uuid

:isIos＝"isIOs()"

:IsConnect＝"IsConnect"

/>

</div>

</template>

And 300, determining a component file of the target component based on the storage path, and sending the component file of the target component to the low-code platform so that the low-code platform renders the target component based on the component file of the target component.

Specifically, to load a remote component file, the low code platform dynamically creates a script tag and sets the src attribute of the tag to the URL of the component file. Thus, when the browser parses the script tag, the component's file, i.e., the dynamic script loading process, is automatically downloaded and loaded. In this process, the component name and version number are spliced into a component unique component new name, such as: component new name EnumButton@1.0.5, where "EnumButton" is the component name and "1.0.5" is the version number.

FIG. 3 is a schematic diagram of component rendering in the component management method of the low-code platform provided by the present application, where, as shown in FIG. 3, after a component file is loaded, the low-code platform dynamically registers the component as a global component of Vue. Thus, this component can be used throughout the Vue application. Then, the target component is rendered onto the canvas in accordance with the user's configuration parameters, common methods, and the like, in conjunction with rendering logic. In this way, the user can see and interact with the selected component in the application.

FIG. 4 is a schematic flow chart of generating a public component, as shown in FIG. 4, the target component is integrated into a low code platform, and is still private, and can be used only by itself, but not by other users, and can be a public component after release, test and audit.

The above is a description of the steps of the component management method of the low code platform provided by the application. As can be seen from the description of the above steps, according to the component management method of the low-code platform provided by the present application, the component management method is applied to a server, and the low-code platform renders a target component based on the component file of the target component by receiving a target request sent by the low-code platform and used for obtaining the target component, querying a storage path corresponding to the latest version of the target component based on the target request, determining the component file of the target component based on the storage path, and sending the component file of the target component to the low-code platform. Therefore, the application can make the low code platform render the target assembly based on the assembly files of the latest version of the target assembly by inquiring the storage path corresponding to the latest version of the target assembly.

Based on the above embodiment, in this embodiment, step 300 determines the component file of the target component based on the storage path, and sends the component file of the target component to the low code platform, including:

According to the component management method of the low-code platform, the storage path corresponding to the latest version of the target component is queried, so that the low-code platform renders the target component based on the component files of the latest version of the target component, and as the component files corresponding to each target component are independently existing, independent upgrading of the target component can be realized, and the research and development cost is reduced.

Based on the above embodiment, in this embodiment, before receiving the target request for acquiring the target component sent by the low code platform in step 100, the method further includes:

According to the component management method of the low-code platform, before the target component is selected, the component menu category is requested to be acquired, and diversified selection of the component is achieved.

It should be noted that the component to be processed may be, for example, a common vue component.

Specifically, the component development catalog mainly includes two files of vue components: one is a configuration file config.json, which contains basic information of the component, such as component name (name), component version information (version), and component function description (desc). This information will be used in the subsequent build and integration process. Specific contents of the configuration file may include:

{

name: "testCom"// component name

Version: "1.0.0",// component version information

Desc: "test component",// component function description

}

The other is the component file src directory and the entry file index. Vue: this directory contains the source code of the component, while index. The specific content of the entry file may include:

</div>

</template>

export default{

name:'Empty

}

</script>

</style>

Further, the component to be processed is constructed into a separate index. Js file by constructing a script, and this step is mainly to compile and package the source code (in the src directory) of the component into a separate JavaScript file (index. Js). This process includes the steps of code compression, optimization, etc.

According to the component management method of the low-code platform, by configuring vue components, as the component files corresponding to each target component are independent, independent upgrading of the target components can be realized, and the research and development cost is reduced.

Based on the above embodiment, in this embodiment, fig. 5 is a second flowchart of a component management method of a low code platform provided by the present application, as shown in fig. 5, after the component to be processed is built into an independent component file by a building script based on the entry file, the method further includes:

and 510, analyzing the configuration file corresponding to the component to be processed to obtain the component name and the component version information.

And step 520, creating a component catalog corresponding to the component to be processed based on the component name and the component version information.

And 530, storing the independent component file into a component catalog corresponding to the component to be processed through a network interface so as to generate a component and corresponding component information.

Specifically, after the components to be processed are built as independent component files by the build script, the information in the configuration file is parsed, and an OSS (object storage service) of the alicloud is used to store and manage the component files, which is generated on the OSS component pool according to name and version fields. And creating a corresponding directory on the OSS component pool to store the component files according to the name and version fields in the configuration file.

Further, the constructed index. Js is uploaded to a directory previously created on the OSS through an http interface.

Further, the components and component information (e.g., component name, component version information, module name, etc.) are stored in a database for subsequent use. For example, vue components and the following component information are stored in a database:

{

elName:’EnumButton’,

version:’1.0.5’,

mouduleLibName an 'enumeration button',

parth:”https://resource.com/componentLibrary/EnumButton@1.0.5/index.js”

}

Based on the above embodiment, in this embodiment, after storing the component and the corresponding component information in the database, the method further includes:

In particular, if the component version information of a certain component is known to have been updated, this updated component version information needs to be obtained, typically by checking the component's version control library (e.g., git) or by querying the component's maintainer.

Further, when the latest version of the component version information is acquired, the component information needs to be updated in the database.

The component management method of the low-code platform can ensure the convenience of component maintenance by timely acquiring and updating the version information of the components, and can realize independent upgrading of the target components and reduce the research and development cost because the component files corresponding to each target component are independently existed.

Fig. 6 is a complete flowchart of a component management method of a low code platform provided by the present application, and as shown in fig. 6, the component management method of a low code platform provided by the present application is described:

1. the method comprises the steps that a component developer obtains a to-be-processed component and a configuration file and an inlet file corresponding to the to-be-processed component;

2. The method comprises the steps that a component developer builds a component to be processed into an independent component file through a building script based on an entry file;

3. The method comprises the steps that a component developer analyzes a configuration file corresponding to a component to be processed, a component catalog corresponding to the component to be processed is created in an OSS component pool, and an index. Js file is stored in the component catalog corresponding to the component to be processed through a network interface so as to generate a component and corresponding component information; for example, component a, component B in the OSS component pool, component a containing multiple versions, component B also containing multiple versions;

4. The component developer stores the related information of the component (such as the name of the component, the version information of the component, the latest version in the OSS access path, etc.) into a menu database;

5. The detail page developer acquires the access path of the latest version of the target component from the database through the low-code platform, and ensures that the latest version of the target component is acquired.

It should be noted that dynamic expansion is supported in the OSS component pool, and when the components provided by the platform are not enough for all developers, the components can be developed by themselves, integrated into the platform for use and then shared for other users.

The component management method of the low-code platform provided by the application supports single upgrade of components, can select a repair history component (version number and history version number are kept consistent), can also select an unrepairable history component (version number accumulation), and packages a layer of rendering component when all components are applied, and is used for processing common logic and storing common states, such as state data of equipment, judging types and versions of applications, remotely loaded components, methods for registering components, instruction control methods, embedded point methods and the like.

The component management apparatus for a low code platform provided by the present application will be described below, and the component management apparatus for a low code platform described below and the component management method for a low code platform described above may be referred to correspondingly to each other.

Fig. 7 is a schematic structural diagram of a component management device of a low code platform provided by the present application, and as shown in fig. 7, the component management device of a low code platform provided by the present application is applied to a server, and the device includes:

a receiving module 701, configured to receive a target request sent by a low code platform for acquiring a target component;

a query module 702, configured to query a storage path corresponding to a latest version of the target component based on the target request;

And the sending module 703 is configured to determine a component file of the target component based on the storage path, and send the component file of the target component to the low-code platform, so that the low-code platform renders the target component based on the component file of the target component.

The component management device of the low-code platform is applied to a server, and is used for receiving a target request sent by the low-code platform and used for acquiring a target component, inquiring a storage path corresponding to the latest version of the target component based on the target request, determining a component file of the target component based on the storage path, and sending the component file of the target component to the low-code platform so that the low-code platform renders the target component based on the component file of the target component. Therefore, the application can make the low code platform render the target assembly based on the assembly files of the latest version of the target assembly by inquiring the storage path corresponding to the latest version of the target assembly.

Based on the above embodiment, in this embodiment, the sending module 703 is specifically configured to:

before receiving a target request for acquiring a target component sent by a low-code platform, receiving a network request for acquiring a component menu list sent by the low-code platform; wherein the component menu list includes a plurality of components;

Based on the foregoing embodiment, in this embodiment, the apparatus further includes a construction module, specifically configured to:

Before receiving a target request for acquiring a target component sent by a low-code platform, acquiring a component to be processed and a configuration file and an entry file corresponding to the component to be processed;

Based on the foregoing embodiment, in this embodiment, the apparatus further includes a generating module, specifically configured to:

After the to-be-processed component is constructed into an independent component file through a construction script based on the entry file, analyzing a configuration file corresponding to the to-be-processed component to obtain a component name and component version information;

Based on the foregoing embodiment, in this embodiment, the apparatus further includes a storage module, specifically configured to:

and after the independent component files are stored into the component catalogs corresponding to the components to be processed through a network interface to generate components and corresponding component information, storing the components and the corresponding component information into a database.

Based on the foregoing embodiment, in this embodiment, the apparatus further includes an update module, specifically configured to:

After the components and the corresponding component information are stored in a database, under the condition that the update of the component version information corresponding to the components is determined, the component version information of the latest version is acquired;

Fig. 8 illustrates a physical schematic diagram of an electronic device, as shown in fig. 8, which may include: processor 810, communication interface (Communications Interface) 820, memory 830, and communication bus 840, wherein processor 810, communication interface 820, memory 830 accomplish communication with each other through communication bus 840. The processor 810 may call logic instructions in the memory 830 to perform a component management method of a low code platform, applied to a server, the method comprising:

Further, the logic instructions in the memory 830 described above may be implemented in the form of software functional units and may be stored in a computer-readable storage medium when sold or used as a stand-alone product. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

In another aspect, the present application also provides a computer program product, where the computer program product includes a computer program, where the computer program can be stored on a computer readable storage medium, where the computer program when executed by a processor can perform a component management method of a low code platform provided by the above methods, and the method is applied to a server, and the method includes:

In still another aspect, the present application further provides a computer readable storage medium, where the computer readable storage medium includes a stored program, where the program executes a component management method of a low code platform provided by the above methods, and the method is applied to a server, and the method includes:

The apparatus embodiments described above are merely illustrative, wherein the elements illustrated as separate elements may or may not be physically separate, and the elements shown as elements may or may not be physical elements, may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment. Those of ordinary skill in the art will understand and implement the present invention without undue burden.

From the above description of the embodiments, it will be apparent to those skilled in the art that the embodiments may be implemented by means of software plus necessary general hardware platforms, or of course may be implemented by means of hardware. Based on this understanding, the foregoing technical solution may be embodied essentially or in a part contributing to the prior art in the form of a software product, which may be stored in a computer readable storage medium, such as ROM/RAM, a magnetic disk, an optical disk, etc., including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method described in the respective embodiments or some parts of the embodiments.

Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present application, and are not limiting; although the application has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

1. A component management method of a low code platform, applied to a server, the method comprising:

2. The component management method of the low-code platform according to claim 1, wherein the determining the component file of the target component based on the storage path and transmitting the component file of the target component to the low-code platform includes:

3. The component management method of a low code platform according to claim 1, wherein before receiving a target request sent by the low code platform for acquiring a target component, the method further comprises:

4. The component management method of a low code platform according to claim 1, wherein before receiving a target request sent by the low code platform for acquiring a target component, the method further comprises:

5. The component management method of a low code platform according to claim 4, wherein after the component to be processed is built as an independent component file by a build script based on the entry file, the method further comprises:

6. The component management method of a low code platform according to claim 5, wherein after storing the independent component file into a component directory corresponding to the component to be processed through a network interface to generate a component and corresponding component information, the method further comprises:

7. The component management method of a low code platform according to claim 6, wherein after storing the components and corresponding component information in a database, the method further comprises:

8. A component management apparatus of a low code platform, for application to a server, the apparatus comprising:

9. A computer-readable storage medium, characterized in that the computer-readable storage medium comprises a stored program, wherein the program when run performs the method of any one of claims 1 to 7.

10. An electronic device comprising a memory and a processor, characterized in that the memory has stored therein a computer program, the processor being arranged to execute the method according to any of claims 1 to 7 by means of the computer program.