Application configuration method, device, equipment and storage medium

By determining and combining the application portal files and functional components at the target end in the component library, the problem of low multi-end application development and collaboration efficiency is solved, and efficient multi-end application development and collaboration efficiency is achieved.

CN114217845BActive Publication Date: 2025-08-12CHINA CONSTRUCTION BANK
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
CN202111547820.9
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-12-16
Publication Date
2025-08-12
Estimated Expiration
2041-12-16

AI Technical Summary

Technical Problem

The development and collaboration efficiency of multi-end applications in the prior art is low, mainly because after modifying public components and methods, the information and configuration related to shared content needs to be updated in different project warehouses, resulting in cumbersome steps and taking a lot of time for developers.

Method used

By determining the application portal file at the target end, the corresponding functional components are determined in the component library, and the functional components are combined into the application at the target end according to the entry file, and different functional components are called in the same component library.

Benefits of technology

It improves the development and collaboration efficiency of multi-end applications, realizes code reuse, and reduces development and maintenance costs.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114217845B_ABST
    Figure CN114217845B_ABST
Patent Text Reader

Abstract

The present application provides an application configuration method, apparatus, device, and storage medium. The method first determines the entry file of the target-side application to be generated, then determines the functional components corresponding to the target-side application in the component library, and then, based on the entry file of the target-side application, combines the functional components corresponding to the target-side application into the target-side application. The application configuration method provided by the present application improves the development and collaboration efficiency of multi-terminal applications because it can concentrate the functional components of multi-terminal applications in the same component library and call different functional components through the entry file of the target-side application to generate the target-side application.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of Internet technology, and in particular to an application configuration method, device, equipment and storage medium. Background Art

[0002] Front-end development technology is a crucial computer application technology in today's internet age. Within front-end development, both traditional applications and the popular single-page or quasi-single-page applications may encompass multiple client-side applications due to their diverse application scenarios and user groups. For example, a single-page application targeting multiple user groups typically includes a service client for providing service functions and an administrator client for managing platform content. It may also include an operations-specific client for platform operations, a pre-sales client for external demonstrations, and a preview client for functional testing or previewing. Therefore, it is necessary to develop application configuration methods that address these multi-client requirements.

[0003] In the existing application configuration method, the single-page application on each end of the multi-terminal application is independently and collaboratively developed through the corresponding project repository, and by building a common library or sub-module, and then introducing the methods of the common library or sub-module in different project repositories, calling the common components and methods shared by the multi-terminal applications.

[0004] However, in the existing technology, after modifying common components and methods, etc., it is necessary to update the information and configuration related to the shared content in different project repositories, and then perform integration testing on each end application separately. This process is cumbersome and requires a lot of working time from developers, resulting in low efficiency in the development and collaboration of multi-end applications. Summary of the Invention

[0005] The present application provides an application configuration method, apparatus, device and storage medium to solve the technical problem of low efficiency in the development and collaboration of multi-terminal applications in the prior art.

[0006] In a first aspect, the present application provides a method for configuring an application, the method comprising:

[0007] Determine the entry file of the target application to be generated;

[0008] Determine in the component library the functional component corresponding to the application on the target end;

[0009] According to the entry file of the target-side application, functional components corresponding to the target-side application are combined into the target-side application.

[0010] In an optional implementation, the entry file includes at least one of the following: an end entry file, a routing entry file, and a first compilation configuration file;

[0011] The first compilation configuration file corresponds to the application on the target end.

[0012] In an optional implementation, determining the entry file of the target application to be generated includes:

[0013] Get the preset second compilation configuration file;

[0014] Remove the default end entry file from the second compilation configuration file and add the end entry file corresponding to the target end application to generate the first compilation configuration file;

[0015] Calling the page file function component to determine the routing entry file of the target application;

[0016] The target function is passed into the routing entry file corresponding to the application of the target end, and the end entry file of the application of the target end is determined.

[0017] In an optional implementation, the method further includes:

[0018] Defining element values of a constant array in a third compilation configuration file according to a preset name of the application on the target end, wherein the third compilation configuration file is a unified compilation configuration file corresponding to each end;

[0019] According to the preset program environment variables, define the name of the constant array;

[0020] A configuration command in the third compilation configuration file is determined according to the element value of the constant array, the name of the constant array, and the path of the first compilation configuration file, where the configuration command is used to call the first compilation configuration file.

[0021] In an optional implementation, before the target function is transferred into the routing entry file corresponding to the target end application and the end entry file of the target end application is determined, the method further includes:

[0022] According to the preset unified entry files corresponding to each end, the target function for returning the root instance is determined.

[0023] In an optional implementation, before determining the entry file of the target application to be generated, the following steps are included:

[0024] Create the front-end framework of the target application;

[0025] In the front-end framework of the target application, an entry file to be determined corresponding to the target application is created, where the entry file to be determined includes a unified entry file and a third compilation configuration file.

[0026] In an optional implementation, determining the functional component corresponding to the target application in the component library includes:

[0027] Receiving an application configuration instruction sent by a terminal device, wherein the application configuration instruction includes an identifier of a functional component corresponding to the application of the target end to be configured;

[0028] According to the identifier of the functional component, a functional component corresponding to the application of the target end is determined in the component library.

[0029] In an optional implementation, the target end includes at least one of the following: a mobile end and a desktop end.

[0030] In a second aspect, the present application provides an application configuration device, the device comprising:

[0031] A determination module is used to determine an entry file of a target end application to be generated; and to determine a functional component corresponding to the target end application in a component library;

[0032] The combination module is used to combine the functional components corresponding to the target-side application into the target-side application according to the entry file of the target-side application.

[0033] In an optional implementation, the entry file includes at least one of the following: an end entry file, a routing entry file, and a first compilation configuration file; wherein the first compilation configuration file corresponds to the application of the target end.

[0034] In an optional implementation, the determination module is specifically used to obtain a preset second compilation configuration file; remove the default end entry file in the second compilation configuration file and add the end entry file corresponding to the target end application to generate the first compilation configuration file; call the page file function component to determine the routing entry file of the target end application; pass the target function into the routing entry file corresponding to the target end application to determine the end entry file of the target end application.

[0035] In an optional embodiment, the determination module is also used to define the element value of the constant array in the third compilation configuration file according to the preset name of the application of the target end, and the third compilation configuration file is a unified compilation configuration file corresponding to each end; define the name of the constant array according to the preset program environment variables; determine the configuration command in the third compilation configuration file according to the element value of the constant array, the name of the constant array and the path of the first compilation configuration file, and the configuration command is used to call the first compilation configuration file.

[0036] In an optional implementation, the determination module is further used to determine the target function for returning the root instance based on the preset unified entry file corresponding to each end.

[0037] In an optional implementation, the determination module is specifically used to create a front-end framework of the target application; in the front-end framework of the target application, an entry file to be determined corresponding to the target end application is created, and the entry file to be determined includes a unified entry file and a third compilation configuration file.

[0038] In an optional embodiment, the determination module is specifically used to receive an application configuration instruction sent by a terminal device, wherein the application configuration instruction includes an identifier of a functional component corresponding to the application of the target end to be configured; and based on the identifier of the functional component, determine the functional component corresponding to the application of the target end in the component library.

[0039] In an optional implementation, the target end includes at least one of the following: a mobile end and a desktop end.

[0040] In a third aspect, the present application further provides a computer program product, comprising a computer program, which, when executed by a processor, implements the method described in any one of the first aspects.

[0041] In a fourth aspect, the present invention further provides a computer storage medium storing a plurality of instructions, wherein the instructions are suitable for being loaded by a processor and executing the method as described in any one of the first aspects.

[0042] In a fifth aspect, the present application further provides an electronic device comprising: a processor and a memory; wherein the memory stores a computer program, and the computer program is suitable for being loaded by the processor and executing the method as described in any one of the first aspects.

[0043] The present application provides an application configuration method, apparatus, device, and storage medium. The method first determines the entry file of the target-side application to be generated, then determines the functional components corresponding to the target-side application in the component library, and then, based on the entry file of the target-side application, combines the functional components corresponding to the target-side application into the target-side application. The application configuration method provided by the present application improves the development and collaboration efficiency of multi-terminal applications because it can concentrate the functional components of multi-terminal applications in the same component library and call different functional components through the entry file of the target-side application to generate the target-side application. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] In order to more clearly illustrate the technical solutions in the present invention or the prior art, a brief introduction will be given below to the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0045] Figure 1 A schematic diagram of an application scenario of a configuration method for an application provided in an embodiment of the present application;

[0046] Figure 2 A flowchart of a configuration method for an application provided in an embodiment of the present application;

[0047] Figure 3 A project directory structure diagram of a target application provided in an embodiment of the present application;

[0048] Figure 4 A flowchart of another configuration method for an application provided in an embodiment of the present application;

[0049] Figure 5 A schematic diagram of the structure of a configuration device for an application provided in an embodiment of the present application;

[0050] Figure 6 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0051] To make the purpose, technical solutions, and advantages of the embodiments of this application more clear, the technical solutions in the embodiments of this application will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of this application. Obviously, the described embodiments are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0052] Front-end development is a crucial computer application technology in today's internet age. Its primary platform is front-end interfaces such as web browsers and mobile applications. Through front-end development, users can quickly and easily browse and interact with text, images, audio, and video content on web pages or application interfaces. In recent years, with the advancement of network and communication technologies, faster networks and higher-performance mobile terminals have emerged, driving the demand for the development and upgrading of front-end development technology. This has ushered in an era of large-scale engineering and modular development.

[0053] In front-end development, whether traditional applications or today's popular single-page or quasi-single-page applications, they may include multiple client applications due to their diverse application scenarios or user groups. For example, a single-page application targeting multiple user groups typically includes a service client for providing service functions and an administrator client for managing platform content. It may also include a dedicated operations client for platform operations, a pre-sales client for external demonstrations, and a preview client for functional testing or previewing. Therefore, it is necessary to develop application configuration methods that correspond to multi-client requirements.

[0054] In the existing application configuration method, the single-page application on each end of the multi-terminal application is independently and collaboratively developed through the corresponding project repository, and by building a common library or sub-module, and then introducing the methods of the common library or sub-module in different project repositories, calling the common components and methods shared by the multi-terminal applications.

[0055] However, in the existing technology, after modifying common components and methods, etc., it is necessary to update the information and configuration related to the shared content in different project repositories, and then perform integration testing on each end application separately. This process is cumbersome and requires a lot of working time from developers, resulting in low efficiency in the development and collaboration of multi-end applications.

[0056] To solve the above technical problems, embodiments of the present application provide an application configuration method, apparatus, device, and storage medium. In embodiments of the present application, by centralizing the functional components of the target-side application in the same component library, different functional components are called through entry files to generate the target-side application, thereby maximizing code reuse and improving the development and collaboration efficiency of multi-terminal applications.

[0057] The following describes the application scenarios of the configuration method of the application involved in this application.

[0058] Figure 1 This is a schematic diagram of an application scenario of a configuration method for an application provided in an embodiment of the present application. Figure 1 As shown, the system includes a terminal device 101, a terminal device 102, and a server 103, wherein the terminal device 101 is a mobile terminal and the terminal device 102 is a desktop terminal. When the server 103 configures applications for the terminal devices 101 and 102, respectively, the server 103 can first determine the entry files of the applications to be generated for the terminal devices 101 and 102, respectively, then determine the functional components corresponding to the applications of the terminal devices 101 and 102 in the component library, and then, based on the entry files, combine the functional components corresponding to the applications of the terminal devices 101 and 102 into the application of the terminal device 101 and the application of the terminal device 102, respectively.

[0059] Among them, the above-mentioned terminal device can be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in a smart home, etc. In the embodiment of the present application, the device for realizing the function of the terminal can be a terminal, or it can be a device that can support the terminal to realize the function, such as a chip system, which can be installed in the terminal. In the embodiment of the present application, the chip system can be composed of a chip, or it can include a chip and other discrete devices.

[0060] The server may be, but is not limited to, a single network server, a server group consisting of multiple network servers, or a cloud based on cloud computing consisting of a large number of computers or network servers.

[0061] It should be understood that the application scenario of the technical solution of this application can be Figure 1 The present invention is not limited to the configuration scenario of the application in the present invention, but can also be applied to other scenarios where the application needs to be configured.

[0062] It can be understood that the above-mentioned application configuration method can be implemented by the application configuration device provided in the embodiment of the present application, and the application configuration device can be part or all of a certain device, such as a server.

[0063] The following uses a server integrated with or installed with relevant execution code as an example to describe the technical solution of the embodiment of the present application in detail with a specific embodiment. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments.

[0064] Figure 2 This is a flow chart of a configuration method for an application provided in an embodiment of the present application. This embodiment relates to the configuration process of the application. Figure 2 As shown, the method includes:

[0065] S201: Determine the entry file of the target application to be generated.

[0066] In an embodiment of the present application, the server may first determine the entry file of the target end application to be generated, and then generate the target end application by writing and configuring the entry file.

[0067] The target end can be any end of a target application built on a front-end framework, and this embodiment of the application does not limit this. In some embodiments, the target end can include a mobile end, a desktop end, etc. For example, if the target application is a browser, the target end application can be a mobile end application or a desktop end application of the browser.

[0068] In some embodiments, before determining the entry file of the target application to be generated, the server may also create a front-end framework of the target application, and then create the entry file to be determined corresponding to the target application in the front-end framework of the target application, wherein the entry file to be determined includes a unified entry file and a third compilation configuration file.

[0069] It should be understood that the server can create the front-end framework of the target application through the web front-end framework, and the embodiments of the present application do not limit this. In some embodiments, the web front-end framework used to create the target application can be a progressive framework (Vue.js). Exemplarily, the server can write the source code of the target application through the Vue framework and its ecosystem plug-ins (Vue-Router and Vuex), and compile the configuration file of the target application through the project tool flow software (Vue-CLI). Furthermore, the unified entry file can be the page entry file (main.js) of the target application, and the third compilation configuration file can be the unified compilation configuration file (vue.config.js) corresponding to each end in the target application.

[0070] The entry file of the target-side application is used to call and configure the functional components corresponding to the target-side application. The embodiments of the present application do not limit the type of the entry file. In some embodiments, the entry file of the target-side application may include an end entry file, a routing entry file, a first compilation configuration file, etc., wherein the first compilation configuration file corresponds to the target-side application. For example, if the target-side application includes a user-side (client) application and a manager (manager) application, the end entry file of the target-side application may include a user-side entry file (main.client.js) and a manager-side entry file (main.manager.js); the routing entry file of the target-side application may include a user-side routing entry file (router.client.js) and a manager-side routing entry file (router.manager.js); the first compilation configuration file of the target-side application may include a user-side first compilation configuration file (vue.config.client.js) and a manager-side first compilation configuration file (vue.config.manager.js).

[0071] The embodiments of the present application do not limit how to determine the entry file of the target end application to be generated. In some embodiments, the server can obtain a preset second compilation configuration file, and then remove the default end entry file in the second compilation configuration file and add the end entry file corresponding to the target end application to generate a first compilation configuration file. Then, the page file function component is called to determine the routing entry file of the target end application, and finally, the target function is passed into the routing entry file corresponding to the target end application to determine the end entry file of the target end application. Among them, the preset second compilation configuration file can be a pre-created blank user-end first compilation configuration file (vue.config.client.js) and a management-end first compilation configuration file (vue.config.manager.js).

[0072] Exemplarily, for a user-side application, the server can first create a blank entry file for the user-side application, then obtain a blank first compiled configuration file for the user-side (vue.config.client.js), and define the package entry command in the file to remove the default end entry file and add the end entry file corresponding to the target end application, thereby determining the first compiled configuration file (vue.config.client.js). Then, by calling the preset page file function component, the routing entry file (router.client.js) of the user-side is determined. Finally, by defining the routing entry file (router.client.js) that passes the target function to the user-side in the blank user-side entry file (main.client.js), the user-side entry file (main.client.js) is determined.

[0073] In other embodiments, before passing the target function into the routing entry file corresponding to the target application and determining the target application's terminal entry file, the server may also determine a target function for returning the root instance based on a preset unified entry file corresponding to each terminal. For example, the server may modify the target application's unified entry file (main.js) to export a target function (main function), which is configured to return a Vue root instance for rendering website content.

[0074] The embodiment of the present application does not limit how the server determines the third compilation configuration file (vue.config.js). In other embodiments, the server may also define the element value of the constant array in the third compilation configuration file according to the preset name of the application on the target end; then, define the name of the constant array according to the preset program environment variable; finally, determine the configuration command in the third compilation configuration file according to the element value of the constant array, the name of the constant array and the path of the first compilation configuration file, and the configuration command is used to call the first compilation configuration file. For example, the server may define the values of the array elements of the constant array (appNames) to include the user end (client) and the management end (manager), and assign the constant (appName) to the program environment variable (APP_NAME). Then, the server sets the configuration command to return vue.config.client.js when the value of the constant (appName) passed in is client; when the value of the constant (appName) passed in is manager, return vue.config.manager.js; when the value of the constant (appName) passed in is other values, an error is thrown, indicating that an unknown application name has been passed in.

[0075] Figure 3 A project directory structure diagram of a target application provided in an embodiment of the present application. As shown in the figure, integration represents the name of the target application, and the project directory structure also includes a source code folder 301 and a project configuration folder 302. Among them, src represents the source code folder 301, and the source code folder 301 includes an asset directory (assets), a public component directory (components), a front-end route (router), a page directory (views), a main component (APP.vue), an entry file (main.js, main.client.js, main.manager.js), and a routing entry file (router.client.js, router.manager.js) of the target end. The project configuration folder 302 includes a unified compilation configuration file (vue.config.js) and a first compilation configuration file (vue.config.client.js, vue.config.manager.js) of the target end.

[0076] In an embodiment of the present application, the end entry files and routing entry files of the applications of each end are centrally maintained in the project directory structure of a target application, and different first compilation configuration files (vue.config.client.js, vue.config.manager.js) are written for different ends, so that the applications corresponding to each end can be compiled.

[0077] S202: Determine the functional component corresponding to the target application in the component library.

[0078] In this step, after determining the entry file of the target-side application to be generated, the server can determine the functional components corresponding to the target-side application in the component library.

[0079] It should be noted that in the embodiment of the present application, the functional components corresponding to the applications at each end of the target application are placed in the same component library, and the server introduces the corresponding functional components through the entry files of each end.

[0080] The embodiments of the present application do not limit how to determine the functional components corresponding to the target application. In some embodiments, the server can receive an application configuration instruction sent by the terminal device, the application configuration instruction including the identifier of the functional component corresponding to the target application to be configured, and then determine the functional component corresponding to the target application in the component library based on the identifier of the functional component.

[0081] In an embodiment of the present application, by placing all functional components of the target-end application in the same component library and compiling different end applications from different entry files, the effect is achieved that all functional components can be shared by multi-end applications, thereby improving the development and collaboration efficiency of multi-end applications and reducing development and maintenance costs.

[0082] S203: According to the entry file of the target-side application, functional components corresponding to the target-side application are combined into the target-side application.

[0083] In this step, after determining the functional components corresponding to the target application, the server may combine the functional components corresponding to the target application into the target application according to the entry file of the target application.

[0084] In some embodiments, the server can treat the endpoint entry files of each endpoint as a logical front-end, and other functional components as a logical back-end. By configuring and importing the back-end through the front-end, applications corresponding to different target endpoints can be assembled. Because the back-end can be shared by applications on each endpoint through code import, code development costs can be reduced, as well as the cost of refactoring the target application during subsequent compilation.

[0085] The present application provides a method for configuring an application. First, the entry file of the target-side application to be generated is determined. Subsequently, the functional components corresponding to the target-side application are determined in the component library. Then, based on the entry file of the target-side application, the functional components corresponding to the target-side application are combined into the target-side application. The method for configuring an application provided by the present application improves the development and collaboration efficiency of multi-terminal applications because the functional components of multi-terminal applications can be concentrated in the same component library. Different functional components can be called through the entry file of the target-side application to generate the target-side application.

[0086] Based on the above embodiment, how to determine the entry file of the target application to be generated is described below. Figure 4 A flow chart of another configuration method for an application provided in an embodiment of the present application is shown as follows: Figure 4 As shown, the method includes:

[0087] S401: Obtain a preset second compilation configuration file.

[0088] S402: Remove the default end entry file from the second compilation configuration file and add the end entry file corresponding to the target end application to generate a first compilation configuration file.

[0089] S403: Call the page file function component to determine the routing entry file of the target application.

[0090] S404: The target function is transferred to the routing entry file corresponding to the target end application, and the end entry file of the target end application is determined.

[0091] S405: Determine the functional component corresponding to the target application in the component library.

[0092] S406: According to the entry file of the target-side application, functional components corresponding to the target-side application are combined into the target-side application.

[0093] The technical terms, technical effects, technical features, and optional implementation methods of S401-S406 can be referred to Figure 2 The S201-S203 shown are understood, and the repeated content will not be repeated here.

[0094] The present application provides a method for configuring an application. First, the entry file of the target-side application to be generated is determined. Subsequently, the functional components corresponding to the target-side application are determined in the component library. Then, based on the entry file of the target-side application, the functional components corresponding to the target-side application are combined into the target-side application. The method for configuring an application provided by the present application improves the development and collaboration efficiency of multi-terminal applications because the functional components of multi-terminal applications can be concentrated in the same component library. Different functional components can be called through the entry file of the target-side application to generate the target-side application.

[0095] Those skilled in the art will appreciate that all or part of the steps in the above-described method embodiments can be implemented by hardware associated with program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments. The aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0096] Figure 5 This is a schematic diagram of the structure of a configuration device for an application provided in an embodiment of the present application. The configuration device for the application can be implemented by software, hardware, or a combination of both, and can be, for example, the server in the above embodiment to execute the configuration method of the application in the above embodiment. Figure 5 As shown, the configuration device 500 of the application includes:

[0097] The determination module 501 is used to determine the entry file of the target application to be generated; determine the functional components corresponding to the target application in the component library;

[0098] The combining module 502 is configured to combine the functional components corresponding to the target-side application into the target-side application according to the entry file of the target-side application.

[0099] In an optional implementation, the entry file includes at least one of the following: an end entry file, a routing entry file, and a first compilation configuration file; wherein the first compilation configuration file corresponds to an application on the target end.

[0100] In an optional implementation, the determination module 501 is specifically used to obtain a preset second compilation configuration file; remove the default end entry file in the second compilation configuration file and add the end entry file corresponding to the target end application to generate a first compilation configuration file; call the page file function component to determine the routing entry file of the target end application; pass the target function into the routing entry file corresponding to the target end application to determine the end entry file of the target end application.

[0101] In an optional implementation, the determination module 501 is also used to define the element value of the constant array in the third compilation configuration file according to the preset name of the application of the target end, and the third compilation configuration file is a unified compilation configuration file corresponding to each end; define the name of the constant array according to the preset program environment variables; determine the configuration command in the third compilation configuration file according to the element value of the constant array, the name of the constant array and the path of the first compilation configuration file, and the configuration command is used to call the first compilation configuration file.

[0102] In an optional implementation, the determination module 501 is further configured to determine a target function for returning to the root instance based on a preset unified entry file corresponding to each end.

[0103] In an optional implementation, the determination module 501 is specifically used to create a front-end framework of the target application; in the front-end framework of the target application, an entry file to be determined corresponding to the target end application is created, and the entry file to be determined includes a unified entry file and a third compilation configuration file.

[0104] In an optional implementation, the determination module 501 is specifically used to receive an application configuration instruction sent by a terminal device, where the application configuration instruction includes an identifier of a functional component corresponding to the target end application to be configured; based on the identifier of the functional component, the functional component corresponding to the target end application is determined in the component library.

[0105] In an optional implementation, the target end includes at least one of the following: a mobile end and a desktop end.

[0106] Need to explain, Figure 5 The application configuration device provided in the illustrated embodiment can be used to execute the application configuration method provided in the above-mentioned embodiment. The specific implementation method and technical effect are similar and will not be described in detail here.

[0107] Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. Figure 6 As shown, the electronic device 600 may include: at least one processor 601 and a memory 602 . Figure 6 An electronic device is shown using a processor as an example.

[0108] The memory 602 is used to store programs. Specifically, the programs may include program codes, and the program codes include computer operation instructions.

[0109] The memory 602 may include a high-speed RAM memory, and may also include a non-volatile memory (non-volatile memory), such as at least one disk memory.

[0110] The processor 601 is configured to execute computer-executable instructions stored in the memory 602 to implement the configuration method of the above application;

[0111] The processor 601 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application.

[0112] Alternatively, in a specific implementation, if the communication interface, memory 602, and processor 601 are implemented independently, they may be interconnected via a bus and communicate with each other. The bus may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus. Buses can be categorized as address buses, data buses, control buses, etc., but this does not mean that there is only one bus or only one type of bus.

[0113] Optionally, in a specific implementation, if the communication interface, the memory 602 and the processor 601 are integrated on a chip, the communication interface, the memory 602 and the processor 601 can complete communication through an internal interface.

[0114] The present application also provides a chip comprising a processor and an interface. The interface is used to input and output data or instructions processed by the processor. The processor is used to execute the method provided in the above method embodiment. The chip can be used in an application configuration device.

[0115] An embodiment of the present application also provides a program, which, when executed by a processor, is used to execute the configuration method of the application provided in the above method embodiment.

[0116] An embodiment of the present application also provides a program product, such as a computer-readable storage medium, which stores instructions that, when executed on a computer, enable the computer to execute the application configuration method provided in the above method embodiment.

[0117] The present application also provides a computer-readable storage medium, which may include various media capable of storing program code, such as a USB flash drive, a mobile hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk. Specifically, the computer-readable storage medium stores program information, which is used for the configuration method of the above-mentioned application.

[0118] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function according to the embodiment of the present invention is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive (SSD)).

[0119] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the above embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the above embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A configuration method for an application, characterized in that: The method comprises: Determine an entry file of a target end application to be generated; the entry file includes at least one of the following: an end entry file, a routing entry file, and a first compilation configuration file; wherein the first compilation configuration file corresponds to the target end application; Receiving an application configuration instruction sent by a terminal device, wherein the application configuration instruction includes an identifier of a functional component corresponding to the application of the target end to be configured; Determining, in a component library, a functional component corresponding to the target application according to the identifier of the functional component; wherein the functional components corresponding to the applications at each end of the target application are all placed in the same component library; Combining functional components corresponding to the target-side application into the target-side application according to the entry file of the target-side application; The step of determining the entry file of the target application to be generated includes: Get the preset second compilation configuration file; Remove the default end entry file from the second compilation configuration file and add the end entry file corresponding to the target end application to generate the first compilation configuration file; Calling the page file function component to determine the routing entry file of the target application; The target function is passed into the routing entry file corresponding to the target end application, and the end entry file of the target end application is determined; The method further comprises: Defining element values of a constant array in a third compilation configuration file according to a preset name of the application on the target end, wherein the third compilation configuration file is a unified compilation configuration file corresponding to each end; According to the preset program environment variables, define the name of the constant array; Determining, according to the element values of the constant array, the name of the constant array, and the path of the first compile configuration file, a configuration command in the third compile configuration file, where the configuration command is used to call the first compile configuration file; Before the target function is transferred into the routing entry file corresponding to the target end application and the end entry file of the target end application is determined, the method further includes: According to the preset unified entry files corresponding to each end, the target function for returning the root instance is determined.

2. The method according to claim 1, characterized in that Before determining the entry file of the target application to be generated, the following steps are included: Create the front-end framework of the target application; In the front-end framework of the target application, an entry file to be determined corresponding to the target application is created, where the entry file to be determined includes a unified entry file and a third compilation configuration file.

3. The method according to claim 1 or 2, characterized in that The target terminal includes at least one of the following: a mobile terminal and a desktop terminal.

4. An application configuration device, characterized in that: The device comprises: A determination module is configured to determine an entry file for a target-side application to be generated; receive an application configuration instruction sent by a terminal device, the application configuration instruction including an identifier of a functional component corresponding to the target-side application to be configured; and determine, in a component library, the functional component corresponding to the target-side application based on the identifier of the functional component; the entry file includes at least one of the following: an end entry file, a routing entry file, and a first compilation configuration file; wherein the first compilation configuration file corresponds to the target-side application; and the functional components corresponding to the applications at each end of the target application are all placed in the same component library; a combining module, configured to combine functional components corresponding to the target-side application into the target-side application according to the entry file of the target-side application; The determination module is specifically configured to obtain a preset second compilation configuration file; remove the default end entry file from the second compilation configuration file and add the end entry file corresponding to the target end application to generate the first compilation configuration file; call the page file function component to determine the routing entry file of the target end application; pass the target function into the routing entry file corresponding to the target end application to determine the end entry file of the target end application; The determination module is also used to define the element value of the constant array in the third compilation configuration file according to the preset name of the application of the target end, and the third compilation configuration file is a unified compilation configuration file corresponding to each end; define the name of the constant array according to the preset program environment variables; determine the configuration command in the third compilation configuration file according to the element value of the constant array, the name of the constant array and the path of the first compilation configuration file, and the configuration command is used to call the first compilation configuration file; determine the target function used to return to the root instance according to the preset unified entry file corresponding to each end.

5. A computer storage medium, characterized in that The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to any one of claims 1 to 3 when executed by a processor.

6. An electronic device, characterized in that: include: A processor and a memory; wherein the memory stores a computer program, and the computer program is suitable for being loaded by the processor and executing the method according to any one of claims 1 to 3.

7. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the method according to any one of claims 1 to 3 is implemented.

Citation Information

Patent Citations

  • Assembly-based platform deployment method and device, equipment and storage medium

    CN113703785A