Front-end development methods, devices, equipment and media

By introducing user interaction interface and Electron technology in front-end development, the front-end development process is automatically managed, which solves the problem of low automation in the existing technology and improves development efficiency.

CN113703738BActive Publication Date: 2024-12-03工银科技有限公司 +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202111029459.0
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-09-02
Publication Date
2024-12-03
Estimated Expiration
2041-09-02

AI Technical Summary

Technical Problem

In the existing technology, the front-end development process has low degree of automation, and developers need to frequently switch various tools, resulting in extremely low efficiency.

Method used

Provide a front-end development method, which guides users to complete the full process management from project creation to deployment by displaying user interaction interface, and uses Electron technology to call third-party tools such as scaffolding tools, npm tools and continuous deployment platforms to realize an automated front-end development process. .

Benefits of technology

It realizes automated management of the entire front-end development process, simplifies the operation process, avoids tool switching, and significantly improves development efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113703738B_ABST
    Figure CN113703738B_ABST
Patent Text Reader

Abstract

The present disclosure provides a front-end development method that can be applied to the financial field. The front-end development method includes: displaying a first user interaction interface, the first user interaction interface includes M controls corresponding to the M stages included in the full process of the front-end development task, wherein the full process of the front-end development task includes the entire process from the project creation of the front-end development task to the deployment of the business code developed in the front-end development task to the server, wherein M is an integer greater than 1; in response to the selection operation of each of the M controls, displaying the second user interaction interface of the current stage corresponding to the selected control; based on the user interaction operation in the second user interaction interface of the current stage, developing the task of the current stage; and after the tasks of the M stages are all developed, feedback to the user the information that the front-end development task is completed. The present disclosure also provides a front-end development device, equipment, medium and program product.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to the field of Internet technology and can be used in the financial field. More specifically, it relates to a front-end development method, device, equipment, medium and program product. Background Art

[0002] With the continuous evolution of the front-end and back-end separation R&D model and front-end engineering, scaffolding tools, packaging tools, low-code platforms and continuous deployment platforms have also developed rapidly in the front-end field. Front-end development can be carried out based on various tools and platforms.

[0003] However, in the prior art, developers often need to switch tools frequently if they want to achieve a complete closed loop from research and development to launch. For example, developers need to use a scaffolding tool to initialize the project, and then switch to the npm tool to install the dependencies required for the project after the project is initialized. After the dependencies are installed, switch to the IDE tool to open the project for code development. After the code is developed, it is necessary to switch to the packaging tool to perform operations such as escaping, compression, and obfuscation on the code. After packaging, the code that we need to deploy to the production environment is generated. After that, the packaged code is stored in the specified directory of the server, and then the deployment tool is opened to deploy the code. It can be seen that the entire process of front-end development has a low degree of automation, and developers need to frequently switch between various tools, which is extremely inefficient. Summary of the invention

[0004] In view of the above problems, the embodiments of the present disclosure provide a front-end development method, apparatus, device, medium and program product that can automatically implement the full process management of front-end development.

[0005] In the first aspect of the disclosed embodiment, a front-end development method is provided. The method includes: displaying a first user interaction interface, the first user interaction interface includes M controls corresponding to the M stages included in the full process of the front-end development task, wherein the full process of the front-end development task includes the entire process from the creation of the project of the front-end development task to the deployment of the business code developed in the front-end development task to the server, wherein M is an integer greater than 1; in response to the selection operation of each of the M controls, displaying the second user interaction interface of the current stage corresponding to the selected control, the second user interaction interface of the current stage is used to guide the user to perform the task development of the current stage; based on the user interaction operation in the second user interaction interface of the current stage, perform the task development of the current stage; and after the tasks of the M stages are all developed, feedback the information that the front-end development task is completed to the user.

[0006] According to an embodiment of the present disclosure, the M phases include at least one of a project creation phase, a dependency installation phase, a code generation phase, or a continuous deployment phase.

[0007] According to an embodiment of the present disclosure, the method is implemented using Electron technology. Then, the task development of the current stage based on the user interaction operation in the second user interaction interface of the current stage includes: calling a third-party tool to develop the task of the current stage; wherein, when the current stage is the project creation stage, the third-party tool includes a locally installed scaffolding tool; when the current stage is the dependency installation stage, the third-party tool includes a package manager npm tool; or when the current stage is the continuous deployment stage, the third-party tool includes a continuous deployment platform.

[0008] According to an embodiment of the present disclosure, the second user interaction interface of the project creation stage includes a directory selection area and a project initialization method selection control; wherein, based on the user interaction operation in the second user interaction interface of the project creation stage, the task development of the project creation stage includes: in response to the user's operation in the directory selection area, calling the local file system to select the root directory of the project for developing the front-end development task; and in response to the user's operation of selecting a project initialization method from the project initialization method selection control, creating a new project for developing the front-end development task under the root directory according to the project initialization method selected by the user.

[0009] According to an embodiment of the present disclosure, the project initialization mode selection control includes at least one of a create project button, a copy project button or a clone project button; wherein, creating a new project for developing the front-end development task in the root directory according to the project initialization mode selected by the user includes: when the user selects the create project button, calling the locally installed scaffolding tool to create the new project; when the user selects the copy project button, copying the local project file selected by the user to the root directory as the new project; or when the user selects the clone project button, calling the locally installed distributed version controller Git tool to pull the business code from the remote repository to the root directory as the new project, wherein the business code in the remote repository is the business code of other front-end development tasks waiting to be deployed to the server.

[0010] According to an embodiment of the present disclosure, the second user interaction interface of the dependency installation phase includes a file directory selection area and a dependency installation button; wherein, based on the user interaction operation in the second user interaction interface of the dependency installation phase, the task development of the dependency installation phase includes: based on the user's operation in the file directory selection area, calling the local file system so that the user uses the local file system to select the dependencies to be installed; and in response to the user's operation on the dependency installation button, calling the local package manager npm tool to execute the npm intall dependency installation command through the npm tool to perform dependency installation.

[0011] According to an embodiment of the present disclosure, the second user interaction interface in the dependency installation phase also includes a dependency list, and the dependency list is used to list information of all installed dependencies.

[0012] According to an embodiment of the present disclosure, the dependency list further includes an operation bar, and the operation bar is used to receive a user's update operation or delete operation on the dependency displayed in the dependency list.

[0013] According to an embodiment of the present disclosure, the second user interaction interface in the code generation phase includes a component selection area and a page splicing area, wherein the component selection area is integrated with at least one form component; wherein, based on the user interaction operation in the second user interaction interface in the code generation phase, the task development in the code generation phase includes: based on the user's dragging operation on the form component, dragging the form component selected by the user in the component selection area to the page splicing area to combine into a page style; and after the page style design is completed, generating the business code of the front-end development task based on the designed page style.

[0014] According to an embodiment of the present disclosure, the second user interaction interface in the continuous deployment stage includes a deployment information configuration control and a one-key deployment button; wherein, based on the user interaction operation in the second user interaction interface in the continuous deployment stage, the task development in the continuous deployment stage includes: receiving the user's user deployment configuration for the front-end development task through the deployment information configuration control; and in response to the user operating the one-key deployment button, calling the continuous deployment platform to deploy the business code of the front-end development task to the server according to the user deployment configuration.

[0015] According to an embodiment of the present disclosure, the method further includes: before the continuous deployment stage, when the business code of the front-end development task is developed, calling the local distributed version controller Git tool to push the business code of the front-end development task to the remote warehouse. Then calling the continuous deployment platform to deploy the business code of the front-end development task to the server according to the user deployment configuration includes: calling the code deployment interface provided by the continuous deployment platform to read the business code of the front-end development task from the remote warehouse through the continuous deployment platform, and deploying it to the server after packaging.

[0016] According to an embodiment of the present disclosure, deployment progress information is displayed to the user during the deployment process.

[0017] The second aspect of the disclosed embodiment provides a front-end development device. The device includes a user interaction module and a development module. The user interaction module is used to: display a first user interaction interface, the first user interaction interface includes M controls corresponding to the M stages included in the full process of the front-end development task, wherein the full process of the front-end development task includes the entire process from the project creation of the front-end development task to the deployment of the business code developed in the front-end development task to the server, wherein M is an integer greater than 1; in response to the selection operation of each of the M controls, display the second user interaction interface of the current stage corresponding to the selected control, the second user interaction interface of the current stage is used to guide the user to develop the task of the current stage; and after the tasks of the M stages are all developed, feedback the information that the front-end development task is completed to the user. The development module is used to develop the task of the current stage based on the user interaction operation in the second user interaction interface of the current stage.

[0018] According to an embodiment of the present disclosure, the development module includes a project creation module. The M stages include a project creation stage, and the second user interaction interface of the project creation stage includes a directory selection area and a project initialization mode selection control. The project creation module is used to call the local file system to select the root directory of the project for developing the front-end development task in response to the user's operation in the directory selection area; and in response to the user's operation of selecting a project initialization mode from the project initialization mode selection control, create a new project for developing the front-end development task under the root directory according to the project initialization mode selected by the user.

[0019] According to an embodiment of the present disclosure, the development module includes a dependency installation module. The M stages include a dependency installation stage, and the second user interaction interface of the dependency installation stage includes a file directory selection area and a dependency installation button. The dependency installation module is used to: based on the user's operation in the file directory selection area, call the local file system so that the user uses the local file system to select the dependency to be installed; and in response to the user's operation on the dependency installation button, call the local package manager npm tool to execute the npm install dependency installation command through the npm tool to perform dependency installation.

[0020] According to an embodiment of the present disclosure, the second user interaction interface in the dependency installation phase also includes a dependency list. The dependency installation module is also used to list information of all installed dependencies through the dependency list.

[0021] According to an embodiment of the present disclosure, the dependency list further includes an operation bar. The dependency installation module is further configured to receive, through the operation bar, an update operation or a delete operation of a dependency displayed in the dependency list by a user.

[0022] According to an embodiment of the present disclosure, the development module includes a code generator. The M stages include a code generation stage, and the second user interaction interface of the code generation stage includes a component selection area and a page splicing area, wherein the component selection area is integrated with at least one form component. The code generator is used to drag the form component selected by the user in the component selection area to the page splicing area based on the user's drag operation on the form component, and combine it into a page style; and after the page style design is completed, generate the business code of the front-end development task based on the designed page style.

[0023] According to an embodiment of the present disclosure, the development module includes a continuous deployment module. The M stages include a continuous deployment stage, and the second user interaction interface of the continuous deployment stage includes a deployment information configuration control and a one-key deployment button. The continuous deployment module is used to receive the user's user deployment configuration for the front-end development task through the deployment information configuration control; and in response to the user operating the one-key deployment button, call the continuous deployment platform to deploy the business code of the front-end development task to the server according to the user deployment configuration.

[0024] According to an embodiment of the present disclosure, the development module includes a code sharing module. The code sharing module is used to call the local distributed version controller Git tool to push the business code of the front-end development task to the remote warehouse before the continuous deployment stage after the business code of the front-end development task is developed. The continuous deployment module is used to call the code deployment interface provided by the continuous deployment platform to read the business code of the front-end development task from the remote warehouse through the continuous deployment platform, and deploy it to the server after packaging.

[0025] A third aspect of the embodiments of the present disclosure provides an electronic device, comprising: one or more processors, and one or more memories. The one or more memories are used to store one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors execute the above-mentioned front-end development method.

[0026] The fourth aspect of the embodiments of the present disclosure also provides a computer-readable storage medium on which executable instructions are stored, and when the instructions are executed by a processor, the processor executes the above-mentioned front-end development method.

[0027] The fifth aspect of the embodiments of the present disclosure also provides a computer program product, including a computer program, which implements the above-mentioned front-end development method when executed by a processor. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0029] Figure 1 The application scenario diagram of the front-end development method, apparatus, device, medium and program product according to the embodiment of the present disclosure is schematically shown;

[0030] Figure 2 A flowchart of a front-end development method according to an embodiment of the present disclosure is schematically shown;

[0031] Figure 3 An exemplary system architecture of a front-end development method according to an embodiment of the present disclosure is schematically shown;

[0032] Figure 4 A schematic diagram of a user interaction interface in a project creation phase according to an embodiment of the present disclosure is schematically shown;

[0033] Figure 5 A schematic diagram of a user interaction interface in a dependency installation phase according to an embodiment of the present disclosure is shown;

[0034] Figure 6A schematic diagram of a user interaction interface in a code generation phase according to an embodiment of the present disclosure is schematically shown;

[0035] Figure 7 A schematic diagram schematically shows a user interaction interface in the continuous deployment phase according to an embodiment of the present disclosure;

[0036] Figure 8 A user interaction sequence diagram in a front-end development method according to another embodiment of the present disclosure is schematically shown;

[0037] Fig. 9 A schematic diagram of a front-end development device according to an embodiment of the present disclosure is shown; and

[0038] Fig.10 A block diagram of an electronic device suitable for implementing the front-end interaction method according to an embodiment of the present disclosure is schematically shown. DETAILED DESCRIPTION

[0039] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the present disclosure. In the following detailed description, for ease of explanation, many specific details are set forth to provide a comprehensive understanding of the embodiments of the present disclosure. However, it is apparent that one or more embodiments may also be implemented without these specific details. In addition, in the following description, descriptions of known structures and technologies are omitted to avoid unnecessary confusion of the concepts of the present disclosure.

[0040] The terms used herein are only for describing specific embodiments and are not intended to limit the present disclosure. The terms "comprise", "include", etc. used herein indicate the existence of the features, steps, operations and / or components, but do not exclude the existence or addition of one or more other features, steps, operations or components.

[0041] All terms (including technical and scientific terms) used herein have the meanings commonly understood by those skilled in the art unless otherwise defined. It should be noted that the terms used herein should be interpreted as having a meaning consistent with the context of this specification and should not be interpreted in an idealized or overly rigid manner.

[0042] When using expressions such as "at least one of A, B, and C, etc.", they should generally be interpreted according to the meaning of the expression commonly understood by those skilled in the art (for example, "a system having at least one of A, B, and C" should include but is not limited to a system having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B, C, etc.).

[0043] It should be understood herein that any number of elements in the specification and drawings is for illustration rather than limitation, and any naming (eg, first, second) is only for distinction but not for limitation.

[0044] In response to the problem of constantly switching tools throughout the entire front-end development process, the embodiments of the present disclosure provide a front-end development method, apparatus, equipment, medium and program that can achieve automated management of the entire life cycle of the front-end development process, allowing developers to achieve full-process visual operations of front-end development tasks in an automated tool.

[0045] The front-end development method implemented according to the present disclosure can be implemented through the following process. First, a first user interaction interface is displayed, and the first user interaction interface includes M controls corresponding to the M stages included in the full process of the front-end development task, wherein the full process of the front-end development task includes the entire process from project creation of the front-end development task to deployment of the business code developed in the front-end development task to the server, wherein M is an integer greater than 1. Then, in response to the selection operation of each of the M controls, the second user interaction interface of the current stage corresponding to the selected control is displayed, and the second user interaction interface of the current stage is used to guide the user to perform task development in the current stage. Next, based on the user interaction operation in the second user interaction interface of the current stage, the task development of the current stage is performed. Finally, after the tasks of the M stages are all developed, the information on the completion of the development of the front-end development task is fed back to the user.

[0046] According to the embodiments of the present disclosure, developers can be guided to perform the full-process development of front-end development tasks through the M controls in the first user interaction interface, and developers can be guided to implement the specific development tasks of each stage through the second user interaction interface of each stage, and the development completion information can be fed back to the user after the tasks of the M stages are completed. In this way, full-process automated management of front-end development tasks can be achieved, the development process can be guided, the operations in the front-end development process can be simplified, the switching between different tools can be avoided, and the front-end development efficiency can be effectively improved.

[0047] It should be noted that the front-end development methods, devices, equipment, media and programs determined in the embodiments of the present disclosure can be used in the financial field (for example, applications in Internet finance) and can also be used in any field other than the financial field. The present disclosure does not limit the application field.

[0048] Figure 1 The application scenario diagram of the front-end development method, apparatus, device, medium and program product according to the embodiment of the present disclosure is schematically shown; It should be noted that, Figure 1What is shown is merely an example of a system architecture to which the embodiments of the present disclosure can be applied, in order to help those skilled in the art understand the technical content of the present disclosure, but it does not mean that the embodiments of the present disclosure cannot be used in other devices, systems, environments or scenarios.

[0049] like Figure 1 As shown, the application scenario 100 according to this embodiment may include a terminal device 101, a network 102 and a server 103. The network 102 is used to provide a communication link between the terminal device 101 and the server 103. The network 102 may include various connection types, such as wired, wireless communication links or optical fiber cables, etc.

[0050] Developer 1 can use terminal device 101 to develop front-end business code, and the completed business code is deployed to server 103.

[0051] In some embodiments, the application scenario 100 may further include a continuous deployment platform 104 and a remote warehouse 105. The continuous deployment platform 104 and the remote warehouse 105 may be connected to the network 102 respectively, and may communicate with the terminal device 101 and the server 103 through the network 102.

[0052] The continuous deployment platform 104 can perform specific code deployment operations. For example, the continuous deployment platform 104 can accept the call of the terminal device 101 to perform specific code deployment operations, and finally deploy the business code developed by the developer in the terminal device 101 to the server 103.

[0053] The remote warehouse 105 is a code hosting platform. In some embodiments, during the front-end development process, the front-end business code developed by the developer using the terminal device 101 can be submitted to the remote warehouse 105. For example, the front-end code can be submitted to the remote warehouse 105 through the distributed version controller Git tool (referred to as Git tool) installed locally in the terminal device 101, wherein the remote warehouse 105 can be connected to the git tool in the terminal device 101, wherein the Git tool can push local files to the remote warehouse 105.

[0054] Thus, after receiving the call or deployment instruction from the terminal device 101, the continuous deployment platform 104 can read the business code from the remote warehouse 105 and deploy the read business code to the server 103. In some embodiments, the continuous deployment platform 104 can be a DOS system platform.

[0055] The method of the embodiment of the present disclosure may be performed by the terminal device 101. For example, the terminal device 101 may be provided with a device, software program, medium or electronic device for implementing the front-end development method of the embodiment of the present disclosure, and the developer may implement the front-end development by operating in the terminal device 101.

[0056] Taking the application program installed in the terminal device 101 that can execute the front-end development method of the embodiment of the present disclosure as an example, the development scenario of the developer is described as follows. For example, the developer 1 can open the application program in the terminal device 101, and carry out the full process development of the front end according to the interactive guidance of the user interaction interface (including the first user interaction interface and the second user interaction interface of each stage) of the application program. Among them, in the development process of each stage, the application program 101 can realize the full process development of the front-end development task based on the user operation instruction, through its own integrated functions, or by calling the locally installed third-party tools, or calling the continuous deployment platform 104, etc. In the whole process, the developer does not need to switch tools, wherein the logic of calling the third-party tools or other platforms can be realized by the internal processing logic of the application program. Thus, the user can carry out the full process development of the front end only by operating in the application program. Moreover, the user interaction interface that can guide the development operation provided by the application program can greatly simplify the operation in the development process and improve the development efficiency.

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

[0058] The following will be based on Figure 1 The scene described by Figure 2~Figure 8 The front-end development method of the disclosed embodiment is described in detail.

[0059] Figure 2 The flowchart of the front-end development method according to an embodiment of the present disclosure is schematically shown.

[0060] like Figure 2 As shown, the front-end development method according to this embodiment may include operations S210 to S240.

[0061] In operation S210, a first user interaction interface is displayed, and the first user interaction interface includes M controls corresponding to the M stages included in the full process of the front-end development task. The full process of the front-end development task includes the entire process from project creation of the front-end development task to deployment of the business code developed in the front-end development task to the server, where M is an integer greater than 1.

[0062] The M stages included in the entire process of the front-end development task can be divided according to actual needs, wherein the M stages can be parallel, serial, or a mixture of partially parallel and partially serial, which is not limited in this disclosure.

[0063] In operation S220, in response to a selection operation on each of the M controls, a second user interaction interface of the current stage corresponding to the selected control is displayed, and the second user interaction interface of the current stage is used to guide the user to perform task development of the current stage.

[0064] In operation S230, based on the user interaction operation in the second user interaction interface of the current stage, the task development of the current stage is performed. In the task development process of each stage, the corresponding functions can be executed based on the user operation. Among them, these functions can be implemented by pre-integrated functions, or by calling with the operating system or a third-party tool.

[0065] In operation S240, after the tasks of the M stages are all developed, information on the completion of the front-end development task is fed back to the user. The information on the completion of the front-end development task can be a notification message notifying the user of the completion of the development, or can be the deployment information of the front-end task on the server, or can be a summary record information of the front-end task development process, etc.

[0066] In this way, the disclosed embodiments can achieve full-process automated management of front-end development tasks, guide the development process, simplify operations during the front-end development process, avoid switching between different tools, and effectively improve front-end development efficiency.

[0067] Figure 3 An exemplary system architecture of a front-end development method according to an embodiment of the present disclosure is schematically shown.

[0068] like Figure 3 As shown, according to this embodiment, the front-end development method is implemented using Electron technology. Electron is a cross-platform desktop GUI application development framework based on Web front-end technology. Electron can call scaffolding tools, Git tools, and npm tools to create projects, install dependencies, and pull and push business codes to remote repositories. Electron can also interact with the operating system, such as opening the file system to create a directory. Electron can also perform operations such as reading, deleting, copying, and modifying local files.

[0069] In the method of the embodiment of the present disclosure, the user interaction interface 310 can be developed using Electron technology, and the user interaction interface 310 can provide the first user interaction interface of the embodiment of the present disclosure and the second user interaction interface at each stage. The user interaction interface 310 can guide developers to advance front-end development on the one hand, and on the other hand, can receive user interaction operations, generate corresponding operation instructions in response to the user interaction operations, and then transmit the operation instructions to the processing logic 320 developed based on Electron technology.

[0070] Combination Figure 3 In one embodiment, the M stages of the front-end development task may include at least one of a project creation stage, a dependency installation stage, a code generation stage, or a continuous deployment stage. Figure 3 The illustration of all four stages is only for illustration purposes. In actual applications, the stages may be set, merged, or replaced as needed.

[0071] According to some embodiments of the present disclosure, when developing tasks in some stages, third-party tools may be called to implement the tasks. For example, when developing tasks in the project creation stage, project creation may be performed by calling a locally installed scaffolding tool 331. Or, for example, when developing tasks in the dependency installation stage, front-end dependencies may be installed by calling the package manager npm tool 332. Or, for another example, when performing tasks in the continuous deployment stage, a continuous deployment platform 335 may be called to perform specific deployment tasks.

[0072] According to other embodiments of the present disclosure, when developing tasks at some stages, it can also be achieved by developing integrated corresponding functions using Electron technology. For example, a code development environment can be developed using Electron technology to develop and debug code. In some embodiments, an integrated code generator can be developed using Electron technology, and the code generator can have some Form form components, which can be used to quickly design Form form components in the front-end page by dragging and dropping.

[0073] According to other embodiments of the present disclosure, after the code is generated in the code generation phase, it can be submitted to the remote repository 334. For example, after the code generation is completed in the code generation phase, the Git tool 333 can be called to push the locally developed business code to the remote repository 334. In this way, the continuous deployment platform 335 can read the code from the remote repository 334 after being called in the continuous deployment phase.

[0074] According to some embodiments of the present disclosure, during the project creation phase, the Git tool 333 may be used to pull code from the business code shared in the remote repository to the local repository, so as to create a project.

[0075] Figure 4 A schematic diagram of a user interaction interface in a project creation phase according to an embodiment of the present disclosure is schematically shown.

[0076] like Figure 4 As shown, the user interaction interface 400 includes a first user interaction interface 410 and a second user interaction interface 420 in the project creation stage.

[0077] In this embodiment, the first user interaction interface 410 is located on the left side of the interface, wherein a project creation button, a dependency installation button, a code generation button, and a continuous deployment button are displayed in the first user interaction interface 410. In the first user interaction interface 410, the project creation button is in a selected state, and accordingly, a second user interaction interface 420 of the project creation stage is displayed on the right side of the user interaction interface 400.

[0078] The second user interaction interface 420 in the project creation stage includes a directory selection area 421 and a project initialization mode selection control 422 .

[0079] In one embodiment, the project initialization mode selection control 422 may include at least one of a create project button, a copy project button, or a clone project button ( Figure 4 All three buttons are shown schematically in FIG.

[0080] In the directory selection area 421, directory selection, project directory information display, directory creation controls, etc. can be set as needed. Different controls can interact in different ways. For example, clicking on the directory selection control can provide a pop-up to allow the user to select directory information, etc.

[0081] Combination Figure 4 In operation S230, when developing tasks in the project creation phase, the local file system may be called to select a root directory of a project for developing a front-end development task in response to the user's operation in the directory selection area 421. Then, in response to the user's operation of selecting a project initialization method from the project initialization method selection control, a new project for developing a front-end development task may be created in the root directory according to the project initialization method selected by the user.

[0082] Different project initialization methods can trigger different project creation logic. For example, when the user selects the Create Project button, the locally installed scaffolding tool can be called to create a new project. For another example, when the user selects the Copy Project button, the local project file selected by the user is copied to the root directory as a new project. For another example, when the user selects the Clone Project button, the locally installed distributed version controller Git tool is called to pull the business code from the remote repository to the root directory as a new project, where the business code in the remote repository is the business code of other front-end development tasks waiting to be deployed to the server.

[0083] Figure 5 A schematic diagram of a user interaction interface in a dependency installation phase according to an embodiment of the present disclosure is schematically shown.

[0084] like Figure 5 As shown, the user interaction interface 500 includes a first user interaction interface 510 and a second user interaction interface 520 depending on the installation stage.

[0085] In this embodiment, the first user interaction interface 510 is located on the left side of the interface, wherein a project creation button, a dependency installation button, a code generation button, and a continuous deployment button are displayed in the first user interaction interface 510. The dependency installation button is in a selected state in the first user interaction interface 510, and accordingly, a second user interaction interface 520 of the dependency installation stage is displayed on the right side of the user interaction interface 500.

[0086] The second user interaction interface 520 in the dependency installation phase may include a file directory selection area 521 and a dependency installation button 522. The file directory selection area 521 may include a directory selection control, etc., and dependent files etc. that need to be installed in the front-end development task may be selected according to the user's operation.

[0087] Combination Figure 5 In operation S230, when developing tasks in the dependency installation phase, the local file system can be called based on the user's operation in the file directory selection area 521, so that the user can use the local file system to select the dependencies to be installed, and then in response to the user's operation on the dependency installation button 522, the local package manager npm tool is called to execute the npm install dependency installation command through the npm tool to perform dependency installation.

[0088] In some embodiments, the second user interaction interface 520 may further include a dependency list 523. The dependency list 523 may list information of all installed dependencies, such as the name and / or version of the dependency, etc. This can help developers to view and confirm the installation status of the dependency.

[0089] Furthermore, according to some embodiments of the present disclosure, the dependency list 523 may further include an operation bar 5231. The operation bar 5231 is used to receive a user's update operation or delete operation on the dependency displayed in the dependency list, so as to facilitate the developer to manage the dependency, for example, update the dependency version, or delete unnecessary dependency or low-version dependency, etc.

[0090] The embodiment of the present disclosure can provide visual management of dependencies through the dependency list 523. Compared with the non-visualization of the dependency installation process in the prior art, the embodiment of the present disclosure can effectively provide dependency management functions and improve front-end development efficiency.

[0091] Figure 6 The following schematically shows a user interaction interface diagram in the code generation stage according to an embodiment of the present disclosure.

[0092] like Figure 6 As shown, the user interaction interface 600 includes a first user interaction interface 610 and a second user interaction interface 620 in the code generation stage.

[0093] In this embodiment, the first user interaction interface 610 is located on the left side of the interface, wherein a project creation button, a dependency installation button, a code generation button, and a continuous deployment button are displayed in the first user interaction interface 610. The code generation button is in a selected state in the first user interaction interface 610, and accordingly, a second user interaction interface 620 of the code generation stage is displayed on the right side of the user interaction interface 600.

[0094] According to an embodiment of the present disclosure, the second user interaction interface 620 in the code generation phase may include a component selection area 621 and a page stitching area 622 , wherein at least one form component (eg, a form component) is integrated in the component selection area 621 .

[0095] Therefore, in operation S230, when developing tasks in the code generation phase, the form component selected by the user in the component selection area 621 can be dragged to the page splicing area 622 by dragging the form component to form a page style. Then, after the page style design is completed, the business code of the front-end development task can be generated based on the designed page style according to the user's instructions.

[0096] The component selection area 621 and the page stitching area 622 may be code generation functions (eg, code generators) developed using Electron, which can help developers quickly design web pages, increase the reuse rate of common codes, and improve front-end development efficiency.

[0097] Of course, it is understandable Figure 6The content in the second user interaction interface 620 in the code generation stage is only exemplary. In some embodiments, the second user interaction interface 620 in the code generation stage can provide a code development environment, which can include tools such as a code editor, a compiler, a debugger and / or a graphical user interface, and the developer can edit and debug the code as needed.

[0098] Figure 7 A schematic diagram schematically shows a user interaction interface in the continuous deployment phase according to an embodiment of the present disclosure.

[0099] like Figure 7 As shown, the user interaction interface 700 includes a second user interaction interface 720 in a continuous deployment phase of the first user interaction interface 710 .

[0100] In this embodiment, the first user interaction interface 710 is located on the left side of the interface, wherein a project creation button, a dependency installation button, a code generation button, and a continuous deployment button are displayed in the first user interaction interface 710. The continuous deployment button is in a selected state in the first user interaction interface 710, and accordingly, a second user interaction interface 720 of the continuous deployment stage is displayed on the right side of the user interaction interface 700.

[0101] The second user interaction interface 720 in the continuous deployment phase may include a deployment information configuration control 721 and a one-click deployment button 722. The deployment information configuration control 721 may include, for example, a file selection area, an environment selection drop-down box, or a branch selection drop-down box, where different controls are used to set configuration information of different dimensions.

[0102] Therefore, in operation S230, when developing tasks in the continuous deployment phase, the user deployment configuration of the front-end development task can be received by the deployment information configuration control 721, and then in response to the user operating the one-key deployment button 722, the continuous deployment platform is called to deploy the business code of the front-end development task to the server according to the user deployment configuration.

[0103] According to some embodiments of the present disclosure, the continuous deployment platform can read code from a remote repository when performing code deployment. Thus, before the continuous deployment phase, after the business code development of the front-end development task is completed, the local distributed version controller Git tool can be called to push the business code of the front-end development task to the remote repository. In one embodiment, the submission of code to the remote repository can be triggered at the same time as the code generation is completed in the code generation phase. In other embodiments, a code submission phase can be added between the code generation phase and the continuous deployment phase, and then the developer is prompted to submit the code in the code submission phase. Thus, after the user operates the one-key deployment button 722, the code deployment interface provided by the continuous deployment platform is called to read the business code of the front-end development task from the remote warehouse through the continuous deployment platform, and package it and deploy it to the server.

[0104] According to an embodiment of the present disclosure, deployment progress information may also be displayed to the user in the second user interaction interface 720 during the deployment process.

[0105] Figure 8 The user interaction sequence diagram in the front-end development method according to another embodiment of the present disclosure is schematically shown.

[0106] Combination Figure 8 According to the embodiment of the present disclosure, an automation tool 801 for the full process development of front-end tasks can be developed based on Electron technology to implement the front-end development method of the embodiment of the present disclosure. Among them, the automation tool 801 can integrate four core functional modules, namely project creation, dependency installation, code generation and continuous deployment. Developers can complete the full life cycle automation management of the entire R&D process through visual operations in the automation tool 801, which reduces the complexity of the development process and does not require switching various tools, greatly improving R&D efficiency.

[0107] Specifically, Figure 8 The user interaction sequence diagram of the automation tool 801 shown may include steps S1 to S10. The user interaction interface of the automation tool 801 in each stage of project creation, dependency installation, code generation and continuous deployment can refer to Figure 4~Figure 7 .

[0108] First, in step S1, select the file directory to initialize the project. The developer clicks the Create Project button on the left menu bar, and the file directory selection area and the Create Project, Copy Project, and Clone Project buttons appear on the right interface (refer to Figure 4 ). In the first step, the automation tool 801 uses Electron to call the local file system to select the root directory of the new project to be generated. In the second step, a new project is created by clicking one of the three buttons: Create Project, Copy Project, or Clone Project.

[0109] Creating a project, copying a project, and cloning a project are three different ways to create a new project. Among them, click the Create a New Project button, and a new project configuration information pop-up window will appear. You can enter the project name, project description, etc. You can also choose project templates of different styles. After clicking OK, the automation tool 801 calls the scaffolding tool integrated in the tool to execute the project creation command and generate a new project in the file directory selected in the first step. Click the Copy button, and a project directory selection pop-up window will appear. Select the project you want to copy. After clicking OK, the automation tool 801 reads and copies the project to the local file directory selected in the first step as a new project through Electron. Click Clone a New Project, and a clone project information pop-up window will appear. You can enter the address and branch name of the remote repository connected to the project through the Git tool. Click OK, and the automation tool 801 can call the locally globally installed Git tool to execute the code cloning command and pull the corresponding code to the file directory selected in the first step as a new project.

[0110] Then, in step S2, when the project initialization is completed, information indicating that the project initialization is completed can be fed back to the user.

[0111] Next, in step S3, install dependencies. After the project is initialized, click the dependency installation button on the left menu bar, and the file directory selection area, one-click installation button and dependency list will appear on the right interface (refer to Figure 5 ). Developers can use the automation tool 801 to call the local file system through Electron to select the project to install dependencies. Then click the one-click installation button, and the automation tool 801 calls the npm tool installed locally and globally, executes the npm install dependency installation command, and installs the dependencies of the project.

[0112] The dependency list is a dependency management tool provided by the automation tool 801. After the project dependency is installed with one click, all installed runtime dependencies and development dependencies will be displayed in the dependency list. The right side of the dependency list is the operation bar. Dependencies can be managed through the operation bar. For example, if you select a version of an installed dependency and click Install, the automation tool 801 will execute the npmintall xxx@version dependency installation command to update the version of the installed dependency, or click the Delete button, the automation tool 801 will execute the npm unintall command to delete the dependency.

[0113] Then, in step S4, information indicating that the dependency installation is complete is fed back to the user.

[0114] Next, in step S5, after the dependencies are installed, you can directly open the project in the automation tool 801 to start code development. The automation tool 801 can provide a code generator. Click the code generator button on the left menu bar, and the component selection area and page splicing area will appear on the right interface (refer to Figure 6 ). The automation tool 801 code generator integrates a simple Form component implemented by Electron. Developers can drag the components to the page splicing area to combine them into the page style we want to develop. Finally, click the code generation button, a file selector pops up, select the code save path, and click the OK button to generate the business code that we can use directly in the corresponding directory.

[0115] Then in step S6, based on the developer's confirmation operation, it is determined that the code development is completed.

[0116] Next, in step S7, the code is submitted to the remote repository. After the code development is completed, the Git command is executed through the command line tool integrated in the automation tool 801 to submit the code to the remote repository.

[0117] Then, in step S8, information indicating that the code submission is completed is fed back to the user.

[0118] Next, in step S9, continuous deployment. After the code is submitted, click the Continuous Deployment button in the left menu bar. The right interface will display the file selection area, environment selection drop-down box, branch selection drop-down box, and one-click deployment button (refer to Figure 7 ). Developers can use the automation tool 801 to call the local file system through Electron to select the project we want to deploy, select the environment and branch, click one-click deployment, and the automation tool 801 will call the code deployment API provided by the continuous deployment platform to package the code and upload it to the target server to complete the deployment operation. The continuous deployment platform can be a DOS platform, for example. In the prior art, since the front-end development tasks are executed in different tools in a decentralized manner, developers generally do not have the authority to log in to the DOS platform for code deployment, and usually need to notify limited personnel to log in to the DOS platform for code packaging and deployment operations, which is extremely inefficient. In contrast, in the present application scheme, the logic of the automation tool 801 calling the continuous deployment platform DOS platform is encapsulated as the back-end logic. Developers can call the DOS platform to deploy the code through the trigger operation in the automation tool 801, thereby improving the deployment efficiency.

[0119] Then in step S10, after the deployment is completed, the automation tool 801 feeds back the developer specific deployment information, and the process ends.

[0120] The front-end development method of the disclosed embodiment can enable developers to implement full-process visual operations from project creation, dependency installation, code development, code packaging to continuous deployment in the automation tool 801.

[0121] Moreover, through visual operation, the operation process of front-end development tasks can be streamlined and the operation complexity can be reduced. Developers can obtain process progress information in real time, control the R&D progress at all times, and realize the automated management of the entire life cycle of the R&D process.

[0122] At the same time, by providing functions such as project cloning, dependency management, and code generator, it improves project reusability, solves the problem of dependency version incompatibility, reduces the amount of development code, and improves R&D efficiency.

[0123] Fig. 9 The structural block diagram of a front-end development device 900 according to an embodiment of the present disclosure is schematically shown.

[0124] like Fig. 9 As shown, the front-end development device 900 according to this embodiment may include a user interaction module 910 and a development module 920 .

[0125] The user interaction module 910 may be used to provide a user interaction interface in the front-end development task, receive user interaction operations, and feedback the results of the interaction operations to the user. According to an embodiment of the present disclosure, the user interaction module 910 may be used to perform operations S210, S220, and S240, for example.

[0126] Specifically, the user interaction module 910 can be used to display a first user interaction interface, wherein the first user interaction interface includes M controls corresponding one-to-one to the M stages included in the full process of the front-end development task, wherein the full process of the front-end development task includes the entire process from project creation of the front-end development task to deployment of the business code developed in the front-end development task to the server, wherein M is an integer greater than 1.

[0127] Furthermore, the user interaction module 910 can also be used to respond to the selection operation of each of the M controls and display the second user interaction interface of the current stage corresponding to the selected control, and the second user interaction interface of the current stage is used to guide the user to carry out task development in the current stage.

[0128] Furthermore, the user interaction module 910 can also be used to provide feedback to the user on the completion of the front-end development task after the tasks in the M stages are completed.

[0129] The development module 920 may be used to develop tasks in the current phase based on the user interaction operation in the second user interaction interface in the current phase. According to an embodiment of the present disclosure, the development module 920 may, for example, perform operation S230.

[0130] According to some embodiments of the present disclosure, the M stages included in the full process of the front-end development task may include at least one of a project creation stage, a dependency installation stage, a code generation stage, or a continuous deployment stage. Accordingly, the development module 920 may include at least one of a project creation module 921, a dependency installation module 922, a code generator 923, or a continuous deployment module 924.

[0131] During the project creation phase, the second user interface includes a directory selection area and a project initialization method selection control (see Figure 4 ). The project creation module 921 can be used to call the local file system to select the root directory of the project for developing the front-end development task in response to the user's operation in the directory selection area; and in response to the user's operation of selecting a project initialization method from the project initialization method selection control, create a new project for developing the front-end development task in the root directory according to the project initialization method selected by the user.

[0132] During the dependency installation phase, the second user interface may include a file directory selection area and a dependency installation button (see Figure 5 ). The dependency installation module 922 can be used to: based on the user's operation in the file directory selection area, call the local file system so that the user can use the local file system to select the dependencies to be installed; and in response to the user's operation on the dependency installation button, call the local package manager npm tool to execute the npm install dependency installation command through the npm tool to install the dependencies.

[0133] According to another embodiment of the present disclosure, the second user interaction interface in the dependency installation phase also includes a dependency list (refer to Figure 5 ). The dependency installation module 922 may also be used to list information of all installed dependencies through a dependency list. According to another embodiment of the present disclosure, the dependency list also includes an operation bar. The dependency installation module 922 may also be used to receive an update operation or a delete operation of a dependency displayed in the dependency list by a user through the operation bar.

[0134] In the code generation stage, the second user interaction interface includes a component selection area and a page splicing area (reference Figure 6), wherein the component selection area is integrated with at least one form component. The code generator 923 is used to drag the form component selected by the user in the component selection area to the page splicing area based on the user's drag operation on the form component in the code generation stage to combine into a page style; and after the page style design is completed, generate the business code of the front-end development task based on the designed page style.

[0135] In the continuous deployment phase, the second user interface includes a deployment information configuration control and a one-click deployment button (reference Figure 7 ). The continuous deployment module 924 can be used to receive the user deployment configuration of the front-end development task through the deployment information configuration control; and in response to the user operating the one-key deployment button, call the continuous deployment platform to deploy the business code of the front-end development task to the server according to the user deployment configuration.

[0136] According to other embodiments of the present disclosure, the development module 920 may also include a code sharing module. The code sharing module may be used to call the local distributed version controller Git tool to push the business code of the front-end development task to the remote warehouse after the business code of the front-end development task is developed before the continuous deployment phase. Thus, the continuous deployment module 924 may be used to call the code deployment interface provided by the continuous deployment platform to read the business code of the front-end development task from the remote warehouse through the continuous deployment platform, and deploy it to the server after packaging.

[0137] According to an embodiment of the present disclosure, the front-end development device 900 can be used to implement reference Figure 2~Figure 8 The front-end development method described provides a full-process, automated management platform for front-end development, reduces the complexity of the front-end development process, and does not require users to switch between various tools, thereby improving the efficiency of front-end development.

[0138] According to an embodiment of the present disclosure, any multiple modules in the user interaction module 910, the project creation module 921, the dependency installation module 922, the code generator 923, the continuous deployment module 924, or the code sharing module can be combined in one module for implementation, or any one of the modules can be split into multiple modules. Alternatively, at least part of the functions of one or more of these modules can be combined with at least part of the functions of other modules and implemented in one module. According to an embodiment of the present disclosure, at least one of the user interaction module 910, the project creation module 921, the dependency installation module 922, the code generator 923, the continuous deployment module 924, or the code sharing module can be at least partially implemented 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 can be implemented by hardware or firmware such as any other reasonable way of integrating or packaging the circuit, or implemented in any one of the three implementation methods of software, hardware, and firmware or in an appropriate combination of any of them. Alternatively, at least one of the user interaction module 910, the project creation module 921, the dependency installation module 922, the code generator 923, the continuous deployment module 924, or the code sharing module may be at least partially implemented as a computer program module, which may perform corresponding functions when executed.

[0139] Fig.10 A block diagram of an electronic device 1000 suitable for implementing the front-end interaction method according to an embodiment of the present disclosure is schematically shown.

[0140] like Fig.10 As shown, the electronic device 1000 according to an embodiment of the present disclosure includes a processor 1001, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1002 or a program loaded from a storage part 1008 to a random access memory (RAM) 1003. The processor 1001 may include, for example, a general-purpose microprocessor (such as a CPU), an instruction set processor and / or a related chipset and / or a special-purpose microprocessor (for example, an application-specific integrated circuit (ASIC)), etc. The processor 1001 may also include an onboard memory for caching purposes. The processor 1001 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0141] In RAM 1003, various programs and data required for the operation of electronic device 1000 are stored. Processor 1001, ROM 1002 and RAM 1003 are connected to each other via bus 1004. Processor 1001 performs various operations of the method flow according to the embodiment of the present disclosure by executing the program in ROM 1002 and / or RAM 1003. It should be noted that the program can also be stored in one or more memories other than ROM 1002 and RAM 1003. Processor 1001 can also perform various operations of the method flow according to the embodiment of the present disclosure by executing the program stored in the one or more memories.

[0142] According to an embodiment of the present disclosure, the electronic device 1000 may further include an input / output (I / O) interface 1005, which is also connected to the bus 1004. The electronic device 1000 may further include one or more of the following components connected to the I / O interface 1005: an input portion 1006 including a keyboard, a mouse, etc.; an output portion 1007 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage portion 1008 including a hard disk, etc.; and a communication portion 1009 including a network interface card such as a LAN card, a modem, etc. The communication portion 1009 performs communication processing via a network such as the Internet. A drive 1010 is also connected to the I / O interface 1005 as needed. A removable medium 1011, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 1010 as needed, so that a computer program read therefrom is installed into the storage portion 1008 as needed.

[0143] The present disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or may exist independently without being assembled into the device / apparatus / system. The above computer-readable storage medium carries one or more programs, and when the above one or more programs are executed, the method according to the embodiment of the present disclosure is implemented.

[0144] According to an embodiment of the present disclosure, a computer-readable storage medium may be a non-volatile computer-readable storage medium, for example, may include but is not limited to: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by or in combination with an instruction execution system, an apparatus, or a device. For example, according to an embodiment of the present disclosure, a computer-readable storage medium may include the ROM 1002 and / or RAM 1003 described above and / or one or more memories other than ROM 1002 and RAM 1003.

[0145] The embodiment of the present disclosure also includes a computer program product, which includes a computer program, and the computer program contains program code for executing the method shown in the flowchart. When the computer program product is run in a computer system, the program code is used to enable the computer system to implement the front-end development method provided by the embodiment of the present disclosure.

[0146] The above functions defined in the system / device of the embodiment of the present disclosure are performed when the computer program is executed by the processor 1001. According to the embodiment of the present disclosure, the system, device, module, unit, etc. described above can be implemented by a computer program module.

[0147] In one embodiment, the computer program may rely on tangible storage media such as optical storage devices, magnetic storage devices, etc. In another embodiment, the computer program may also be transmitted and distributed in the form of signals on a network medium, and downloaded and installed through the communication part 1009, and / or installed from the removable medium 1011. The program code contained in the computer program may be transmitted using any appropriate network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0148] In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 1009, and / or installed from the removable medium 1011. When the computer program is executed by the processor 1001, the above functions defined in the system of the embodiment of the present disclosure are performed. According to the embodiment of the present disclosure, the system, device, means, module, unit, etc. described above can be implemented by a computer program module.

[0149] According to an embodiment of the present disclosure, the program code for executing the computer program provided by the embodiment of the present disclosure can be written in any combination of one or more programming languages. Specifically, these computing programs can be implemented using high-level process and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, Java, C++, python, "C" language or similar programming languages. The program code can be executed entirely on the user computing device, partially on the user device, partially on the remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device can be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computing device (for example, using an Internet service provider to connect through the Internet).

[0150] The flow charts and block diagrams in the accompanying drawings illustrate the possible architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each box in the flow chart or block diagram can represent a module, a program segment, or a part of a code, and the above-mentioned module, program segment, or a part of a code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flow chart, and the combination of the boxes in the block diagram or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0151] It will be appreciated by those skilled in the art that the features described in the various embodiments and / or claims of the present disclosure may be combined and / or combined in a variety of ways, even if such combinations and / or combinations are not explicitly described in the present disclosure. In particular, the features described in the various embodiments and / or claims of the present disclosure may be combined and / or combined in a variety of ways without departing from the spirit and teachings of the present disclosure. All of these combinations and / or combinations fall within the scope of the present disclosure.

[0152] The embodiments of the present disclosure are described above. However, these embodiments are only for illustrative purposes and are not intended to limit the scope of the present disclosure. Although the embodiments are described above separately, this does not mean that the measures in the various embodiments cannot be used in combination to advantage. The scope of the present disclosure is defined by the attached claims and their equivalents. Without departing from the scope of the present disclosure, those skilled in the art may make a variety of substitutions and modifications, which should all fall within the scope of the present disclosure.

Claims

1. A front-end development method, the method is implemented using Electron technology, wherein: The method comprises: Displaying a first user interaction interface, wherein the first user interaction interface includes M controls corresponding to the M stages included in the full process of the front-end development task, wherein the full process of the front-end development task includes the entire process from project creation of the front-end development task to deployment of the business code developed in the front-end development task to the server, wherein M is an integer greater than 1; In response to a selection operation on each of the M controls, displaying a second user interaction interface of the current stage corresponding to the selected control, wherein the second user interaction interface of the current stage is used to guide the user to perform task development of the current stage; Based on the user interaction operation in the second user interaction interface of the current stage, calling a third-party tool to perform task development of the current stage; and After the tasks of the M stages are all developed, feedback to the user on the completion of the front-end development task; The M phases include a project creation phase, a dependency installation phase, a code generation phase, and a continuous deployment phase; The second user interaction interface in the project creation phase includes a directory selection area and a project initialization mode selection control; The second user interaction interface in the dependency installation phase includes a file directory selection area and a dependency installation button; The second user interaction interface in the code generation phase includes a component selection area and a page splicing area; wherein the component selection area is integrated with at least one form component; The second user interaction interface in the continuous deployment phase includes a deployment information configuration control and a one-key deployment button.

2. The method according to claim 1, wherein: When the current stage is the project creation stage, the third-party tool includes a locally installed scaffolding tool; When the current stage is the dependency installation stage, the third-party tool includes a package manager npm tool; or When the current stage is the continuous deployment stage, the third-party tool includes a continuous deployment platform.

3. The method according to claim 1, wherein: Based on the user interaction operation in the second user interaction interface in the project creation stage, developing tasks in the project creation stage includes: In response to the user's operation in the directory selection area, calling the local file system to select a root directory of a project for developing the front-end development task; and In response to the user selecting a project initialization method from the project initialization method selection control, a new project for developing the front-end development task is created under the root directory according to the project initialization method selected by the user.

4. The method according to claim 3, wherein: The project initialization mode selection control includes at least one of a create project button, a copy project button, or a clone project button; wherein, creating a new project for developing the front-end development task in the root directory according to the project initialization mode selected by the user includes: When the user selects the create project button, the locally installed scaffolding tool is called to create the new project; When the user selects the copy project button, the local project file selected by the user is copied to the root directory to serve as the new project; or When the user selects the Clone Project button, the locally installed distributed version controller Git tool is called to pull the business code from the remote repository to the root directory as the new project, wherein the business code in the remote repository is the business code of other front-end development tasks waiting to be deployed to the server.

5. The method according to claim 1, wherein: Based on the user interaction operation in the second user interaction interface in the dependency installation phase, performing task development in the dependency installation phase includes: Based on the user's operation in the file directory selection area, calling the local file system so that the user uses the local file system to select the dependency to be installed; and In response to the user's operation on the dependency installation button, the local package manager npm tool is called to execute the npm install dependency installation command through the npm tool to perform dependency installation.

6. The method according to claim 5, wherein: The second user interaction interface in the dependency installation phase also includes a dependency list, which is used to list information of all installed dependencies.

7. The method according to claim 6, wherein: The dependency list further includes an operation bar, and the operation bar is used to receive a user's update operation or delete operation on the dependency displayed in the dependency list.

8. The method according to claim 1, wherein: Based on the user interaction operation in the second user interaction interface in the code generation stage, performing task development in the code generation stage includes: Based on the user's dragging operation on the form component, dragging the form component selected by the user in the component selection area to the page splicing area to combine into a page style; and After the page style design is completed, the business code of the front-end development task is generated based on the designed page style.

9. The method according to claim 1, wherein: Based on the user interaction operation in the second user interaction interface in the continuous deployment stage, performing task development in the continuous deployment stage includes: Receiving, through the deployment information configuration control, a user deployment configuration of the front-end development task by the user; and In response to the user operating the one-key deployment button, the continuous deployment platform is called to deploy the business code of the front-end development task to the server according to the user deployment configuration.

10. The method according to claim 9, wherein: The method further includes: before the continuous deployment stage, when the business code of the front-end development task is developed, calling a local distributed version controller Git tool to push the business code of the front-end development task to a remote warehouse; Then, calling the continuous deployment platform to deploy the business code of the front-end development task to the server according to the user deployment configuration includes: The code deployment interface provided by the continuous deployment platform is called to read the business code of the front-end development task from the remote warehouse through the continuous deployment platform, and then package and deploy it to the server.

11. The method according to claim 9, wherein: Display deployment progress information to users during the deployment process.

12. A front-end development device, the device is implemented using Electron technology, wherein: The device comprises: User interaction module, used to: Displaying a first user interaction interface, wherein the first user interaction interface includes M controls corresponding to the M stages included in the full process of the front-end development task, wherein the full process of the front-end development task includes the entire process from project creation of the front-end development task to deployment of the business code developed in the front-end development task to the server, wherein M is an integer greater than 1; In response to a selection operation on each of the M controls, displaying a second user interaction interface of the current stage corresponding to the selected control, wherein the second user interaction interface of the current stage is used to guide the user to perform task development of the current stage; and After the tasks in the M stages are all developed, information about the completion of the front-end development task is fed back to the user; A development module, used to call a third-party tool to perform task development in the current stage based on the user interaction operation in the second user interaction interface in the current stage; The M phases include a project creation phase, a dependency installation phase, a code generation phase, and a continuous deployment phase; The second user interaction interface in the project creation phase includes a directory selection area and a project initialization mode selection control; The second user interaction interface in the dependency installation phase includes a file directory selection area and a dependency installation button; The second user interaction interface in the code generation stage includes a component selection area and a page splicing area; The second user interaction interface in the continuous deployment phase includes a deployment information configuration control and a one-key deployment button.

13. An electronic device comprising: one or more processors; one or more memories for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors execute the method according to any one of claims 1 to 11.

14. A computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, causes the processor to execute the method according to any one of claims 1 to 11.