CN113760229A

CN113760229A - Front-end project generation method and system, electronic equipment and storage medium

Info

Publication number: CN113760229A
Application number: CN202110133309.8A
Authority: CN
Inventors: 魏兵兵
Original assignee: Beijing Jingdong Tuoxian Technology Co Ltd
Current assignee: Beijing Jingdong Tuoxian Technology Co Ltd
Priority date: 2021-01-29
Filing date: 2021-01-29
Publication date: 2021-12-07

Abstract

The present disclosure provides a front-end project generation method, including: receiving a downloading instruction; pulling a front-end project configuration file specified by the downloading instruction from a preset configuration file management library, and pulling a dependent package specified by the downloading instruction from a dependent package management library; and installing the front-end project configuration file and the dependency package in the local to finish the generation of the front-end project.

Description

Front-end project generation method and system, electronic equipment and storage medium

Technical Field

The present disclosure relates to the field of internet technologies, and in particular, to a front-end project generation method, a front-end project generation system, an electronic device, and a computer storage medium.

Background

In the era of rapid development of computer technology, it is important to provide agile development efficiency, unified management, flexible technology stack and better maintenance for products in order to make the products better.

In the prior art, many developers carry out rapid project generation in a mode of copying and pasting, generating pages by one key and generating code blocks by one key, and the mode has the problems of no version control of programs, single functions of generated pages and code blocks, difficult correlation and maintenance, low participation of project development members and the like due to the fact that technical stacks are bound. At present, no solution for realizing project, UI component, business component, combination of different project technology stacks or multiple composite overlays exists for the moment.

Disclosure of Invention

In view of this, the present disclosure provides a front-end item generating method, including: receiving a downloading instruction; pulling a front-end project configuration file specified by the downloading instruction from a preset configuration file management library, and/or pulling a dependency package specified by the downloading instruction from a preset dependency package management library; and installing the front-end project configuration file and the dependency package in the local to finish the generation of the front-end project.

According to the embodiment of the present disclosure, after receiving the download instruction, the method further includes: inquiring whether the front-end item exists locally; if the front-end project does not exist locally, pulling the front-end project configuration file from the configuration file management library, and/or pulling the dependency package from the dependency package management library to generate the front-end project; and if the front-end item exists locally, prompting a user whether to update or cover the front-end item.

According to an embodiment of the present disclosure, after prompting the user whether to update or cover the front-end item, the method includes: when a user agrees to update or cover, pulling the front-end project configuration file specified by the downloading instruction from the configuration file management library, and/or pulling the dependency package specified by the downloading instruction from the dependency package management library to update or cover the front-end project; and when the user does not agree to update or cover, pulling the dependency package specified by the downloading instruction from the dependency package management library, and only updating the item dependency of the front-end item.

According to an embodiment of the present disclosure, further comprising: receiving an updating instruction; prompting a user whether to update or cover the front-end item specified by the updating instruction according to the updating instruction;

after a user agrees to update or cover, pulling the front-end project configuration file specified by the update instruction from the configuration file management library, and/or pulling the dependency package specified by the update instruction from the dependency package management library to update or cover the front-end project; and when the user does not agree to update or cover, pulling the dependency package specified by the update instruction from the dependency package management library, and only updating the item dependency of the front-end item.

According to an embodiment of the present disclosure, the receiving an update instruction includes: inquiring whether a front-end item to be updated by the updating instruction exists locally; when the front-end item exists locally, prompting a user whether to update or cover the front-end item specified by the updating instruction; when the front-end item does not exist locally, ignoring the update instruction.

According to an embodiment of the disclosure, the profile management library includes a plurality of user-defined front-end project profiles, the dependency package management library includes a dependency package of the front-end project profiles, and the front-end project profiles and the dependency package are custom-developed by developers.

The other aspect of the present disclosure further provides a front-end project generating system, including a download instruction receiving module, configured to receive a download instruction; the file downloading module is used for pulling the front-end project configuration file specified by the downloading instruction from a preset configuration file management library and/or pulling the dependency package specified by the downloading instruction from a preset dependency package management library; and the project generation module is used for installing the front-end project configuration file and the dependency package in the local to finish the generation of the front-end project.

According to an embodiment of the present disclosure, further comprising: the first local item detection module is used for inquiring whether the front-end item exists locally; if the front-end project does not exist locally, the file downloading module is enabled to pull the front-end project configuration file from the configuration file management library, and/or pull the dependency package from the dependency package management library to generate the front-end project; and if the front-end item exists locally, prompting a user whether to update or cover the front-end item.

According to an embodiment of the present disclosure, further comprising: the first project updating module is used for pulling the front-end project configuration file specified by the downloading instruction from the configuration file management library and/or pulling the dependency package specified by the downloading instruction from the dependency package management library to update or cover the front-end project when a user agrees to update or cover; and the first dependency updating module is used for pulling the dependency package specified by the downloading instruction from the dependency package management library and only updating the item dependency of the front-end item when the user does not agree to update or override.

According to an embodiment of the present disclosure, further comprising: the updating instruction receiving module is used for receiving an updating instruction; the updating prompting module is used for prompting a user whether to update or cover the front-end project specified by the updating instruction according to the updating instruction; the second item updating module is further configured to, after the user agrees to perform updating or overwriting, pull the front-end item configuration file specified by the updating instruction from the configuration file management library, and/or pull the dependency package specified by the updating instruction from the dependency package management library, so as to update or overwrite the front-end item; and the second dependency updating module is further used for pulling the dependency package specified by the updating instruction from the dependency package management library and updating only the item dependency of the front-end item when the user does not agree to perform updating or overriding.

According to an embodiment of the present disclosure, further comprising: the second local item detection module is used for inquiring whether a front-end item to be updated by the updating instruction exists locally; when the front-end item exists locally, prompting a user whether to update or cover the front-end item specified by the update instruction through the update prompting module; when the front-end item does not exist locally, ignoring the update instruction.

The present disclosure also provides an electronic device, including: one or more processors; memory for storing one or more programs, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method of any of the first aspects.

The present disclosure also provides a computer-readable storage medium having stored thereon executable instructions that, when executed by a processor, cause the processor to carry out the method of any one of the first aspects.

According to the embodiment of the disclosure, the unified management of the project components is realized through the configuration file management library and the dependency package management library, so that a developer can complete the rapid generation of a front-end project by using one instruction, the project technology stack is flexible, the development efficiency is improved, and the developer can conveniently maintain the existing project.

Drawings

The above and other objects, features and advantages of the present disclosure will become more apparent from the following description of embodiments of the present disclosure with reference to the accompanying drawings, in which:

fig. 1 schematically illustrates an application scenario of a front-end project generation method according to an embodiment of the present disclosure;

FIG. 2 is a flow chart schematically illustrating a front-end project generation method provided by an embodiment of the present disclosure;

fig. 3 schematically shows a flowchart of operation S240 of the front-end item generation method provided according to an embodiment of the present disclosure;

fig. 4 schematically shows a flowchart of operation S242 of the front-end item generation method provided by the embodiment of the present disclosure;

fig. 5 schematically shows a flowchart of operation S250 of a front-end item generation method provided according to an embodiment of the present disclosure;

fig. 6 schematically shows a flowchart of operation S270 of the front-end item generation method provided according to an embodiment of the present disclosure;

FIG. 7 is a flow chart that schematically illustrates another front-end item generation method provided in accordance with an embodiment of the present disclosure;

FIG. 8 schematically shows a block diagram of a front-end project generation system provided in accordance with another embodiment of the present disclosure;

FIG. 9 schematically illustrates another block diagram of a front-end item generation system according to an embodiment of the present disclosure;

FIG. 10 schematically illustrates another block diagram of a front-end item generation system according to an embodiment of the present disclosure;

FIG. 11 schematically illustrates a block diagram of another portion of a front-end item generation system, in accordance with an embodiment of the present disclosure;

fig. 12 schematically shows another structural block diagram of another part of the front-end project generation system provided by another embodiment of the present disclosure;

FIG. 13 schematically shows a block diagram of a computer system of an electronic device according to an embodiment of the disclosure.

Detailed Description

Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that the description is illustrative only and is not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. Moreover, in the following description, descriptions of well-known structures and techniques are omitted so as to not unnecessarily obscure the concepts of the present disclosure.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and the like, as used herein, specify the presence of stated features, steps, operations, and components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.

All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It is noted that the terms used herein should be interpreted as having a meaning that is consistent with the context of this specification and should not be interpreted in an idealized or overly formal sense.

Where a convention analogous to "at least one of A, B and C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B and C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, A, B, C together, etc.). Where a convention analogous to "A, B or at least one of C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B or C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, A, B, C together, etc.).

The embodiment of the disclosure provides a front-end project generation method and a front-end project generation system. The method comprises the following steps: receiving a downloading instruction; pulling a front-end project configuration file specified by the downloading instruction from a preset configuration file management library, and/or pulling a dependency package specified by the downloading instruction from a preset dependency package management library; and installing the front-end project configuration file and the dependency package in the local to finish the generation of the front-end project.

Fig. 1 schematically shows a flowchart of a front-end project generation method provided by an embodiment of the present disclosure. It should be noted that fig. 1 is only an example of a system architecture to which the embodiments of the present disclosure may be applied to help those skilled in the art understand the technical content of the present disclosure, and does not mean that the embodiments of the present disclosure may not be applied to other devices, systems, environments or scenarios.

As shown in fig. 1, the system architecture 100 according to this embodiment may include

terminal devices

101, 102, 103, a network 104 and a server 105. The network 104 serves as a medium for providing communication links between the

terminal devices

101, 102, 103 and the server 105. Network 104 may include various connection types, such as wired and/or wireless communication links, and so forth.

The user may use the

terminal devices

101, 102, 103 to interact with the server 105 via the network 104 to receive or send messages or the like. The

terminal devices

101, 102, 103 may have installed thereon various communication client applications, such as a shopping-like application, a web browser application, a search-like application, an instant messaging tool, a mailbox client, and/or social platform software, etc. (by way of example only).

The

terminal devices

101, 102, 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.

The server 105 may be a server providing various services, such as a background management server (for example only) providing support for websites browsed by users using the

terminal devices

101, 102, 103. The background management server may analyze and perform other processing on the received data such as the user request, and feed back a processing result (e.g., a webpage, information, or data obtained or generated according to the user request) to the terminal device.

It should be noted that the front-end project generation method provided by the embodiment of the present disclosure may be generally executed by the server 105. Accordingly, the front-end project generation system provided by the disclosed embodiments may be generally disposed in the server 105. The front-end item generation method provided by the embodiment of the present disclosure may also be executed by a server or a server cluster that is different from the server 105 and is capable of communicating with the

terminal devices

101, 102, 103 and/or the server 105. Accordingly, the front-end item generation system provided by the embodiment of the present disclosure may also be disposed in a service broker or server cluster different from the server 105 and capable of communicating with the

terminal devices

101, 102, 103 and/or the server 105. Alternatively, the front-end item generation method provided by the embodiment of the present disclosure may also be executed by the

terminal device

101, 102, or 103, or may also be executed by another terminal device different from the

terminal device

101, 102, or 103. Accordingly, the front-end item generation system provided by the embodiment of the present disclosure may also be provided in the

terminal device

101, 102, or 103, or in another terminal device different from the

terminal device

101, 102, or 103.

For example, the project profile or dependency package used to generate the front-end project may be originally stored in any of the

terminal devices

101, 102, or 103 (e.g., but not limited to terminal device 101), or stored on an external storage device and may be imported into terminal device 101. Then, the terminal device 101 may locally execute the front-end item generation method provided by the embodiment of the present disclosure, or send the item configuration file or the dependency package of the generated front-end item to another terminal device, a server, or a server cluster, and execute the front-end item generation method provided by the embodiment of the present disclosure by another terminal device, a server, or a server cluster that receives the item configuration file or the dependency package of the generated front-end item.

It should be understood that the number of terminal devices, networks, and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

Fig. 2 schematically shows a flow chart of a front-end item generation method according to an embodiment of the present disclosure.

As shown in fig. 2, the method includes operations S210 to S230.

In operation S210, a download instruction is received.

In operation S220, a front-end project profile specified by the download instruction is pulled from a preset profile management library, and/or a dependency package specified by the download instruction is pulled from a preset dependency package management library.

In operation S230, the front-end project configuration file and the dependency package are installed locally, and the generation of the front-end project is completed.

In the project development, when a developer needs to generate a front-end project, because the basic modules of the front-end projects are different, a plurality of modules can be reused among the projects, and the modules can be stored in a library for unified management, so that the development efficiency is improved.

According to an embodiment of the disclosure, the profile management library may manage a large number of front-end project profiles for various types of code hosting platforms, such as Git and the like, and the dependency package management library may also manage dependency packages for various types of code hosting platforms, such as nmp and the like, using nmp. The two different types of files are separately managed through the two libraries, so that the different types of files are convenient to independently maintain, the use is convenient, the two types of files can be downloaded and installed at one time through an instruction including the project configuration file and the dependent package name, and the steps of generating the front-end project are simplified.

The configuration file management library comprises a plurality of user-defined front-end project configuration files, the dependency package management library comprises dependency packages of the front-end project configuration files, and the front-end project configuration files and the dependency packages are developed in a self-defined mode by developers. The developer can maintain the project configuration files and the dependency packages in the configuration file management library and the dependency package management library at irregular intervals, and when the project configuration files and the dependency packages of the existing front-end projects need to be updated, the project configuration files and the dependency packages can be realized only through one downloading instruction.

Optionally, the download instruction includes a front-end project name, a project profile name or a dependent package name. For example, the download instruction may be used as a project generation instruction, which is used to enable the computer to download corresponding files from the configuration file management library and the dependency package management library according to the instruction, and install the corresponding files locally to generate a new front-end project. The download instructions may also be used to download a designated project profile or dependency package for an existing project to add functional modules to the project, update existing functional modules or update dependencies, and the like.

Optionally, the download instruction may be encapsulated by a method of a development tool such as node.js, for example, using a command.js, download.js, download-git-response.js, inquire.js, and the like, and implementing different functions according to different download instructions, so that the computer implements generation or update of a front-end project according to the download instruction, and provides a related document for the project. For example, through a command, description, action and other methods of a command.

Fig. 3 schematically shows a flowchart of operation S240 of the front-end item generation method provided according to an embodiment of the present disclosure.

As shown in fig. 3, after receiving the download instruction according to operation S210, the front-end item generation method according to the embodiment of the present disclosure further includes operation S240, specifically, operation S240 includes operations S241 to S242.

In operation S240, it is queried whether the front-end item exists locally.

In operation S241, if the front-end item does not exist locally, the front-end item profile is pulled from the profile management repository, and/or the dependency package is pulled from the dependency package management repository to generate the front-end item.

In operation S242, if the front-end item exists locally, the user is prompted whether to update or overwrite the front-end item.

In the embodiment of the present disclosure, after receiving the download instruction, before downloading the file specified in the download instruction, it should be first determined whether an item specified in the instruction already exists locally, so as to avoid repeated generation of the item, and according to the query result, operation S241 and operation S242 are respectively performed. Illustratively, whether the same front-end item exists locally can be judged by an existSync method of fs-extra.

Fig. 4 schematically shows a flowchart of operation S242 provided by the embodiment of the present disclosure.

Referring to fig. 4, according to operation S242, there are two cases divided into S2421 and S2422 according to the user response.

In operation S2421, when the user agrees to update or override, the front-end project profile specified by the download instruction is pulled from the profile management repository, and/or the dependency package specified by the download instruction is pulled from the dependency package management repository to update or override the front-end project.

According to the embodiment of the disclosure, when the user agrees to update the original front-end item, the corresponding file is downloaded from the corresponding library according to the front-end item configuration file or the dependent package name included in the download instruction, and is used for updating the file corresponding to the front-end item specified in the download instruction, so as to update the front-end item. Illustratively, the downloading of the project file specified by the downloading instruction from the Git library can be realized through a download-Git-repo.js plug-in, the project configuration file pulled down from the Git library is read through an fs.js plug-in, the option of a project template is provided for an inquire.js plug-in, and a user can select the project configuration file to install, for example, the installation of the dependent package can be realized through the express definition of more dependent installation modes such as differentiated encapsulation yarn npm and the like of the execa.js plug-in.

In operation S2422, when the user does not agree to update or override, the dependency package specified by the download instruction is pulled from the dependency package management library, and only the item dependencies of the front-end items are updated.

According to the embodiment of the disclosure, when the user does not agree to update or cover the file of the front-end project specified in the download instruction, the continuous execution of the download instruction is cancelled, and the original front-end project is prevented from being damaged.

Optionally, after the file is successfully or unsuccessfully installed, the installation result is displayed, wherein when the installation is unsuccessfully installed, error information needs to be displayed and the code prompted by the information needs to be demonstrated.

Fig. 5 schematically shows a flowchart of operation S250 provided according to an embodiment of the present disclosure.

As shown in fig. 5, the front-end project generating method provided in the embodiment of the present disclosure may further include operations S250 to S260, that is, the instruction edited by the user may further include an update instruction besides the download instruction, and the existing local project may be updated according to the update instruction.

In operation S250, an update instruction is received.

Operation S260, according to the update instruction, prompting the user whether to update or overwrite the front-end item specified by the update instruction.

In operation S261, after the user agrees to perform the update or the overlay, the front-end item configuration file specified by the update instruction is pulled from the configuration file management library, and/or the dependency package specified by the update instruction is pulled from the dependency package management library, so as to update or overlay the front-end item.

In operation S262, when the user does not agree to perform the update or the override, the dependency package specified by the update instruction is pulled from the dependency package management library, and only the item dependency of the front-end item is updated.

In the embodiment of the present disclosure, after the update instruction is obtained, the specific operations S260, S261, and S262 are the same as the operations S242, S2421, and S2422, which are not described herein again.

Fig. 6 schematically shows a flowchart of operation S270 of the front-end item generation method provided according to an embodiment of the present disclosure.

Referring to fig. 6, similar to operation S210, after receiving the update instruction in operation S250, it is first detected whether the front-end item specified by the update instruction already exists locally according to step S270, which is specifically divided into two cases S271 and S272. Operation S270 is performed to query whether a front-end item to be updated by the update instruction exists locally.

In operation S271, when the front-end item exists locally, the user is prompted whether to update or overwrite the front-end item specified by the update instruction.

In operation S272, when the front-end item does not exist locally, the update instruction is ignored.

Fig. 7 schematically shows another flow chart of a front-end project generation method provided according to an embodiment of the present disclosure.

As shown in fig. 7, in conjunction with operations S210 to S270, the overall flow diagram of the front-end project generation method provided in the embodiment of the present disclosure is shown.

According to the front-end project generation method provided by the embodiment of the disclosure, the unified management of project components is realized through the configuration file management library and the dependency package management library, the flexible definition of projects and technical stacks can be realized, the projects can be flexibly configured, developers can complete the rapid generation of front-end projects by using one instruction, the development efficiency is improved, the perfect version disclosure is facilitated, the maintenance cost is low, and the method enables the front-end project development process to be standardized and easy to master.

Fig. 8 schematically shows a block diagram of a front-end item generation system provided according to another embodiment of the present disclosure.

As shown in fig. 8, another embodiment of the present disclosure provides a front-end project generating system 310, which specifically includes a download instruction receiving module 311, a file downloading module 312, and a project generating module 313.

The download instruction receiving module 311 is configured to receive a download instruction.

The file downloading module 312 is configured to pull the front-end project configuration file specified by the downloading instruction from a preset configuration file management library, and/or pull the dependency package specified by the downloading instruction from a preset dependency package management library.

And the project generation module 313 is configured to locally install the front-end project configuration file and the dependency package to complete generation of the front-end project.

According to the embodiment of the present disclosure, the file downloading module 312 is configured to receive a downloading instruction, and the file downloading module 312 is configured to download a corresponding file from the configuration file management library and/or the dependency package management library according to the downloading instruction, so that the project generating module 313 generates a corresponding front-end project according to the file.

Fig. 9 schematically shows another block diagram of the front-end project generation system 310 according to an embodiment of the present disclosure.

As shown in fig. 9, the front-end item generation system 310 may further include a first local item detection module 314 in addition to the download instruction receiving module 311, the file download module 312, and the item generation module 313.

The first local item detection module 314 is configured to query whether the front-end item exists locally.

If the front-end project does not exist locally, the file downloading module is enabled to pull the front-end project configuration file from the configuration file management library, and/or pull the dependency package from the dependency package management library to generate the front-end project.

And if the front-end item exists locally, prompting a user whether to update or cover the front-end item.

According to the embodiment of the disclosure, the first local item detection module 314 detects whether there is a front-end item requested to be generated by the download instruction locally, so that repeated generation of the same item can be avoided.

Fig. 10 schematically shows another structural block diagram of the front-end item generation system according to the embodiment of the present disclosure.

As shown in fig. 10, the front-end item generation system may further include a first item update module 315 and a first dependency update module 316 according to the detection result of the first local item detection module 314.

A first item updating module 315, configured to, when the user agrees to perform the update or override, pull the front-end item configuration file specified by the download instruction from the configuration file management library through the file downloading module 312, and/or pull the dependency package specified by the download instruction from the dependency package management library, so as to update or override the front-end item.

A first dependency updating module 316, configured to, when the user does not agree to perform the updating or overriding, pull the dependency package specified by the download instruction from the dependency package management library through the file downloading module 312, and update only the item dependencies of the front-end items.

According to the embodiment of the present disclosure, the system implements the update or overlay of the item by the first item update module 315 and the first dependent update module 316, respectively, according to the selection of the user, so that the item is updated to the degree required by the user.

Fig. 11 schematically shows a block diagram of another part of the front-end item generation system according to an embodiment of the present disclosure.

As shown in fig. 11, the front-end project generation system 310 may further include another part 320, specifically including: an update instruction receiving module 321, an update prompting module 322, a second item updating module 323, and a second dependency updating module 324.

The update instruction receiving module 321 is configured to receive an update instruction.

And an update prompting module 322, configured to prompt a user whether to update or overwrite the front-end item specified by the update instruction according to the update instruction.

The second item updating module 323 is further configured to, after the user agrees to perform the update or the overlay, pull the front-end item configuration file specified by the update instruction from the configuration file management library through the file downloading module 312, and/or pull the dependency package specified by the update instruction from the dependency package management library, so as to update or overlay the front-end item.

The second dependency updating module 324 is further configured to, when the user does not agree to perform the updating or overriding, pull the dependency package specified by the updating instruction from the dependency package management library through the file downloading module 312, and update only the item dependencies of the front-end items.

According to the embodiment of the present disclosure, the update instruction receiving module 321, the update prompting module 322, the second item updating module 323, and the second dependent updating module 324 are similar to or identical to the download instruction receiving module 311, the first local item detecting module 314, the first item updating module 315, and the second item updating module 316, respectively.

Fig. 12 schematically shows another structural block diagram of another part of the front-end project generation system according to another embodiment of the present disclosure.

As shown in FIG. 12, another portion 320 of the front end item generation system 310 may further include: a second local item detection module 325.

The second local item detection module 325 is configured to query whether there is a front-end item to be updated by the update instruction locally.

And when the front-end item exists locally, prompting whether the user updates or covers the front-end item specified by the updating instruction or not through the updating prompting module.

When the front-end item does not exist locally, ignoring the update instruction.

According to an embodiment of the present disclosure, the second local item detection module 325 is similar in function to the second module between the first local items, with duplication in function.

Any number of modules, sub-modules, units, sub-units, or at least part of the functionality of any number thereof according to embodiments of the present disclosure may be implemented in one module. Any one or more of the modules, sub-modules, units, and sub-units according to the embodiments of the present disclosure may be implemented by being split into a plurality of modules. Any one or more of the modules, sub-modules, units, sub-units according to embodiments of the present disclosure may be implemented at least in part as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented in any other reasonable manner of hardware or firmware by integrating or packaging a circuit, or in any one of or a suitable combination of software, hardware, and firmware implementations. Alternatively, one or more of the modules, sub-modules, units, sub-units according to embodiments of the disclosure may be at least partially implemented as a computer program module, which when executed may perform the corresponding functions.

For example, any plurality of the download instruction receiving module 311, the file downloading module 312, and the item generating module 313 may be combined into one module/unit/sub-unit to be implemented, or any one of the modules/units/sub-units may be divided into a plurality of modules/units/sub-units. Alternatively, at least part of the functionality of one or more of these modules/units/sub-units may be combined with at least part of the functionality of other modules/units/sub-units and implemented in one module/unit/sub-unit. According to the embodiment of the present disclosure, at least one of the download instruction receiving module 311, the file downloading module 312, and the item generating module 313 may be implemented at least partially as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented by hardware or firmware in any other reasonable manner of integrating or packaging a circuit, or implemented by any one of three implementations of software, hardware, and firmware, or implemented by a suitable combination of any several of them. Alternatively, at least one of the download instruction receiving module 311, the file downloading module 312, and the item generating module 313 may be at least partially implemented as a computer program module, which when executed, may perform a corresponding function.

FIG. 13 schematically illustrates a block diagram of a computer system suitable for implementing an electronic device according to an embodiment of the disclosure. The computer system illustrated in FIG. 13 is only one example and should not impose any limitations on the scope of use or functionality of embodiments of the disclosure.

As shown in fig. 13, a computer system 400 according to an embodiment of the present disclosure includes a processor 401 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)402 or a program loaded from a storage section 408 into a Random Access Memory (RAM) 403. Processor 401 may include, for example, a general purpose microprocessor (e.g., a CPU), an instruction set processor and/or associated chipset, and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), among others. The processor 410 may also include onboard memory for caching purposes. Processor 410 may include a single processing unit or multiple processing units for performing different actions of the method flows described with reference to fig. 2-6 in accordance with embodiments of the present disclosure.

In the RAM 403, various programs and data necessary for the operation of the system 400 are stored. The processor 401, ROM 402 and RAM 403 are connected to each other by a bus 404. The processor 401 performs various operations of the method of processing a search operation of a user described above with reference to fig. 2 to 9 by executing programs in the ROM 402 and/or the RAM 403. Note that the programs may also be stored in one or more memories other than the ROM 402 and RAM 403. The processor 401 may also perform various operations of the method of processing a user's search operation described above with reference to fig. 2-6 by executing the programs stored in the one or more memories.

According to an embodiment of the present disclosure, system 400 may also include an input/output (I/O) interface 405, input/output (I/O) interface 405 also connected to bus 404. The system 400 may also include one or more of the following components connected to the I/O interface 405: an input section 406 including a keyboard, a mouse, and the like; an output section 407 including a display device such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage section 408 including a hard disk and the like; and a communication section 409 including a network interface card such as a LAN card, a modem, or the like. The communication section 809 performs communication processing via a network such as the internet. A driver 410 is also connected to the I/O interface 405 as needed. A removable medium 411 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 410 as necessary, so that a computer program read out therefrom is mounted into the storage section 408 as necessary.

According to an embodiment of the present disclosure, the method described above with reference to the flow chart may be implemented as a computer software program. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 409, and/or installed from the removable medium 411. The computer program, when executed by the processor 401, performs the above-described functions defined in the system of the embodiments of the present disclosure. The systems, devices, apparatuses, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the present disclosure.

It should be noted that the computer readable media shown in the present disclosure may be computer readable signal media or computer readable storage media or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In contrast, in the present disclosure, a computer-readable signal medium may include a propagated data signal with computer-readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing. According to embodiments of the present disclosure, a computer-readable medium may include the ROM 402 and/or RAM 403 and/or one or more memories other than the ROM 402 and RAM 403 described above.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

As another aspect, the present disclosure also provides a computer-readable medium, which may be contained in the apparatus described in the above embodiments; or may be separate and not incorporated into the device. The computer readable medium carries one or more programs which, when executed by a device, cause the device to perform: acquiring one or more search parameters input by a user; when the one or more search parameters meet a preset condition, sending a search request according to the one or more search parameters; receiving a search result corresponding to the search request; and responding to the confirmation operation of the user and displaying the search result.

The embodiments of the present disclosure have been described above. However, these examples are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Although the embodiments are described separately above, this does not mean that the measures in the embodiments cannot be used in advantageous combination. The scope of the disclosure is defined by the appended claims and equivalents thereof. Various alternatives and modifications can be devised by those skilled in the art without departing from the scope of the present disclosure, and such alternatives and modifications are intended to be within the scope of the present disclosure.

Claims

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

receiving a downloading instruction;

pulling a front-end project configuration file specified by the downloading instruction from a configuration file management library, and/or pulling a dependency package specified by the downloading instruction from a dependency package management library;

and installing the front-end project configuration file and the dependency package in the local to finish the generation of the front-end project.

2. The method of claim 1, after receiving the download instruction, further comprising:

inquiring whether the front-end item exists locally;

if the front-end project does not exist locally, pulling the front-end project configuration file from the configuration file management library, and/or pulling the dependency package from the dependency package management library to generate the front-end project;

3. The method of claim 2, wherein prompting the user whether to update or overwrite the front-end item comprises:

when a user agrees to update or cover, pulling the front-end project configuration file specified by the downloading instruction from the configuration file management library, and/or pulling the dependency package specified by the downloading instruction from the dependency package management library to update or cover the front-end project;

and when the user does not agree to update or cover, pulling the dependency package specified by the downloading instruction from the dependency package management library, and only updating the item dependency of the front-end item.

4. The method of claim 1, further comprising:

receiving an updating instruction;

prompting a user whether to update or cover the front-end item specified by the updating instruction according to the updating instruction;

after a user agrees to update or cover, pulling the front-end project configuration file specified by the update instruction from the configuration file management library, and/or pulling the dependency package specified by the update instruction from the dependency package management library to update or cover the front-end project;

and when the user does not agree to update or cover, pulling the dependency package specified by the update instruction from the dependency package management library, and only updating the item dependency of the front-end item.

5. The method of claim 4, wherein the receiving an update instruction comprises:

inquiring whether a front-end item to be updated by the updating instruction exists locally;

when the front-end item exists locally, prompting a user whether to update or cover the front-end item specified by the updating instruction;

6. The method of claim 1, wherein the profile management library comprises a plurality of user-customized front-end project profiles, the dependency package management library comprises a dependency package for the front-end project profiles, and the front-end project profiles and the dependency package are custom developed by a developer.

7. A front-end project generation system includes

The download instruction receiving module is used for receiving a download instruction;

the file downloading module is used for pulling the front-end project configuration file specified by the downloading instruction from a preset configuration file management library and/or pulling the dependency package specified by the downloading instruction from a preset dependency package management library;

and the project generation module is used for installing the front-end project configuration file and the dependency package in the local to finish the generation of the front-end project.

8. The system of claim 7, further comprising:

the first local item detection module is used for inquiring whether the front-end item exists locally;

if the front-end project does not exist locally, the file downloading module is enabled to pull the front-end project configuration file from the configuration file management library, and/or pull the dependency package from the dependency package management library to generate the front-end project;

9. The system of claim 8, further comprising:

the first project updating module is used for pulling the front-end project configuration file specified by the downloading instruction from the configuration file management library through the file downloading module and/or pulling the dependency package specified by the downloading instruction from the dependency package management library to update or cover the front-end project when a user agrees to update or cover;

and the first dependency updating module is used for pulling the dependency package specified by the downloading instruction from the dependency package management library through the file downloading module and only updating the item dependency of the front-end item when the user does not agree to update or override.

10. The system of claim 7, further comprising:

the updating instruction receiving module is used for receiving an updating instruction;

the updating prompting module is used for prompting a user whether to update or cover the front-end project specified by the updating instruction according to the updating instruction;

the second item updating module is further used for pulling the front-end item configuration file specified by the updating instruction from the configuration file management library through the file downloading module and/or pulling the dependency package specified by the updating instruction from the dependency package management library to update or cover the front-end item after the user agrees to update or cover;

and the second dependency updating module is further used for pulling the dependency package specified by the updating instruction from the dependency package management library through the file downloading module and only updating the item dependency of the front-end item when the user does not agree to perform updating or covering.

11. The system of claim 10, further comprising:

the second local item detection module is used for inquiring whether a front-end item to be updated by the updating instruction exists locally;

when the front-end item exists locally, prompting a user whether to update or cover the front-end item specified by the update instruction through the update prompting module;

12. The system of claim 7, wherein the profile management library comprises a plurality of user-customized front-end project profiles, the dependency package management library comprises a dependency package for the front-end project profiles, and the front-end project profiles and the dependency package are custom developed by a developer.

13. An electronic device, comprising:

one or more processors;

a memory for storing one or more programs,

wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method of any of claims 1-6.

14. A computer readable storage medium having stored thereon executable instructions which, when executed by a processor, cause the processor to carry out the method of any one of claims 1 to 6.