CN115658032A - Component processing method and device, storage medium and electronic equipment - Google Patents
Component processing method and device, storage medium and electronic equipment Download PDFInfo
- Publication number
- CN115658032A CN115658032A CN202211293370.XA CN202211293370A CN115658032A CN 115658032 A CN115658032 A CN 115658032A CN 202211293370 A CN202211293370 A CN 202211293370A CN 115658032 A CN115658032 A CN 115658032A
- Authority
- CN
- China
- Prior art keywords
- component
- determining
- instruction
- information
- low
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Landscapes
- Stored Programmes (AREA)
Abstract
The invention provides a component processing method and device, a storage medium and an electronic device, wherein the method comprises the following steps: determining component variable data corresponding to the received component development instruction in the component global variables; generating a component based on the component variable data, packaging the component and then issuing the packaged component to a node package manager; when a component downloading instruction is received, acquiring a first component list of a node packet manager; acquiring a component selection instruction, wherein the component selection instruction comprises component selection information generated based on each component information in the first component list; and pulling the component corresponding to the component selection information from the node manager, and installing the component to the low-code platform. The component global variables of all the public component modules of the low-code platform are applied to develop the components, the developed components are released in the node packet manager, the corresponding components can be directly pulled from the node packet manager and installed in the low-code platform, all the codes of the low-code platform do not need to be pulled for development, and the development cost is reduced.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a component processing method and apparatus, a storage medium, and an electronic device.
Background
At present, when an application program is developed, a low-code platform is usually used for development, and the low-code platform is a development platform which can generate the application program rapidly through unordered coding or a small amount of codes. At present, most of mainstream low-code platforms directly integrate components in the low-code platforms, and operators can only build projects by using the existing components in the low-code platforms.
The subassembly in the low code platform is difficult for increasing, if need newly increase the subassembly in the platform, then need draw whole codes of low code platform and carry out component development, then pack the integration, release whole low code platform again, and whole process is comparatively loaded down with trivial details, need drop into higher cost.
Disclosure of Invention
In view of the above, the present invention provides a component processing method and apparatus, a storage medium, and an electronic device, where each common component module required for developing a component is mounted to a Window global variable, so as to obtain a component global variable, a component global variable development component is called, and the developed component is packaged and then issued in a node package manager, and a low-code platform can pull the component from the node package manager for installation, so that when a component is newly added to the low-code platform, all components of the low-code platform do not need to be pulled for development, and development cost is effectively reduced.
In order to achieve the purpose, the invention provides the following technical scheme:
a component handling method, comprising:
when an assembly development instruction is received, determining assembly variable data corresponding to the assembly development instruction in preset assembly global variables, wherein the assembly global variables are variables obtained by mounting all common assembly modules of a low-code platform to Window global variables;
generating a component corresponding to the component development instruction based on the component variable data, packaging the component, and issuing the packaged component to a preset node package manager;
when a component downloading instruction is received, acquiring a first component list of the node packet manager, wherein the first component list comprises component information of each component issued on the node packet manager;
acquiring a component selection instruction, wherein the component selection instruction comprises component selection information generated based on each component information in the first component list;
and pulling the component corresponding to the component selection information from the node manager, and installing the pulled component to the low-code platform.
Optionally, the determining component variable data corresponding to the component development instruction in the preset component global variables includes:
analyzing the component development instruction to obtain the names of all component modules in the component development instruction;
determining a common component module of each component module name, and determining each determined common component module as a target module;
and determining variable data of each target module in the component global variables, and determining the determined variable data as component variable data.
Optionally, the method for acquiring the component selection instruction includes:
displaying the information of each component in the first component list to developers through a preset display module;
and acquiring a component selection instruction input by the developer based on each component information.
Optionally, the method for pulling, from the node manager, the component corresponding to the component selection information includes:
acquiring a component name and a component version number in the component selection information;
determining each component with the same name as the component name in the node manager as a target component;
and determining the version number of each target component, and determining the target component with the version number consistent with the component version number as the component corresponding to the component selection information.
The above method, optionally, further includes:
sending a second component list of the low-code platform to a preset client, wherein the second component list comprises information of each component installed in the low-code platform;
acquiring a selection instruction fed back by the client based on the second component list;
and feeding back the script file of the component corresponding to the selection instruction to the client, so that the client builds a page by using the script file.
A component handling apparatus comprising:
the device comprises a determining unit and a processing unit, wherein the determining unit is used for determining component variable data corresponding to a component development instruction in preset component global variables when the component development instruction is received, and the component global variables are variables obtained by mounting all common component modules of a low-code platform to Window global variables;
the generating unit is used for generating a component corresponding to the component development instruction based on the component variable data, packaging the component and issuing the packaged component to a preset node packet manager;
a first obtaining unit, configured to obtain a first component list of the node packet manager when a component download instruction is received, where the first component list includes component information of each component issued on the node packet manager;
a second obtaining unit, configured to obtain a component selection instruction, where the component selection instruction includes component selection information generated based on each component information in the first component list;
and the installation unit is used for pulling the component corresponding to the component selection information from the node manager and installing the pulled component to the low-code platform.
The above apparatus, optionally, the determining unit includes:
the first obtaining subunit is used for analyzing the component development instruction to obtain the names of the component modules in the component development instruction;
the first determining subunit is used for determining a common component module of each component module name and determining each determined common component module as a target module;
and the second determining subunit is used for determining the variable data of each target module in the component global variables and determining the determined variable data as the component variable data.
The above apparatus, optionally, the second obtaining unit includes:
the display subunit is used for displaying the information of each component in the first component list to developers through a preset display module;
and the second acquisition subunit is used for acquiring a component selection instruction input by the developer based on each component information.
The above apparatus, optionally, the mounting unit includes:
a third acquiring subunit, configured to acquire a component name and a component version number in the component selection information;
a third determining subunit, configured to determine, as target components, components in the node manager that have the same name as the component name;
and the fourth determining subunit is used for determining the version number of each target component, and determining the target component of which the version number is consistent with the component version number as the component corresponding to the component selection information.
The above apparatus, optionally, further comprises:
a sending unit, configured to send a second component list of the low-code platform to a preset client, where the second component list includes information of each component installed in the low-code platform;
a third obtaining unit, configured to obtain a selection instruction fed back by the client based on the second component list;
and the feedback unit is used for feeding back the script file of the component corresponding to the selection instruction to the client side, so that the client side uses the script file to construct a page.
A storage medium comprising stored instructions, wherein the instructions, when executed, control a device on which the storage medium resides to perform a component handling method as described above.
An electronic device comprising a memory, and one or more instructions, wherein the one or more instructions are stored in the memory and configured to be executed by the one or more processors to perform the component processing method as described above.
Compared with the prior art, the invention has the following advantages:
the invention provides a component processing method and device, a storage medium and electronic equipment, wherein when a component development instruction is received, component variable data corresponding to the component development instruction is determined in preset component global variables, and the component global variables are variables obtained by mounting each common component module of a low-code platform to Window global variables; generating a component corresponding to the component development instruction based on the component variable data, packaging the component, and issuing the packaged component to a preset node packet manager; when a component downloading instruction is received, acquiring a first component list of a node packet manager, wherein the first component list comprises component information of each component issued on the node packet manager; acquiring a component selection instruction, wherein the component selection instruction comprises component selection information generated based on each component information in the first component list; and pulling the component corresponding to the component selection information from the node manager, and installing the pulled component to the low-code platform. The method comprises the steps of mounting all public component modules of a low-code platform to a Window global variable to obtain component variable data, calling data from the component variable data to develop in the component development process, releasing the developed components at a node packet manager, and directly pulling corresponding components from the node packet manager when new components need to be added to the low-code platform.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
FIG. 1 is a flowchart of a method for processing a component according to an embodiment of the present invention;
fig. 2 is an exemplary diagram for mounting each common component module to a Window global variable according to the embodiment of the present invention;
fig. 3 is a flowchart of a method for determining component variable data corresponding to a component development instruction in preset component global variables according to an embodiment of the present invention;
FIG. 4 is a diagram illustrating an exemplary process for packaging developed components according to an embodiment of the present invention;
fig. 5 is a flowchart of a method for pulling a component corresponding to component selection information from a node manager according to an embodiment of the present invention;
FIG. 6 is a diagram illustrating an exemplary processing flow of components according to an embodiment of the present invention;
FIG. 7 is a schematic structural diagram of a component handling apparatus according to an embodiment of the present invention;
fig. 8 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be obtained by a person skilled in the art without making any creative effort based on the embodiments in the present invention, belong to the protection scope of the present invention.
In this application, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrases "comprising a," "8230," "8230," or "comprising" does not exclude the presence of additional like elements in a process, method, article, or apparatus that comprises the element.
At present, most of mainstream low-code platforms directly integrate components in the platforms, and operators can only build projects by using the existing components in the platforms. If a new component needs to be supported, the development can be carried out only depending on the platform, and then the whole platform is released again, so that a large development cost is required to be invested when a new component is added in a low-code platform.
In order to solve the above problems, the present invention provides a component processing method and apparatus, a storage medium, and an electronic device, which do not need to pull the code of the entire low-code platform for development when adding a new component in the low-code platform, thereby effectively reducing the cost of adding a component in the low-code platform.
The invention is operational with numerous general purpose or special purpose computing device environments or configurations. For example: personal computers, server computers, hand-held or portable devices, tablet-type devices, multi-processor apparatus, distributed computing environments that include any of the above devices or equipment, and the like. The execution subject of the present invention may be a low code platform.
Referring to fig. 1, a flowchart of a method for processing a component according to an embodiment of the present invention is described in detail as follows.
S101, when an assembly development instruction is received, determining assembly variable data corresponding to the assembly development instruction in preset assembly global variables, wherein the assembly global variables are variables obtained after mounting each common assembly module of a low-code platform to a Window global variable.
When a developer needs to develop a new component, a component development instruction is sent to the low-code platform, and after the low-code platform receives the component development instruction, component variable data corresponding to the component development instruction is determined in the component global variables.
The component development command is used to develop a new component, and the component development command includes development information required to develop the new component, for example, the name of a module to be called.
It should be noted that, each common component module includes, but is not limited to, a base library, a base component, a common framework, and the like, which have been developed in a low-code platform; further, the base library contains classes and methods for low code platforms, such as Core tag libraries; the basic components comprise components such as texts, pictures, videos and the like, such as a Module component; common framework refers to the development framework used by the front end and may be determined by the technology stack, e.g., vue framework, react framework, etc.
Referring to fig. 2, an exemplary diagram for mounting each common component module to a Window global variable according to the embodiment of the present invention includes a low-code platform 201 where each common component module is not mounted to the Window global variable, and a low-code platform 202 where each common component module is mounted to the Window global variable. Each common component Module is not mounted in the low-code platform 201 of the Window global variable and comprises an undeployed basic library Croe, a common framework Vue and a basic component Module; the low-code platform 202 in which each common component Module has been mounted to the Window global variable contains a base library Croe mounted to the Window global variable, which may be denoted as Window [ 'Core' ] = Core, a common framework Vue mounted to the Window global variable, which may be denoted as Window [ 'Vue' ] = Vue, and a base component Module mounted to the Window global variable, which may be denoted as Window [ 'Module' ] = Module. Preferably, the common framework, the base library and the base component are mounted to the Window global variable, which is to be understood as assigning the common framework, the base library and the base component to the Window global variable, so that the candidate component can call the base library method or inherit the base component.
Referring to fig. 3, a flowchart of a method for determining component variable data corresponding to a component development instruction from preset component global variables according to an embodiment of the present invention is specifically described as follows.
S301, analyzing the component development instruction, and acquiring the names of the component modules in the component development instruction.
S302, determining a common component module of each component module name, and determining each determined common component module as a target module.
S303, determining the variable data of each target module in the component global variables, and determining each determined variable data as the component variable data.
In the method provided by the embodiment of the invention, the component development instruction comprises the name of the public component module which needs to be called when a developer develops a new component, the corresponding public component module is determined based on the name, and the variable data corresponding to the public component module in the component global variable is determined as the component variable data.
Preferably, the component development instruction includes at least one component module name, and the component variable data is a set of variable data corresponding to each component module name in the component development instruction.
And S102, generating a component corresponding to the component development instruction based on the component variable data, packaging the component, and issuing the packaged component to a preset node package manager.
Generating the component corresponding to the component development instruction based on the component variable data may be understood as performing component development using the component variable data to obtain a component, and further, in the process of developing the component, a basic library or a basic component may be directly introduced to develop a new component, and preferably, the developed component may be referred to as a third-party component; illustratively, the third-party component may be a component obtained by encapsulating, according to the content such as the picture and the text in the basic component and the http request acquisition function in the basic library, and the like, with the service logic.
After the developed components are obtained, packaging the components by using a packaging tool, preferably, the packaging tool can be Webpack; all common component Module names in the components can be put into the externals configuration, the externalsType is set to be "window", which means that the packaged modules read the common component modules from the window, and the output type of the modules is set to be UMD (Universal Module Definition in JavaScript), so that the compatibility of the modules running in the browser is ensured. Since the NPM is a third-party platform, and the number of modules is large, a certain limitation needs to be imposed on the component name, and preferably, a specific @ scope prefix may be added, for example: @ xxxx-modou/name.
After the components are packaged, the packaged components may be published to a predetermined Node Package Manager (NPM), so that the low-code platform may pull the published components from the NPM.
Referring to fig. 4, as an example of a flow for packaging a developed component provided by the embodiment of the present invention, as shown in the drawing, a third-party component may be introduced into a framework through fw = require [ 'vue' ] at the time of development, a foundation library through core = require [ 'core' ] and a foundation component through mod = require [ 'module' ], and when the third-party component is packaged, third-party component conversion is implemented through fw = window [ 'vue' ] in the framework, core = window [ 'core' ] in the foundation library and core = window [ 'core' ] in the package, and the packaged third-party component is issued to an NPM platform, preferably, the third-party component is a new component that needs to be developed by a developer.
Preferably, the newly developed component may be the first developed component or may be a component that has been developed but needs to be upgraded.
Further, after the component is published to the node packet manager, the information of the component needs to be added to the first component list in the node packet manager.
S103, when receiving the component downloading instruction, acquiring a first component list of the node packet manager, wherein the first component list comprises component information of each component issued on the node packet manager.
When the low-code platform needs to update or upgrade the components or add new components, a developer needs to send a component downloading instruction to the low-code platform, and the low-code platform obtains a first component list of the node packet manager after receiving the component downloading instruction.
Preferably, the component information in the first component list includes, but is not limited to, a component name and version information of the component, and further, versions of components having the same component name may be different, for example, a component name is a, a component of version 1.0 exists, and a component of version 2.0 exists. Further, the version information may include a version number identifier, that is, the component information at this time includes a component name and a version number identifier, for example, for a component with a component name of a, there are version 1.0 and version 2.0, the version number of version 1.0 is identified as 1.0, and the version number of version 2.0 is identified as 2.0, then the component has two pieces of component information, one piece of component information includes a component name of a and the version number of the component is 1.0, and the other piece of component information includes a component name of a and the version number of the component is 2.0. The version information may include a plurality of version number identifiers, and names of components to which the version number identifiers belong are the same, and the component information includes the version number identifiers having the component name a and the component name a as described above.
S104, acquiring a component selection instruction, wherein the component selection instruction comprises component selection information generated based on each component information in the first component list.
In the method provided by the embodiment of the invention, after the low-code platform acquires the first component list, the information of each component in the first component list is displayed to developers through a preset display module; acquiring a component selection instruction input by a developer based on information of each component; preferably, the component selection instruction includes a name of the component selected by the developer and corresponding version information.
And S105, pulling the component corresponding to the component selection information from the node manager, and installing the pulled component to the low-code platform.
Referring to fig. 5, a flowchart of a method for pulling a component corresponding to component selection information from a node manager according to an embodiment of the present invention is specifically described as follows:
s401, obtaining the component name and the component version number in the component selection information.
And analyzing the component selection information so as to obtain the component name and the component version number in the component selection information.
S402, determining all the components with the same names as the component names in the node manager as target components.
S403, determining the version number of each target component, and determining the target component of which the version number is consistent with the component version number as the component corresponding to the component selection information.
In the method provided by the embodiment of the invention, after the component corresponding to the component selection information is pulled, the pulled component can be decompressed and renamed to obtain the script file corresponding to the component, and the script file is stored in the server side of the low-code platform, so that the installation of the component on the low-code platform is completed.
In the method provided by the embodiment of the invention, when an assembly development instruction is received, assembly variable data corresponding to the assembly development instruction is determined in a preset assembly global variable, wherein the assembly global variable is a variable obtained by mounting each common assembly module of a low-code platform to a Window global variable; generating a component corresponding to the component development instruction based on the component variable data, packaging the component, and issuing the packaged component to a preset node package manager; when a component downloading instruction is received, acquiring a first component list of a node packet manager, wherein the first component list comprises component information of each component issued on the node packet manager; acquiring a component selection instruction, wherein the component selection instruction comprises component selection information generated based on each component information in the first component list; and pulling the component corresponding to the component selection information from the node manager, and installing the pulled component to the low-code platform. The method includes the steps that all public component modules of a low-code platform are mounted to a Window global variable to obtain component variable data, data are called from the component variable data to be developed in the component development process, developed components are published in a node packet manager, and when new components need to be added to the low-code platform, the corresponding components can be directly pulled from the node packet manager, so that the codes of the whole low-code platform do not need to be pulled to develop the components, and development cost is effectively reduced.
Referring to fig. 6, which is an exemplary diagram of a component processing flow provided in an embodiment of the present invention, as shown in the figure, a low-code platform downloads a component to be installed from an NPM platform, and a server of the low-code platform decompresses and renames the downloaded component to obtain a corresponding script file, where the script file may be a js file, and the name of the js file may be named by using the name of the downloaded component and the version number of the component; and storing the script file in a server of the low-code platform to complete the installation of the component, and updating the information of the installed component to a component list of the low-code platform.
Preferably, the server of the low-code platform can also send a second component list to the client in the low-code platform, wherein the second component list contains information of each component installed in the low-code platform; the client feeds back a selection instruction to the server based on the second component list, and the server of the low-code platform feeds back a script file of a component corresponding to the selection instruction to the client so that the client can construct a page by using the script file; furthermore, the selection instruction includes the name and version number of the component selected by the client, the low-code platform can search the corresponding script file according to the name and version number of the component in the selection instruction, and the client can use the script file to read the data of the corresponding component from Window.
Corresponding to the method shown in fig. 1, the present invention also provides a component processing apparatus for supporting the specific implementation of the method shown in fig. 1, which may be configured in a low-code platform.
Referring to fig. 7, a schematic structural diagram of a component processing apparatus according to an embodiment of the present invention is specifically described as follows:
the determining unit 601 is configured to determine, when an assembly development instruction is received, assembly variable data corresponding to the assembly development instruction in preset assembly global variables, where the assembly global variables are variables obtained by mounting each common assembly module of a low-code platform to a Window global variable;
a generating unit 602, configured to generate, based on the component variable data, a component corresponding to the component development instruction, package the component, and issue the packaged component to a preset node package manager;
a first obtaining unit 603, configured to obtain, when a component download instruction is received, a first component list of the node bundle manager, where the first component list includes component information of each component issued on the node bundle manager;
a second obtaining unit 604, configured to obtain a component selection instruction, where the component selection instruction includes component selection information generated based on each component information in the first component list;
an installing unit 605, configured to pull the component corresponding to the component selection information from the node manager, and install the pulled component to the low-code platform.
In the device provided by the embodiment of the invention, when a component development instruction is received, component variable data corresponding to the component development instruction is determined in a preset component global variable, wherein the component global variable is a variable obtained by mounting each common component module of a low-code platform to a Window global variable; generating a component corresponding to the component development instruction based on the component variable data, packaging the component, and issuing the packaged component to a preset node packet manager; when a component downloading instruction is received, acquiring a first component list of a node packet manager, wherein the first component list comprises component information of each component issued on the node packet manager; acquiring a component selection instruction, wherein the component selection instruction comprises component selection information generated based on each component information in the first component list; and pulling the component corresponding to the component selection information from the node manager, and installing the pulled component to the low-code platform. The method includes the steps that all public component modules of a low-code platform are mounted to a Window global variable to obtain component variable data, data are called from the component variable data to be developed in the component development process, developed components are published in a node packet manager, and when new components need to be added to the low-code platform, the corresponding components can be directly pulled from the node packet manager, so that the codes of the whole low-code platform do not need to be pulled to develop the components, and development cost is effectively reduced.
In an apparatus provided by another embodiment of the present invention, the determining unit 601 includes:
the first acquisition subunit is used for analyzing the component development instruction to acquire the names of the component modules in the component development instruction;
the first determining subunit is used for determining a common component module of each component module name and determining each determined common component module as a target module;
and the second determining subunit is used for determining the variable data of each target module in the component global variables and determining the determined variable data as the component variable data.
In an apparatus provided by another embodiment of the present invention, the second obtaining unit 604 includes:
the display subunit is used for displaying the information of each component in the first component list to developers through a preset display module;
and the second acquisition subunit is used for acquiring a component selection instruction input by the developer based on each component information.
In another embodiment of the present invention, the installation unit 605 includes:
a third obtaining subunit, configured to obtain a component name and a component version number in the component selection information;
a third determining subunit, configured to determine, as target components, each component in the node manager whose name is the same as the component name;
and the fourth determining subunit is used for determining the version number of each target component, and determining the target component of which the version number is consistent with the component version number as the component corresponding to the component selection information.
Another embodiment of the present invention provides an apparatus, further comprising:
a sending unit, configured to send a second component list of the low-code platform to a preset client, where the second component list includes information of each component installed in the low-code platform;
a third obtaining unit, configured to obtain a selection instruction fed back by the client based on the second component list;
and the feedback unit is used for feeding back the script file of the component corresponding to the selection instruction to the client side, so that the client side uses the script file to construct a page.
The embodiment of the invention also provides a storage medium, which comprises a stored instruction, wherein when the instruction runs, the device where the storage medium is located is controlled to execute the component processing method.
The electronic device of the present invention is further provided, and the structural diagram thereof is shown in fig. 8, and specifically includes a memory 701 and one or more instructions 702, where the one or more instructions 702 are stored in the memory 701, and are configured to be executed by the one or more processors 703 to execute the one or more instructions 702 to perform the component processing method.
The specific implementation procedures and derivatives thereof of the above embodiments are within the scope of the present invention.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, the system or system embodiments are substantially similar to the method embodiments and therefore are described in a relatively simple manner, and reference may be made to some of the descriptions of the method embodiments for related points. The above-described system and system embodiments are only illustrative, wherein the units described as separate parts may or may not be physically separate, and the parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement without inventive effort.
Those of skill would further appreciate that the various illustrative components and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the components and steps of the various examples have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (10)
1. A component handling method, comprising:
when an assembly development instruction is received, determining assembly variable data corresponding to the assembly development instruction in preset assembly global variables, wherein the assembly global variables are variables obtained by mounting all common assembly modules of a low-code platform to Window global variables;
generating a component corresponding to the component development instruction based on the component variable data, packaging the component, and issuing the packaged component to a preset node package manager;
when a component downloading instruction is received, acquiring a first component list of the node packet manager, wherein the first component list comprises component information of each component issued on the node packet manager;
acquiring a component selection instruction, wherein the component selection instruction comprises component selection information generated based on each component information in the first component list;
and pulling the component corresponding to the component selection information from the node manager, and installing the pulled component to the low-code platform.
2. The method according to claim 1, wherein the determining component variable data corresponding to the component development instruction in the preset component global variables comprises:
analyzing the component development instruction to obtain the names of all component modules in the component development instruction;
determining a common component module of each component module name, and determining each determined common component module as a target module;
and determining the variable data of each target module in the component global variables, and determining the determined variable data as component variable data.
3. The method of claim 1, wherein the obtaining component selection instructions comprises:
displaying the information of each component in the first component list to developers through a preset display module;
and acquiring a component selection instruction input by the developer based on each component information.
4. The method according to claim 1, wherein the pulling the component corresponding to the component selection information from the node manager comprises:
acquiring a component name and a component version number in the component selection information;
determining each component with the same name as the component name in the node manager as a target component;
and determining the version number of each target component, and determining the target component with the version number consistent with the component version number as the component corresponding to the component selection information.
5. The method of claim 1, further comprising:
sending a second component list of the low-code platform to a preset client, wherein the second component list comprises information of each component installed in the low-code platform;
acquiring a selection instruction fed back by the client based on the second component list;
and feeding back the script file of the component corresponding to the selection instruction to the client, so that the client builds a page by using the script file.
6. A component handling apparatus, comprising:
the device comprises a determining unit, a calculating unit and a calculating unit, wherein the determining unit is used for determining component variable data corresponding to a component development instruction in a preset component global variable when the component development instruction is received, and the component global variable is a variable obtained by mounting each common component module of a low-code platform to a Window global variable;
the generating unit is used for generating a component corresponding to the component development instruction based on the component variable data, packaging the component and issuing the packaged component to a preset node packet manager;
a first obtaining unit, configured to obtain a first component list of the node bundle manager when a component download instruction is received, where the first component list includes component information of each component issued on the node bundle manager;
a second obtaining unit, configured to obtain a component selection instruction, where the component selection instruction includes component selection information generated based on each component information in the first component list;
and the installation unit is used for pulling the component corresponding to the component selection information from the node manager and installing the pulled component to the low-code platform.
7. The apparatus of claim 6, wherein the determining unit comprises:
the first obtaining subunit is used for analyzing the component development instruction to obtain the names of the component modules in the component development instruction;
the first determining subunit is used for determining a common component module of each component module name and determining each determined common component module as a target module;
and the second determining subunit is used for determining the variable data of each target module in the component global variables and determining the determined variable data as the component variable data.
8. The apparatus of claim 6, wherein the second obtaining unit comprises:
the display subunit is used for displaying the information of each component in the first component list to developers through a preset display module;
and the second acquisition subunit is used for acquiring a component selection instruction input by the developer based on each component information.
9. A storage medium comprising stored instructions, wherein the instructions, when executed, control a device on which the storage medium resides to perform the component processing method of any one of claims 1-5.
10. An electronic device comprising a memory and one or more instructions, wherein the one or more instructions are stored in the memory and configured to be executed by the one or more processors to perform the component processing method of any one of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211293370.XA CN115658032A (en) | 2022-10-21 | 2022-10-21 | Component processing method and device, storage medium and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211293370.XA CN115658032A (en) | 2022-10-21 | 2022-10-21 | Component processing method and device, storage medium and electronic equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115658032A true CN115658032A (en) | 2023-01-31 |
Family
ID=84989297
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211293370.XA Pending CN115658032A (en) | 2022-10-21 | 2022-10-21 | Component processing method and device, storage medium and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115658032A (en) |
-
2022
- 2022-10-21 CN CN202211293370.XA patent/CN115658032A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8612947B2 (en) | System and method for remotely compiling multi-platform native applications for mobile devices | |
| CN108847950B (en) | Electronic device, cloud system software automatic deployment method and storage medium | |
| US7640542B2 (en) | Managing midlet suites in OSGI environment | |
| CN111273898A (en) | Web front-end code automatic construction method, system and storage medium | |
| US20100281475A1 (en) | System and method for mobile smartphone application development and delivery | |
| CN106325847B (en) | Method and device for acquiring application program function based on iOS platform | |
| US8856685B2 (en) | Method and system for providing web content on a mobile device | |
| CN111680253B (en) | Page application data packet generation method and device, computer equipment and storage medium | |
| CN111324421B (en) | Container mirror image providing method, loading method, related equipment and system | |
| CN113050984A (en) | Resource calling method and device, electronic equipment and storage medium | |
| CN111142884A (en) | Applet version deployment method and device, electronic equipment and storage medium | |
| CN110716786B (en) | Page display method, system and storage medium | |
| CN112835568A (en) | Project construction method and device | |
| CN110113391B (en) | Client online method and device and client operation method and device | |
| CN113010178B (en) | Application program operation control method, device, equipment and medium | |
| CN114217789A (en) | Function component expansion method, device, equipment, storage medium and program product | |
| CN116166907B (en) | Method and device for developing Web application by using WebAsssembly and service page compiling technology | |
| CN111930455A (en) | Page updating method, device, terminal and storage medium | |
| CN111488286A (en) | Method and device for independently developing Android module | |
| CN111625291A (en) | Automatic iteration method and device of data processing model and electronic equipment | |
| CN115658032A (en) | Component processing method and device, storage medium and electronic equipment | |
| CN110727423A (en) | Method and system for developing mobile application program across platforms | |
| CN110502251B (en) | Application installation method and device | |
| CN107247661A (en) | Support the method and system to the installation kit progress automatic Verification of application | |
| CN113791778A (en) | Software project generation method and device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |