CN116400959A - Front-end function expansion device, method, equipment and storage medium - Google Patents

Front-end function expansion device, method, equipment and storage medium Download PDF

Info

Publication number
CN116400959A
CN116400959A CN202310309227.3A CN202310309227A CN116400959A CN 116400959 A CN116400959 A CN 116400959A CN 202310309227 A CN202310309227 A CN 202310309227A CN 116400959 A CN116400959 A CN 116400959A
Authority
CN
China
Prior art keywords
target
logic
current
system environment
business logic
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202310309227.3A
Other languages
Chinese (zh)
Inventor
邬洪阳
钱晓雷
母思路
吴海洋
王伟
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Servyou Software Group Co ltd
Original Assignee
Servyou Software Group Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Servyou Software Group Co ltd filed Critical Servyou Software Group Co ltd
Priority to CN202310309227.3A priority Critical patent/CN116400959A/en
Publication of CN116400959A publication Critical patent/CN116400959A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/70Software maintenance or management
    • G06F8/73Program documentation
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/70Software maintenance or management
    • G06F8/71Version control; Configuration management
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/445Program loading or initiating
    • G06F9/44521Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
    • G06F9/44526Plug-ins; Add-ons
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00Energy efficient computing, e.g. low power processors, power management or thermal management

Abstract

The application discloses a front-end function expansion device, a method, equipment and a storage medium, which relate to the technical field of computers and comprise the following steps: the environment configuration module is used for configuring system environment requirements required by the execution of the target business logic; the parameter configuration module is used for configuring target parameters required by the target service logic and setting triggering conditions of the target service logic; the logic configuration module is used for configuring service logic according to service requirements in a target service scene to obtain target service logic, and packaging the target service logic into a target plug-in; the path generation module is used for generating a file resource path of the target plug-in when the system environment meets the requirement, the current parameter value corresponding to the target parameter meets the triggering condition and the current service scene is the target service scene; and the logic calling module is used for calling and executing the target business logic in the target plug-in. The method and the device realize non-invasive function expansion of the original software system or on-line function completion of friends.

Description

Front-end function expansion device, method, equipment and storage medium
Technical Field
The invention relates to the technical field of computers, and more particularly, to a front-end function extension apparatus, method, device, and storage medium.
Background
The function expansion is an important link in the software research and development process, is a key technical means for realizing function enhancement, and generally, the function enhancement is mainly realized by source codes on functions which do not exist in the original program, for example, a safety verification function needing interception is performed on the original submitting link, and the safety of the program is further enhanced. In the process of program development, the function expansion generally has the following requirements: in the software development process, because of the temporary requirements of the demonstration class, the function test point class and the like of the first party, the software needs to be expanded on the original function nodes, and after the software development process is finished, the function needs to be restored. Program software is already running in a production environment, and on the premise that restarting service is not allowed in reality, on-line function enhancement needs to be realized by means of technology. When a software system is commonly completed by a plurality of manufacturers, when the friends cannot provide source code support, the functions of the programs of the friends are required to be enhanced by technical means. However, the prior art has drawbacks in solving the above-mentioned problems. For example, pulling a branch code requires pulling a copy of a code backup in a source code repository, and implementing a functional extension on the branch code, which has long resulted in a large number of branch codes in the source code repository, and eventually cannot be combined with the backbone branches, which is difficult to maintain. Multiparty coding transformation requires contract development specifications for the same service, including coding specifications, data format specifications, request parameter specifications, etc., resulting in a large amount of management and joint debugging docking costs. The code differentiation is equivalent to the code transformation in a trunk branch code, the volume of the code becomes large, when the scene and differentiation are excessive, the readability and maintainability of the source code become difficult and heavy, and most importantly, when the code is in the scene A, the code of the scene B business logic still exists, a large amount of useless differentiated codes are generated, and the extra flow cost is caused.
Disclosure of Invention
In view of the above, an object of the present invention is to provide a front-end function expansion device, method, apparatus, and storage medium that can solve the problem of enhancing the function of an original system by non-invasive implementation, and that can accomplish the functions of putting on and off shelves at any time as long as the investment of small cost is made. The specific scheme is as follows:
in a first aspect, the present application provides a front-end function extension device, including:
the environment configuration module is used for configuring system environment requirements required by the execution of the target business logic;
the parameter configuration module is used for configuring target parameters required by the target business logic during execution and setting triggering conditions of the target business logic by utilizing the target parameters;
the logic configuration module is used for configuring corresponding service logic according to service requirements in a target service scene to obtain the target service logic, and packaging the target service logic into a target plug-in;
the path generation module is used for generating a file resource path of the target plug-in when the current system environment of the front end meets the system environment requirement, the current parameter value corresponding to the target parameter meets the triggering condition and the current service scene of the front end is the target service scene;
and the logic calling module is used for calling and executing the target business logic in the target plug-in from the file resource path.
Optionally, the environment configuration module includes:
and the parameter information configuration unit is used for configuring system environment parameter information required by the target business logic when in execution, wherein the system environment parameter information comprises system version information, system functions and a user white list required by the target business logic when in execution.
Optionally, the apparatus further includes:
the analysis module is used for analyzing the configured system environment requirement, the target parameter, the trigger condition and the target business logic to obtain analyzed information, and sending the analyzed information to the path generation module.
Optionally, the path generating module includes:
the first judging unit is used for judging whether the current system environment of the front end meets the system environment requirement in the analyzed information;
the second judging unit is used for judging whether the current parameter value corresponding to the target parameter meets the triggering condition in the analyzed information;
the third judging unit is used for judging whether the current service scene of the front end is the target service scene in the analyzed information;
and the path generating unit is used for processing and assembling the analyzed information when the current system environment of the front end meets the system environment requirement, the current parameter value corresponding to the target parameter meets the triggering condition and the current service scene of the front end is the target service scene so as to generate the file resource path of the target plug-in.
Optionally, the path generating module further includes:
and the flow ending unit is used for ending the current function expansion flow when the current system environment of the current end does not meet the system environment requirement and the current parameter value corresponding to the target parameter does not meet the trigger condition or the current service scene of the front end is not the target service scene.
Optionally, the logic call module includes:
and the asynchronous loading unit is used for asynchronously loading the resource file of the target plug-in according to the file resource path so as to call and execute the target business logic in the target plug-in.
Optionally, the target business logic specifically may include: the system comprises any one or a combination of a first logic used for changing the original data processing flow of the target interface data in the front end, a second logic used for changing the original business logic in the front end and a third logic used for adjusting the interface element of the target type in the front end.
In a second aspect, the present application provides a front-end function extension method, including:
configuring system environment requirements required by target business logic in execution;
configuring target parameters required by the target service logic during execution, and setting triggering conditions of the target service logic by utilizing the target parameters;
configuring corresponding business logic according to business requirements in a target business scene to obtain the target business logic, and packaging the target business logic into a target plug-in;
when the current system environment of the front end meets the system environment requirement, the current parameter value corresponding to the target parameter meets the triggering condition, and the current service scene of the front end is the target service scene, generating a file resource path of the target plug-in;
and the target business logic in the target plugin is fetched and executed from the file resource path.
In a third aspect, the present application provides an electronic device, including:
a memory for storing a computer program;
and the processor is used for executing the computer program to realize the steps of the front-end function expansion method.
In a fourth aspect, the present application provides a computer-readable storage medium for storing a computer program; wherein the computer program when executed by the processor implements the steps of the front-end function extension method described above.
The environment configuration module is used for configuring the system environment requirement required by the execution of the target business logic; the parameter configuration module is used for configuring target parameters required by the target business logic during execution and setting triggering conditions of the target business logic by utilizing the target parameters; the logic configuration module is used for configuring corresponding service logic according to service requirements in a target service scene to obtain the target service logic, and packaging the target service logic into a target plug-in; the path generation module is used for generating a file resource path of the target plug-in when the current system environment of the front end meets the system environment requirement, the current parameter value corresponding to the target parameter meets the triggering condition and the current service scene of the front end is the target service scene; and the logic calling module is used for calling and executing the target business logic in the target plug-in from the file resource path. Therefore, the method and the device monitor and strengthen the original business logic in a manner of packaging the plug-in and dynamically injecting the script, and particularly can avoid forcing the friend cooperation units to synchronously cooperate and modify codes in the multi-party cooperation process, thereby greatly reducing the joint debugging and cooperation cost, realizing the effects that the original codes can not be modified for a certain program to apply function expansion and a server is not required to be restarted.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings that are required to be used in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are only embodiments of the present invention, and that other drawings can be obtained according to the provided drawings without inventive effort for a person skilled in the art.
Fig. 1 is a schematic diagram of a front end function expansion device provided in the present application;
fig. 2 is a schematic structural diagram of a front-end function expansion system provided in the present application;
fig. 3 is a schematic diagram of configuration information of a registration device provided in the present application;
fig. 4 is a schematic diagram of information analysis provided in the present application;
FIG. 5 is a schematic diagram of a data item synthesis result provided in the present application;
FIG. 6 is a schematic diagram of a logic execution flow provided in the present application;
FIG. 7 is a complete schematic flow chart of the application generalized to the landing of other business scenarios;
FIG. 8 is a flowchart of a front end function expansion method provided in the present application;
fig. 9 is a block diagram of an electronic device provided in the present application.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present invention, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
The currently known ways of enhancing or differentiating processing functions basically modify the trunk branches, pull the branches or increase the system parameters in the packaging process to complete the differentiation of the final online results, but the above ways need to restart the service, which is very inefficient and has very low effect. In order to solve the above problems, the present application provides a front-end function expansion device, which can implement non-invasive function expansion for the on-line functions of the original software system or friends.
Referring to fig. 1, an embodiment of the present invention discloses a front-end function expansion device, including:
the environment configuration module 11 is configured to configure system environment requirements required by the target business logic when executing.
In this embodiment, the environment is the final execution environment of the program code, and the current environment in which the front-end program code finally operates is divided into two environments, namely a browser and a node. Wherein, the environment configuration module includes: and the parameter information configuration unit is used for configuring system environment parameter information required by the target business logic when in execution, wherein the system environment parameter information comprises system version information, system functions and a user white list required by the target business logic when in execution.
The parameter configuration module 12 is configured to configure target parameters required by the target service logic when the target service logic is executed, and set triggering conditions of the target service logic by using the target parameters.
In this embodiment, the data items, i.e. parameters, are various parameters required for the execution of the program code, including both fixed variables and dynamic variables, where the static variables mainly describe the version of the function, text description, execution assistance, etc., and the dynamic variables mainly include system parameters, browser parameters, dom (Document Object Model ) structures, etc., acquired at runtime. In the parameter configuration process, a data matching mechanism and a triggering condition are included, the configuration can be carried out according to a specific service scene, under the configuration of the registration device, the current triggering condition is judged based on a hash value of a url (Universal Resource Locator, uniform resource locator) of a browser, and the matching is effective.
The logic configuration module 13 is configured to configure corresponding service logic according to service requirements in a target service scenario, so as to obtain the target service logic, and encapsulate the target service logic into a target plug-in.
In this embodiment, the logic configuration, that is, the scene configuration, encapsulates the logic of one or more scenes into a javascript plug-in according to the service requirement, where the scene is a basic execution unit, and after the execution of the unit, the original service function has a function enhancement part inside the javascript plug-in. It should be noted that, the above three configuration modules, the environment configuration module, the parameter (data item) configuration module, and the logic (scene) configuration module form a registration device, as shown in fig. 2, the information for registering various configuration units is data of json (JavaScriptObject Notation, JS object numbered) structure, and is used for organizing relevant information with enhanced functions, including, but not limited to, function description, version number, icon library, white list, and the like. A configuration case is similar to the data shown in fig. 3, and in this registration configuration, the function-enhanced plug-in is named content_descriptions. The registration is to compress all the files into a program package, then register the program package into the expansion program of the browser in a browser plug-in mode, and finally enable the browser to assist in execution. After registration is completed, further comprising: the analysis module is used for analyzing the configured system environment requirement, the target parameter, the trigger condition and the target business logic to obtain analyzed information, and sending the analyzed information to the path generation module.
And the path generating module 14 is configured to generate a file resource path of the target plug-in when the current system environment of the front end meets the system environment requirement, the current parameter value corresponding to the target parameter meets the trigger condition, and the current service scene of the front end is the target service scene.
In this embodiment, the path generating module includes: the first judging unit is used for judging whether the current system environment of the front end meets the system environment requirement in the analyzed information; the second judging unit is used for judging whether the current parameter value corresponding to the target parameter meets the triggering condition in the analyzed information; the third judging unit is used for judging whether the current service scene of the front end is the target service scene in the analyzed information; and the path generating unit is used for processing and assembling the analyzed information when the current system environment of the front end meets the system environment requirement, the current parameter value corresponding to the target parameter meets the triggering condition and the current service scene of the front end is the target service scene so as to generate the file resource path of the target plug-in. The path generation module further includes: and the flow ending unit is used for ending the current function expansion flow when the current system environment of the current end does not meet the system environment requirement and the current parameter value corresponding to the target parameter does not meet the trigger condition or the current service scene of the front end is not the target service scene. In a specific embodiment, as shown in fig. 4, it is determined whether all of the checks in the graph pass, and if so, the data item synthesizer is entered. The data item synthesis refers to a process of reassembling data according to the information returned by the registration information parser, such as variable replacement and resource path synthesis, and the result of data synthesis in this case is to assemble a resource path to be loaded, as shown in fig. 5. After the data item synthesizer assembles the data, starting to execute resource asynchronous loading, loading the CSS file into a < head > tag of a current window page Dom structure, loading the js file into the bottom of the < body > tag, and noting that the js resource file must be loaded into the tail of the tag so as to ensure that the original business logic is completely loaded. Therefore, the data can be dynamically assembled based on the technical scheme of the application, and the iframe window can be transmitted in a transparent way.
And the logic calling module 15 is used for calling and executing the target business logic in the target plug-in from the file resource path.
In this embodiment, the logic call module includes: and the asynchronous loading unit is used for asynchronously loading the resource file of the target plug-in according to the file resource path so as to call and execute the target business logic in the target plug-in. The target business logic comprises any one or a combination of a plurality of first logic used for changing the original data processing flow of the target interface data in the front end, second logic used for changing the original business logic in the front end and third logic used for adjusting the interface element of the target type in the front end. In a specific embodiment, three typical scenarios are implemented, one of which, taking the data encryption scenario as an example, assumes that we now need to encrypt data submitted by a user of a system before submitting it. After the processing of the device (101) and the device (102), we can clearly know that the interface of the data submitted by the user is assumed to be 'post/userInfo', the capturing mechanism is to monitor the data sending, when the captured interface url is just matched with 'post/userInfo', we cancel the original request, encrypt the transmitted data according to the need (such as base64, RSA, national secret algorithm, etc.), and then call our own request body, and the data received by the 'post/userInfo' becomes encrypted data. I.e. a first logic for changing the original data processing flow of the target interface data in the front-end. Secondly, taking a scene of changing a user interaction mode as an example, there is a business audit scene, and the credit risk prompt function of a sponsor user is added in the original business approval process. Namely, a second logic for changing the original service logic in the front end. Thirdly, by using the above service resetting case, it is assumed that a red font warning is to be adopted for a high risk user, when handling or capturing an event, the position of the list where the user is located can be obtained, the original Dom structure is read, the original attribute of the original Dom is added, and the font color font-color is marked as red. I.e. a third logic for adjusting interface elements of a target type in the front-end. In addition, a complete schematic flow chart of the technical scheme of the application generalized to the landing of other business scenes is shown in fig. 7. Therefore, the original code can be not modified by using the technical scheme of the application to extend the function of a certain program, and the server is not required to be restarted. Meanwhile, the method and the device are combined with a white list mechanism in a plug-in mode, so that the safety requirement of the project is met. Therefore, when the multiparty system is integrated, the scheme is adopted to reduce the cooperation cost. The functional scene can be configured, and the variable is dynamically transmitted through url parameters, and has window transparent transmission characteristics. The on-line function enhancement can be realized by means of the pure front end of the scheme.
The environment configuration module is used for configuring the system environment requirement required by the execution of the target business logic; the parameter configuration module is used for configuring target parameters required by the target business logic during execution and setting triggering conditions of the target business logic by utilizing the target parameters; the logic configuration module is used for configuring corresponding service logic according to service requirements in a target service scene to obtain the target service logic, and packaging the target service logic into a target plug-in; the path generation module is used for generating a file resource path of the target plug-in when the current system environment of the front end meets the system environment requirement, the current parameter value corresponding to the target parameter meets the triggering condition and the current service scene of the front end is the target service scene; and the logic calling module is used for calling and executing the target business logic in the target plug-in from the file resource path. Therefore, the method and the device monitor and strengthen the original business logic in a manner of packaging the plug-in and dynamically injecting the script, and particularly can avoid forcing the friend cooperation units to synchronously cooperate and modify codes in the multi-party cooperation process, thereby greatly reducing the joint debugging and cooperation cost, realizing the effects that the original codes can not be modified for a certain program to apply function expansion and a server is not required to be restarted.
Referring to fig. 8, an embodiment of the present invention discloses a front-end function extension method, which includes:
step S11, the system environment requirement required by the target business logic in execution is configured.
And step S12, configuring target parameters required by the target business logic during execution, and setting triggering conditions of the target business logic by utilizing the target parameters.
And step S13, configuring corresponding business logic according to business requirements in a target business scene to obtain the target business logic, and packaging the target business logic into a target plug-in.
And S14, when the current system environment of the front end meets the system environment requirement, the current parameter value corresponding to the target parameter meets the triggering condition, and the current service scene of the front end is the target service scene, generating a file resource path of the target plug-in.
And step S15, the target business logic in the target plug-in is fetched and executed from the file resource path.
As can be seen from the above, when the front-end function expansion is performed, the system environment requirement required by the target service logic during execution is firstly configured; configuring target parameters required by the target service logic during execution, and setting triggering conditions of the target service logic by utilizing the target parameters; configuring corresponding business logic according to business requirements in a target business scene to obtain the target business logic, and packaging the target business logic into a target plug-in; when the current system environment of the front end meets the system environment requirement, the current parameter value corresponding to the target parameter meets the triggering condition, and the current service scene of the front end is the target service scene, generating a file resource path of the target plug-in; and the target business logic in the target plugin is fetched and executed from the file resource path. Therefore, the method and the device monitor and strengthen the original business logic in a manner of packaging the plug-in and dynamically injecting the script, and particularly can avoid forcing the friend cooperation units to synchronously cooperate and modify codes in the multi-party cooperation process, thereby greatly reducing the joint debugging and cooperation cost, realizing the effects that the original codes can not be modified for a certain program to apply function expansion and a server is not required to be restarted.
Further, the embodiment of the present application further discloses an electronic device, and fig. 9 is a block diagram of the electronic device 20 according to an exemplary embodiment, where the content of the figure is not to be considered as any limitation on the scope of use of the present application.
Fig. 9 is a schematic structural diagram of an electronic device 20 according to an embodiment of the present application. The electronic device 20 may specifically include: at least one processor 21, at least one memory 22, a power supply 23, a communication interface 24, an input output interface 25, and a communication bus 26. The memory 22 is configured to store a computer program, which is loaded and executed by the processor 21 to implement relevant steps in the front-end function extension method disclosed in any of the foregoing embodiments. In addition, the electronic device 20 in the present embodiment may be specifically an electronic computer.
In this embodiment, the power supply 23 is configured to provide an operating voltage for each hardware device on the electronic device 20; the communication interface 24 can create a data transmission channel between the electronic device 20 and an external device, and the communication protocol to be followed is any communication protocol applicable to the technical solution of the present application, which is not specifically limited herein; the input/output interface 25 is used for acquiring external input data or outputting external output data, and the specific interface type thereof may be selected according to the specific application requirement, which is not limited herein.
The memory 22 may be a carrier for storing resources, such as a read-only memory, a random access memory, a magnetic disk, or an optical disk, and the resources stored thereon may include an operating system 221, a computer program 222, and the like, and the storage may be temporary storage or permanent storage.
The operating system 221 is used for managing and controlling various hardware devices on the electronic device 20 and computer programs 222, which may be Windows Server, netware, unix, linux, etc. The computer program 222 may further include a computer program that can be used to perform other specific tasks in addition to the computer program that can be used to perform the front-end function extension method performed by the electronic device 20 disclosed in any of the previous embodiments.
Further, the application also discloses a computer readable storage medium for storing a computer program; wherein the computer program, when executed by a processor, implements the front-end function extension method disclosed previously. For specific steps of the method, reference may be made to the corresponding contents disclosed in the foregoing embodiments, and no further description is given here.
In this specification, each embodiment is described in a progressive manner, and each embodiment is mainly described in a different point from other embodiments, so that the same or similar parts between the embodiments are referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant points refer to the description of the method section.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative elements and steps are described above generally in terms of functionality in order to clearly illustrate the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. The software modules may be disposed in Random Access Memory (RAM), memory, read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
Finally, it is further noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The foregoing has outlined the detailed description of the preferred embodiment of the present application, and the detailed description of the principles and embodiments of the present application has been provided herein by way of example only to facilitate the understanding of the method and core concepts of the present application; meanwhile, as those skilled in the art will have modifications in the specific embodiments and application scope in accordance with the ideas of the present application, the present description should not be construed as limiting the present application in view of the above.

Claims (10)

1. A front-end function expansion device, comprising:
the environment configuration module is used for configuring system environment requirements required by the execution of the target business logic;
the parameter configuration module is used for configuring target parameters required by the target business logic during execution and setting triggering conditions of the target business logic by utilizing the target parameters;
the logic configuration module is used for configuring corresponding service logic according to service requirements in a target service scene to obtain the target service logic, and packaging the target service logic into a target plug-in;
the path generation module is used for generating a file resource path of the target plug-in when the current system environment of the front end meets the system environment requirement, the current parameter value corresponding to the target parameter meets the triggering condition and the current service scene of the front end is the target service scene;
and the logic calling module is used for calling and executing the target business logic in the target plug-in from the file resource path.
2. The front-end function extension device according to claim 1, wherein the environment configuration module comprises:
and the parameter information configuration unit is used for configuring system environment parameter information required by the target business logic when in execution, wherein the system environment parameter information comprises system version information, system functions and a user white list required by the target business logic when in execution.
3. The front-end function extension device according to claim 1, further comprising:
the analysis module is used for analyzing the configured system environment requirement, the target parameter, the trigger condition and the target business logic to obtain analyzed information, and sending the analyzed information to the path generation module.
4. The front-end function extension device according to claim 3, wherein the path generation module includes:
the first judging unit is used for judging whether the current system environment of the front end meets the system environment requirement in the analyzed information;
the second judging unit is used for judging whether the current parameter value corresponding to the target parameter meets the triggering condition in the analyzed information;
the third judging unit is used for judging whether the current service scene of the front end is the target service scene in the analyzed information;
and the path generating unit is used for processing and assembling the analyzed information when the current system environment of the front end meets the system environment requirement, the current parameter value corresponding to the target parameter meets the triggering condition and the current service scene of the front end is the target service scene so as to generate the file resource path of the target plug-in.
5. The front-end function expansion device according to claim 1, wherein the path generation module further comprises:
and the flow ending unit is used for ending the current function expansion flow when the current system environment of the current end does not meet the system environment requirement and the current parameter value corresponding to the target parameter does not meet the trigger condition or the current service scene of the front end is not the target service scene.
6. The front-end function extension apparatus according to claim 1, wherein the logic call module comprises:
and the asynchronous loading unit is used for asynchronously loading the resource file of the target plug-in according to the file resource path so as to call and execute the target business logic in the target plug-in.
7. The apparatus according to any one of claims 1 to 6, wherein the target business logic includes any one or a combination of several of a first logic for changing an original data processing flow of target interface data in the front end, a second logic for changing an original business logic in the front end, and a third logic for adjusting an interface element of a target type in the front end.
8. A front-end function extension method, comprising:
configuring system environment requirements required by target business logic in execution;
configuring target parameters required by the target service logic during execution, and setting triggering conditions of the target service logic by utilizing the target parameters;
configuring corresponding business logic according to business requirements in a target business scene to obtain the target business logic, and packaging the target business logic into a target plug-in;
when the current system environment of the front end meets the system environment requirement, the current parameter value corresponding to the target parameter meets the triggering condition, and the current service scene of the front end is the target service scene, generating a file resource path of the target plug-in;
and the target business logic in the target plugin is fetched and executed from the file resource path.
9. An electronic device, comprising:
a memory for storing a computer program;
a processor for executing the computer program to implement the front-end function extension method of claim 8.
10. A computer readable storage medium storing a computer program which, when executed by a processor, implements the front-end functionality extension method of claim 8.
CN202310309227.3A 2023-03-22 2023-03-22 Front-end function expansion device, method, equipment and storage medium Pending CN116400959A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310309227.3A CN116400959A (en) 2023-03-22 2023-03-22 Front-end function expansion device, method, equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310309227.3A CN116400959A (en) 2023-03-22 2023-03-22 Front-end function expansion device, method, equipment and storage medium

Publications (1)

Publication Number Publication Date
CN116400959A true CN116400959A (en) 2023-07-07

Family

ID=87009617

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310309227.3A Pending CN116400959A (en) 2023-03-22 2023-03-22 Front-end function expansion device, method, equipment and storage medium

Country Status (1)

Country Link
CN (1) CN116400959A (en)

Similar Documents

Publication Publication Date Title
Tao et al. A reusable software component for integrated syntax and semantic validation for services computing
CA2915619C (en) Method and apparatus for customized software development kit (sdk) generation
US8983935B2 (en) Methods for utilizing a javascript emulator in a web content proxy server and devices thereof
CN105872083A (en) Method and system supporting server access by different types of clients as well as server
CN112015396B (en) DSL-based intelligent contract code generation method, device, equipment and storage medium
CN113238740B (en) Code generation method, code generation device, storage medium and electronic device
CN111880790A (en) Page rendering method, page rendering system, and computer-readable storage medium
KR102226463B1 (en) UI/UX solution providing server linked with process automation program, process automation method using the same, and computer program executing the same
WO2021093672A1 (en) Method for embedding external system, workflow system, device and computer readable storage medium
CN112416533A (en) Method and device for running application program on browser and electronic equipment
US20100057937A1 (en) Method and System for Facilitating Client Server Interaction
CN111880789A (en) Page rendering method, device, server and computer-readable storage medium
CN116432624A (en) Micro-service API document generation method, device, equipment and storage medium
CN115904317A (en) Method, device, equipment and storage medium for uniformly calling front-end interface and back-end interface
CN113315829B (en) Client offline H5 page loading method and device, computer equipment and medium
CN116400959A (en) Front-end function expansion device, method, equipment and storage medium
CN115022312A (en) Method and device for realizing multiple intelligent contract engines, electronic equipment and storage medium
CN112433752A (en) Page parsing method, device, medium and electronic equipment
CN108076067B (en) Method and system for authorized crawler configuration simulation login
US20090300099A1 (en) Aspect services
CN102148755A (en) Mainframe injection component and method for manipulating data packets communicated between emulators and mainframes
CN111443946A (en) Interactive method, system, server and storage medium of IOS system and page
CN115242764B (en) Multi-terminal communication method, system, equipment and storage medium for front end
CN108845803B (en) Method, device and equipment for updating list view and storage medium
CN115982257A (en) Interface creation method and related device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination