Application method and device of front-end service component library, storage medium and server

Abstract

The invention relates to an application method and device of a front-end service component library, a storage medium and a server. The application method of the front-end business component library comprises the following steps: acquiring a plurality of business components for executing similar businesses; carrying out application scene abstraction on the basis of similar service logics of the plurality of service components for executing the similar services to obtain standardized components for executing the similar services; a plurality of standardized components executing different similar services are stored in corresponding storage positions in a standardized component library; and calling the standardized component in the standardized component library by adopting a component calling mode corresponding to an application requirement based on the application requirement on the standardized component in the standardized component library. In the whole development process, the calling of the standardized component is beneficial to greatly reducing the business development of repeated operation in the business by developers, thereby being beneficial to improving the overall development efficiency of the project.

Description

Technical Field

[0001] The present disclosure relates to the field of computer technology, and in particular to an application method of a front-end business component library, an application device of the front-end business component library, a storage medium and a server. Background Art

[0002] With the rapid development and continuous innovation of front-end technology, UI component libraries have gradually become an indispensable and important part of front-end development. UI component libraries can provide rich and diverse resources for front-end developers, which can significantly improve development efficiency and convenience. These UI component libraries are basic component libraries, and the internal UI components are called basic components. They are the smallest basic units or granularity that constitute the abstract structure of front-end applications. However, in daily work, the combination of multiple basic components will have a large number of similar business logics. This causes front-end developers to often face a large amount of repetitive development work. This will undoubtedly affect the overall development efficiency of the project. Summary of the invention

[0003] In view of this, the embodiments of the present disclosure are intended to provide an application method of a front-end business component library, an application device of the front-end business component library, a storage medium, and a server.

[0004] The technical solution of the present disclosure is achieved as follows:

[0005] In a first aspect, the present disclosure provides an application method of a front-end business component library.

[0006] The application method of the front-end business component library provided by the embodiment of the present disclosure includes:

[0007] Obtain multiple business components that perform similar business operations;

[0008] Abstracting the application scenarios of similar business logics of the multiple business components that execute similar businesses, and obtaining standardized components for executing similar businesses;

[0009] Store multiple standardized components that perform different similar businesses in their respective corresponding storage locations in the standardized component library;

[0010] Based on application requirements for standardized components in the standardized component library, the standardized components in the standardized component library are called using a component calling method corresponding to the application requirements.

[0011] In some embodiments, the similar business logics of the multiple business components that perform similar business are abstracted by application scenarios to obtain standardized components for performing similar business, including:

[0012] Determine similar business logics of the multiple similar businesses based on the same operations included in the multiple similar businesses executed by the business component;

[0013] Based on the similar business logic, application scenario abstraction is performed to obtain the standardized component; wherein the standardized component is at least used to execute the same operations included in the multiple similar businesses.

[0014] In some embodiments, based on the application requirements for the standardized components in the standardized component library, calling the standardized components in the standardized component library using a component calling method corresponding to the application requirements includes:

[0015] If the application requirement for the standardized components in the standardized component library is to call all the standardized components in the standardized component library, then determine that the component calling method corresponding to the application requirement is a calling method of all standardized components that are introduced into the standardized component library and registered using a front-end engineering entry file;

[0016] Based on all standardized component calling methods introduced into the standardized component library and registered by using the front-end engineering entry file, calling the standardized components in the standardized component library;

[0017] If the application requirement for the standardized components in the standardized component library is to call a local standardized component in the standardized component library, determining that the component calling method corresponding to the application requirement is a local standardized component calling method of partially introducing the standardized component through the development page;

[0018] Based on the local standardized component calling mode of partially introducing the standardized components through the development page, some standardized components in the standardized component library are called.

[0019] In some embodiments, storing a plurality of standardized components that perform different similar services in respective corresponding storage locations in a standardized component library includes:

[0020] According to the predetermined different standardized components corresponding to different storage locations, a plurality of standardized components that execute different similar businesses are respectively stored in the corresponding storage locations in the standardized component library.

[0021] In some embodiments, the standardized component library includes a standardized component storage location, a configuration file, and a component demo storage location; wherein the configuration file is used to describe the functions of the standardized components stored in the standardized component library;

[0022] The method of storing a plurality of standardized components for executing different similar services in respective corresponding storage locations in the standardized component library includes:

[0023] Multiple standardized components that perform different similar businesses are stored in standardized component storage locations of the standardized component library.

[0024] In a second aspect, the present disclosure provides an application device of a front-end business component library, including:

[0025] A business component acquisition module is used to acquire multiple business components that perform similar businesses;

[0026] A standardized component generation module, used to abstract the application scenarios of the similar business logics of the multiple business components that perform similar business, and obtain standardized components for performing similar business;

[0027] A standardized component storage module is used to store multiple standardized components that perform different similar services in their respective corresponding storage locations in the standardized component library;

[0028] The component calling module is used to call the standardized components in the standardized component library based on the application requirements for the standardized components in the standardized component library and adopt the component calling method corresponding to the application requirements.

[0029] In some embodiments, the standardized component generation module is used to

[0030] Determine similar business logics of the multiple similar businesses based on the same operations included in the multiple similar businesses executed by the business component;

[0031] Based on the similar business logic, application scenario abstraction is performed to obtain the standardized component; wherein the standardized component is at least used to execute the same operations included in the multiple similar businesses.

[0032] In some embodiments, the component calls a module for

[0033] If the application requirement for the standardized components in the standardized component library is to call all the standardized components in the standardized component library, then determine that the component calling method corresponding to the application requirement is a calling method of all standardized components that are introduced into the standardized component library and registered using a front-end engineering entry file;

[0034] Based on all standardized component calling methods introduced into the standardized component library and registered by using the front-end engineering entry file, calling the standardized components in the standardized component library;

[0035] If the application requirement for the standardized components in the standardized component library is to call a local standardized component in the standardized component library, determining that the component calling method corresponding to the application requirement is a local standardized component calling method of partially introducing the standardized component through the development page;

[0036] Based on the local standardized component calling mode of partially introducing the standardized components through the development page, some standardized components in the standardized component library are called.

[0037] In a third aspect, the present disclosure provides a computer-readable storage medium on which an application of a front-end business component library is stored. When the application of the front-end business component library is executed by a processor, the application method of the front-end business component library described in the first aspect is implemented.

[0038] In a fourth aspect, the present disclosure provides a server comprising a memory, a processor, and an application of a front-end business component library stored in the memory and executable on the processor, wherein when the processor executes the application of the front-end business component library, the application method of the front-end business component library described in the first aspect is implemented.

[0039] According to the application method of the front-end business component library of the embodiment of the present disclosure, the method comprises: obtaining multiple business components that perform similar business; abstracting the application scenarios based on the similar business logics of the multiple business components that perform similar business, and obtaining the standardized components when performing similar business; storing the multiple standardized components that perform different similar business in the corresponding storage locations in the standardized component library respectively; based on the application requirements of the standardized components in the standardized component library, using the component calling method corresponding to the application requirements, calling the standardized components in the standardized component library. In the present application, by abstracting the application scenarios of the similar business logics of the multiple business components that perform similar business, the standardized components when performing similar business are obtained, and then the multiple standardized components that perform different similar business are stored in the corresponding storage locations in the standardized component library respectively. When the standardized components need to be called in the standardized component library, the standardized components in the standardized component library can be called based on the application requirements of the standardized components in the standardized component library, using the component calling method corresponding to the application requirements. The calling of standardized components in the entire development process is conducive to greatly reducing the business development of developers for repeated operations in the business, thereby helping to improve the overall development efficiency of the project.

[0040] Additional aspects and advantages of the present disclosure will be given in part in the following description and in part will be obvious from the following description or learned through practice of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] Figure 1is a flow chart of an application method of a front-end business component library according to an exemplary embodiment;

[0042] Figure 2 is an application flow chart of a standardized component library according to an exemplary embodiment;

[0043] Figure 3 The diagram is a schematic diagram of the structure of an application device of a front-end business component library according to an exemplary embodiment. DETAILED DESCRIPTION

[0044] Embodiments of the present disclosure are described in detail below, examples of which are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present disclosure, and should not be construed as limiting the present disclosure.

[0045] With the rapid development and continuous innovation of front-end technology, UI component libraries have gradually become an indispensable and important part of front-end development. UI component libraries can provide rich and diverse resources for front-end developers, which can significantly improve development efficiency and convenience. These UI component libraries are basic component libraries, and the internal UI components are called basic components. They are the smallest basic units or granularity that constitute the abstract structure of front-end applications. However, in daily work, the combination of multiple basic components will have a large number of similar business logics. This causes front-end developers to often face a large amount of repetitive development work. This will undoubtedly affect the overall development efficiency of the project.

[0046] In view of the above situation, the present disclosure provides an application method of a front-end business component library. Figure 1 FIG. 1 is a flow chart of an application method of a front-end business component library according to an exemplary embodiment. Figure 1 As shown, the application method of the front-end business component library includes:

[0047] Step 10: Obtain multiple business components that perform similar business;

[0048] Step 11: abstract the application scenarios of the similar business logics of the multiple business components that execute similar businesses, and obtain standardized components for executing similar businesses;

[0049] Step 12: Store multiple standardized components that perform different similar services in their corresponding storage locations in the standardized component library;

[0050] Step 13: Based on application requirements for the standardized components in the standardized component library, the standardized components in the standardized component library are called using a component calling method corresponding to the application requirements.

[0051] In this exemplary embodiment, similar services in multiple service components that perform similar services can be, for example, account and password login. For example, different system platforms perform account and password login for the same service. Similar service logic is to perform the same service operations on similar services. For example, the same account and password login are performed on different system platforms. The standardized components when performing similar services can be service components that perform the same operations in similar services. For example, account and password login in different application scenarios are performed on different system platforms.

[0052] In this exemplary embodiment, different locations in the standardized component library may be used to store different standardized components.

[0053] In this exemplary embodiment, according to the application requirements of different standardized components in the standardized component library, the component calling methods of the standardized components may be different.

[0054] According to the application method of the front-end business component library of the embodiment of the present disclosure, the method comprises: obtaining multiple business components that perform similar business; abstracting the application scenarios based on the similar business logics of the multiple business components that perform similar business, and obtaining the standardized components when performing similar business; storing the multiple standardized components that perform different similar business in the corresponding storage locations in the standardized component library respectively; based on the application requirements of the standardized components in the standardized component library, using the component calling method corresponding to the application requirements, calling the standardized components in the standardized component library. In the present application, by abstracting the application scenarios of the similar business logics of the multiple business components that perform similar business, the standardized components when performing similar business are obtained, and then the multiple standardized components that perform different similar business are stored in the corresponding storage locations in the standardized component library respectively. When the standardized components need to be called in the standardized component library, the standardized components in the standardized component library can be called based on the application requirements of the standardized components in the standardized component library, using the component calling method corresponding to the application requirements. The calling of standardized components in the entire development process is conducive to greatly reducing the business development of developers for repeated operations in the business, thereby helping to improve the overall development efficiency of the project.

[0055] In some embodiments, the similar business logics of the multiple business components that perform similar business are abstracted by application scenarios to obtain standardized components for performing similar business, including:

[0056] Determine similar business logics of the multiple similar businesses based on the same operations included in the multiple similar businesses executed by the business component;

[0057] Based on the similar business logic, application scenario abstraction is performed to obtain the standardized component; wherein the standardized component is at least used to execute the same operations included in the multiple similar businesses.

[0058] In this exemplary embodiment, based on the same operations contained in multiple similar businesses executed by the business component, the similar business logics possessed by the multiple similar businesses are determined. For example, similar businesses include the advancement of the process of related businesses on different system platforms. Different system platforms, for example, include accounting systems, review systems, task allocation systems, and so on. However, multiple system platforms all contain the same operation of account and password login. In this regard, the same operation of account and password login can be determined as the similar business logic possessed by the multiple similar businesses. Then, based on the similar business logic, the application scenario is abstracted to obtain the standardized component of account and password login. In this way, it is convenient for subsequent developers to call standardized components, thereby reducing repetitive development work.

[0059] In some embodiments, based on the application requirements for the standardized components in the standardized component library, calling the standardized components in the standardized component library using a component calling method corresponding to the application requirements includes:

[0060] If the application requirement for the standardized components in the standardized component library is to call all the standardized components in the standardized component library, then determine that the component calling method corresponding to the application requirement is a calling method of all standardized components that are introduced into the standardized component library and registered using a front-end engineering entry file;

[0061] Based on all standardized component calling methods introduced into the standardized component library and registered by using the front-end engineering entry file, calling the standardized components in the standardized component library;

[0062] If the application requirement for the standardized components in the standardized component library is to call a local standardized component in the standardized component library, determining that the component calling method corresponding to the application requirement is a local standardized component calling method of partially introducing the standardized component through the development page;

[0063] Based on the local standardized component calling mode of partially introducing the standardized components through the development page, some standardized components in the standardized component library are called.

[0064] In this exemplary embodiment, the component calling method for the standardized components may be different according to the application requirements of different standardized components in the standardized component library. In the present application, the component calling method may include two types, namely, the whole standardized component calling method and the partial standardized component calling method. The whole standardized component calling method is to introduce the standardized component library and register it using the front-end engineering entry file, so that developers can directly use the standardized components in the standardized component library without having to introduce them separately through the page. The partial standardized component calling method is to partially introduce the required standardized components in the standardized component library through the development page. For example, a browsing page developed for customers to browse clothing information can introduce the standardized components in the standardized component library that can be browsed by the clothing information through the development page. In this way, the standardized component calling in the standardized component library can be implemented in different calling methods according to development needs.

[0065] In some embodiments, storing a plurality of standardized components that perform different similar services in respective corresponding storage locations in a standardized component library includes:

[0066] According to the predetermined different standardized components corresponding to different storage locations, a plurality of standardized components that execute different similar businesses are respectively stored in the corresponding storage locations in the standardized component library.

[0067] In this exemplary embodiment, the standardized component library includes a standardized component storage location, a configuration file, and a component demo storage location; wherein the configuration file is used to describe the functions of the standardized components stored in the standardized component library;

[0068] The step of storing a plurality of standardized components that perform different similar services in respective corresponding storage locations in the standardized component library comprises:

[0069] Multiple standardized components that perform different similar businesses are stored in standardized component storage locations of the standardized component library.

[0070] In this exemplary embodiment, the standardized component library includes standardized component storage locations. When storing standardized components in the standardized component library, different standardized components corresponding to different storage locations can be predetermined, and multiple standardized components that perform different similar businesses can be stored in their respective corresponding storage locations in the standardized component library. For example, different types of standardized components can be stored in their respective corresponding standardized component storage locations. For example, standardized component A is an account and password login component, which can correspond to the first standardized component storage location; standardized component B is a video playback component, which can correspond to the second standardized component storage location, and so on.

[0071] Figure 2FIG. 1 is a flowchart of an application of a standardized component library according to an exemplary embodiment. Figure 2 As shown in the figure, the application process of the standardized component library includes:

[0072] Step 20, start;

[0073] Step 21, determine whether it can be abstracted into a standardized component;

[0074] Step 22: If possible, abstract it into a standardized component;

[0075] Step 23: Install the business component library in the front-end project scaffolding;

[0076] Step 24: Determine whether a global complete registration component is required;

[0077] Step 25. If the component needs to be fully registered globally, the front-end engineering entry file introduces the installed standardized component library and registers it;

[0078] Step 26: During normal business development process, business components can be used directly without the need to introduce them separately on the page;

[0079] Step 27: If global and complete registration of components is not required, standardized components are introduced locally and used during normal business development process;

[0080] Step 28: Determine whether it can be abstracted into a standardized component. If not, proceed with the normal business development process.

[0081] Step 29, end.

[0082] In this application, the combination of multiple basic components is combined with the abstraction of scenarios with similar business logic to form reusable and standardized business components, which can save a lot of repetitive development tasks; at the same time, for similar business scenarios scattered in different projects, if they can be abstracted into common business components and applied, it will effectively reduce the impact caused by individual differences among developers, thereby improving the consistency and efficiency of completing development tasks; in addition, the combination of multiple basic components is combined with the abstraction of scenarios with similar business logic to form reusable and standardized business components. It is only necessary to maintain the business component in the component library, and there is no need to maintain multiple similar business scenarios scattered in different projects.

[0083] The present invention provides an application device for a front-end business component library. Figure 3 FIG. 1 is a schematic diagram of an application device structure of a front-end business component library according to an exemplary embodiment. Figure 3 As shown, the application device of the front-end business component library includes:

[0084] A business component acquisition module 30 is used to acquire multiple business components that perform similar businesses;

[0085] A standardized component generation module 31 is used to abstract the application scenarios of the similar business logics of the multiple business components that perform similar business, and obtain standardized components for performing similar business;

[0086] A standardized component storage module 32 is used to store a plurality of standardized components that perform different similar services in their respective corresponding storage locations in the standardized component library;

[0087] The component calling module 33 is used to call the standardized components in the standardized component library based on the application requirements for the standardized components in the standardized component library and adopt a component calling method corresponding to the application requirements.

[0088] In this exemplary embodiment, similar services in multiple service components that perform similar services can be, for example, account and password login. For example, different system platforms perform account and password login for the same service. Similar service logic is to perform the same service operations on similar services. For example, the same account and password login are performed on different system platforms. The standardized components when performing similar services can be service components that perform the same operations in similar services. For example, account and password login in different application scenarios are performed on different system platforms.

[0089] In this exemplary embodiment, different locations in the standardized component library may be used to store different standardized components.

[0090] In this exemplary embodiment, according to the application requirements of different standardized components in the standardized component library, the component calling methods of the standardized components may be different.

[0091] According to the application device of the front-end business component library of the embodiment of the present disclosure, it is used to obtain multiple business components that perform similar businesses; based on the similar business logic of multiple business components that perform similar businesses, the application scenario is abstracted to obtain standardized components when performing similar businesses; multiple standardized components that perform different similar businesses are stored in the standardized component library in their corresponding storage locations; based on the application requirements of the standardized components in the standardized component library, the standardized components in the standardized component library are called in a component calling method corresponding to the application requirements. In the present application, by abstracting the application scenario of the similar business logic of multiple business components that perform similar businesses, standardized components when performing similar businesses are obtained, and then multiple standardized components that perform different similar businesses are stored in their corresponding storage locations in the standardized component library, when it is necessary to call the standardized components in the standardized component library, the standardized components in the standardized component library can be called based on the application requirements of the standardized components in the standardized component library, using the component calling method corresponding to the application requirements. The calling of standardized components in the entire development process is conducive to greatly reducing the business development of developers for repeated operations in the business, thereby helping to improve the overall development efficiency of the project.

[0092] In some embodiments, the standardized component generation module is used to

[0093] Determine similar business logics of the multiple similar businesses based on the same operations included in the multiple similar businesses executed by the business component;

[0094] Based on the similar business logic, application scenario abstraction is performed to obtain the standardized component; wherein the standardized component is at least used to execute the same operations included in the multiple similar businesses.

[0095] In this exemplary embodiment, based on the same operations contained in multiple similar businesses executed by the business component, the similar business logics possessed by the multiple similar businesses are determined. For example, similar businesses include the advancement of the process of related businesses on different system platforms. Different system platforms, for example, include accounting systems, review systems, task allocation systems, and so on. However, multiple system platforms all contain the same operation of account and password login. In this regard, the same operation of account and password login can be determined as the similar business logic possessed by the multiple similar businesses. Then, based on the similar business logic, the application scenario is abstracted to obtain the standardized component of account and password login. In this way, it is convenient for subsequent developers to call standardized components, thereby reducing repetitive development work.

[0096] In some embodiments, the component calls a module for

[0097] If the application requirement for the standardized components in the standardized component library is to call all the standardized components in the standardized component library, then determine that the component calling method corresponding to the application requirement is a calling method of all standardized components that are introduced into the standardized component library and registered using a front-end engineering entry file;

[0098] Based on all standardized component calling methods introduced into the standardized component library and registered by using the front-end engineering entry file, calling the standardized components in the standardized component library;

[0099] If the application requirement for the standardized components in the standardized component library is to call a local standardized component in the standardized component library, determining that the component calling method corresponding to the application requirement is a local standardized component calling method of partially introducing the standardized component through the development page;

[0100] Based on the local standardized component calling mode of partially introducing the standardized components through the development page, some standardized components in the standardized component library are called.

[0101] In this exemplary embodiment, the component calling method for the standardized components may be different according to the application requirements of different standardized components in the standardized component library. In the present application, the component calling method may include two types, namely, the whole standardized component calling method and the partial standardized component calling method. The whole standardized component calling method is to introduce the standardized component library and register it using the front-end engineering entry file, so that developers can directly use the standardized components in the standardized component library without having to introduce them separately through the page. The partial standardized component calling method is to partially introduce the required standardized components in the standardized component library through the development page. For example, a browsing page developed for customers to browse clothing information can introduce the standardized components in the standardized component library that can be browsed by the clothing information through the development page. In this way, the standardized component calling in the standardized component library can be implemented in different calling methods according to development needs.

[0102] In some embodiments, the standardized component storage module 32 is used to

[0103] According to the predetermined different standardized components corresponding to different storage locations, a plurality of standardized components that execute different similar businesses are respectively stored in the corresponding storage locations in the standardized component library.

[0104] In this exemplary embodiment, the standardized component library includes a standardized component storage location, a configuration file, and a component demo storage location; wherein the configuration file is used to describe the functions of the standardized components stored in the standardized component library;

[0105] The standardized component storage module 32 is used to

[0106] Multiple standardized components that perform different similar businesses are stored in standardized component storage locations of the standardized component library.

[0107] In this exemplary embodiment, the standardized component library includes standardized component storage locations. When storing standardized components in the standardized component library, different standardized components corresponding to different storage locations can be predetermined, and multiple standardized components that perform different similar businesses can be stored in their respective corresponding storage locations in the standardized component library. For example, different types of standardized components can be stored in their respective corresponding standardized component storage locations. For example, standardized component A is an account and password login component, which can correspond to the first standardized component storage location; standardized component B is a video playback component, which can correspond to the second standardized component storage location, and so on.

[0108] The present disclosure provides a computer-readable storage medium on which an application of a front-end business component library is stored. When the application of the front-end business component library is executed by a processor, the application method of the front-end business component library described in the above embodiments is implemented.

[0109] The present disclosure provides a server, including a memory, a processor, and an application of a front-end business component library stored in the memory and executable on the processor. When the processor executes the application of the front-end business component library, the application method of the front-end business component library described in the above embodiments is implemented.

[0110] It should be noted that the logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be specifically implemented in any computer-readable medium for use by an instruction execution system, device or apparatus (such as a computer-based system, a system including a processor, or other system that can fetch instructions from an instruction execution system, device or apparatus and execute instructions), or in combination with these instruction execution systems, devices or apparatuses. For the purposes of this specification, "computer-readable medium" can be any device that can contain, store, communicate, propagate or transmit a program for use by an instruction execution system, device or apparatus, or in combination with these instruction execution systems, devices or apparatuses. More specific examples of computer-readable media (a non-exhaustive list) include the following: an electrical connection portion with one or more wirings (electronic device), a portable computer disk box (magnetic device), a random access memory (RAM), a read-only memory (ROM), an erasable and programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disk read-only memory (CDROM). In addition, the computer-readable medium may even be paper or other suitable medium on which the program is printed, since the program may be obtained electronically, for example, by optically scanning the paper or other medium and then editing, interpreting or otherwise processing in a suitable manner if necessary, and then stored in a computer memory.

[0111] It should be understood that the various parts of the present disclosure can be implemented in hardware, software, firmware or a combination thereof. In the above-mentioned embodiments, multiple steps or methods can be implemented in software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented by any one of the following technologies known in the art or their combination: a discrete logic circuit having a logic gate circuit for implementing a logic function for a data signal, a dedicated integrated circuit having a suitable combination of logic gate circuits, a programmable gate array (PGA), a field programmable gate array (FPGA), etc.

[0112] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" means that the specific features described in conjunction with the embodiment or example are included in at least one embodiment or example of the present disclosure. In this specification, the schematic representation of the above terms does not necessarily refer to the same embodiment or example. Moreover, the specific features described may be combined in any one or more embodiments or examples in a suitable manner.

[0113] Although the embodiments of the present disclosure have been shown and described above, it is to be understood that the above embodiments are exemplary and are not to be construed as limitations of the present disclosure. A person skilled in the art may change, modify, replace and vary the above embodiments within the scope of the present disclosure.

Claims

1. A method for applying a front-end business component library, characterized in that: include: Obtain multiple business components that perform similar business operations; Abstracting the application scenarios of similar business logics of the multiple business components that execute similar businesses, and obtaining standardized components for executing similar businesses; Store multiple standardized components that perform different similar businesses in their respective corresponding storage locations in the standardized component library; Based on application requirements for standardized components in the standardized component library, the standard components in the standardized component library are called using a component calling method corresponding to the application requirements.

2. The application method of the front-end business component library according to claim 1, characterized in that: The similar business logics of the multiple business components that execute similar business are abstracted by application scenarios to obtain standardized components for executing similar business, including: Determine similar business logics of the multiple similar businesses based on the same operations included in the multiple similar businesses executed by the business component; Based on the similar business logic, application scenario abstraction is performed to obtain the standardized component; wherein the standardized component is at least used to execute the same operations included in the multiple similar businesses.

3. The application method of the front-end business component library according to claim 1, characterized in that: The calling of the standardized components in the standardized component library based on the application requirements of the standardized components in the standardized component library by using the component calling method corresponding to the application requirements includes: If the application requirement for the standardized components in the standardized component library is to call all the standard components in the standardized component library, then determine that the component calling method corresponding to the application requirement is a calling method of all the standardized components that are introduced into the standardized component library and registered using a front-end engineering entry file; Based on all standardized component calling methods introduced into the standardized component library and registered by using the front-end engineering entry file, calling the standardized components in the standardized component library; If the application requirement for the standardized components in the standardized component library is to call a local standardized component in the standardized component library, determining that the component calling method corresponding to the application requirement is a local standardized component calling method of partially introducing the standardized component through the development page; Based on the local standardized component calling mode of partially introducing the standardized components through the development page, some standardized components in the standardized component library are called.

4. The application method of the front-end business component library according to claim 1, characterized in that: The step of storing a plurality of standardized components that perform different similar services in respective corresponding storage locations in the standardized component library comprises: According to the predetermined different standardized components corresponding to different storage locations, a plurality of standardized components that execute different similar businesses are respectively stored in the corresponding storage locations in the standardized component library.

5. The application method of the front-end business component library according to claim 1, characterized in that: The standardized component library includes a standardized component storage location, a configuration file, and a component demo storage location; wherein the configuration file is used to describe the functions of the standardized components stored in the standardized component library; The step of storing a plurality of standardized components that perform different similar services in respective corresponding storage locations in the standardized component library comprises: Multiple standardized components that perform different similar businesses are stored in standardized component storage locations of the standardized component library.

6. An application device for a front-end business component library, characterized in that: include: A business component acquisition module is used to acquire multiple business components that perform similar businesses; A standardized component generation module, used to abstract the application scenarios of the similar business logics of the multiple business components that perform similar business, and obtain standardized components for performing similar business; A standardized component storage module is used to store multiple standardized components that perform different similar services in their respective corresponding storage locations in the standardized component library; The component calling module is used to call the standardized components in the standardized component library based on the application requirements for the standardized components in the standardized component library and adopt the component calling method corresponding to the application requirements.

7. The application device of the front-end business component library according to claim 6, characterized in that: The standardized component generation module is used to Determine similar business logics of the multiple similar businesses based on the same operations included in the multiple similar businesses executed by the business component; Based on the similar business logic, application scenario abstraction is performed to obtain the standardized component; wherein the standardized component is at least used to execute the same operations included in the multiple similar businesses.

8. The application device of the front-end business component library according to claim 6, characterized in that: The component calls a module for If the application requirement for the standardized components in the standardized component library is to call all the standardized components in the standardized component library, then determine that the component calling method corresponding to the application requirement is a calling method of all standardized components that are introduced into the standardized component library and registered using a front-end engineering entry file; Based on all standardized component calling methods introduced into the standardized component library and registered by using the front-end engineering entry file, calling the standardized components in the standardized component library; If the application requirement for the standardized components in the standardized component library is to call a local standardized component in the standardized component library, determining that the component calling method corresponding to the application requirement is a local standardized component calling method of partially introducing the standardized component through the development page; Based on the local standardized component calling mode of partially introducing the standardized components through the development page, some standardized components in the standardized component library are called.

9. A computer-readable storage medium, characterized in that: An application of a front-end business component library is stored thereon, and when the application of the front-end business component library is executed by a processor, an application method of the front-end business component library according to any one of claims 1-5 is implemented.

10. A server, characterized in that: The invention comprises a memory, a processor and an application of a front-end business component library stored in the memory and executable on the processor. When the processor executes the application of the front-end business component library, the application method of the front-end business component library described in any one of claims 1 to 5 is implemented.

Images